We have a single project that is used by 2 different clients.
The Apple store won't let us use the same icon for both, so we need to build version A with Icon set A, and then the same code as version B but with Icon B.
Do you see any way to automate switching the icons?
Note: For you to be able to upload your application on the App store it is mandatory that the App name and the Bundle id(package name) of these applications are different.
Now there is a catch Apple might or might not reject your app if it has the same resources as another. (They can be confusing at times).
I would suggest you do not take a risk change the icons, and you will have to change the app related things in any case.
Do you see any way to automate switching the icons?
I don't think there is an automated way but there is a faster way, make a list of the images that you need to change with the sizes and name of that images as per your resource files, Once you are ready with all the images directly replace them in the resources by pasting them over the existing ones and replacing them.
Once you are done with that clean build your app and your resources are freshly changed and ready to rumble.
Goodluck!
Revert in case of queries.
Related
is there a possible way to work simultaneously with multiple users on a Website without overwritting the global styles. When I'm saving my changes and defining some new CSS classes they always disappear after my partner saves his changes also.
Is there a possible way to avoid this problem?
Maybe we failed at the installation and made some mistakes.
According to Oxygen's site, they do support multi-user editing.
At a guess, it may be possible to apply your own hooks so things aren't auto-generated/saved. You'd essentially create your own plugin to overwrite the functions provided by Oxygen.
How that functions, I'm not sure, but it would require "manually updating" later.
Honestly, IMO, I wouldn't try to overwrite this functionality, but instead look into local environments instead. Create a copy of the site that all your devs can use on their local machine, and then move it on to a shared/dev/staging site.
TBH, I've found Oxygen to be a bit of a step back in the DevOps life cycle, since collaboration is a task now.
The official documentation recommend using a single tab when working with Oxygen to avoid issues where one tab is saving older data than another, resulting in overwriting your new changes. The same scenario can occur when two or more users are working in Oxygen at the same time.
We have developed the plugin to support multiple user simultaneously.
http://collaboration.docs.oxyrealm.com
The plugin will update data and design instantly between multiple tabs of Oxygen Editor. So the overwrite issue is resolved since the data to save will be same and synced between the oxygen editor
I'm using React-Native. I have a mobile app and in near future I'll copy-paste it for many customers. All features will be same except colour, logo and etc. Let's assume that I have 100 mobile Apps and when there are some bugs or errors on my api or another part. I want to fix them just one time and apply it to all my mobile apps without update them on iOS-google play market. Otherwise I have to fix all my Apps separately and it will take my lot so time. I found something about it named as EXPO-OTA(Over-to-air) but that's not sufficient for me. That has some limit to update something. Is there any way to do it? Or Is it possible?
You can use react-native-config for managing each app config. like color and other configurations.
Also keep the logo in android assets and link them in js code .
After that you can use react-natve-code-push to update the js bundle over the air. This way you can sync the same codebase in every app.
I'm using Xamarin forms and I'm wondering, does the UWP Visual Asset Generator work for any image you want to add to your apps XAML? The documentation found HERE is really confusing. It appears as though the asset generator is only for assets that the app needs by default. If you try to use it to add a general image to your app it tries to overwrite the icons your app needs for windows tiles and the application icon, etc.
I have seen others on SO say that all you need to do is manually add the image to your Assets/ folder and while I can easily do that, you don't get all the different sizes and scale factor images that the Visual Asset Generator creates.
I did try using the Visual Asset Generator to create a new image anyway using the "App Icon" option but I made sure to use a different name so it didn't overwrite my existing app icon. Well, even though it didn't overwrite my original app icon my app is now using the image I'm trying to use within my app as the app icon as well.
Anyway, I called this new image I added from my XAML but instead of xaml pulling the best looking image based on the size of my image property which was 300x300 it instead used one of the really small images and it was really blurry so I'm not sure this is worth using anyway but some clarification would help in case I'm missing something.
My question is regarding using it for other image within your app like for instance, lets say I want an image embedded in the 2nd page of my app
These images are not generated for use during app development.
Images generated by UWP Visual Assets Generator are used as the logos or icons of an app in different devices or scenes for different sizes needs. These images are generated for the process of publishing instead of developing the app.Therefore,making good use of these images is of great help for users to identify your app.
Explain with the generated pictures Square44x44Logo.png and Square150x150Logo.png:
I am working with my teammates on the same WordPress project, but once in a while we face overriding each other's codes, mainly in functions.php or style.css files. I was wondering if there is any away to avoid such problems?
once a while we face overriding our codes by each other
When we fix or add something we may not like to first ask about 2 minutes
for something that is done in just 5 minutes. But this gets a problem when multiple persons may work on same file and do not communicate about their work.
Is there a way to know if someone else is editing same functions
You can use any of below ways:
Recommended: use any sub-version control system like Git or SVN, and work only on your own branch (i.e. create a branch even for a single method/function and merge latter, but you also need to communicate about like: will create a branch and work on ...).
You could use an IDE that has a plugin that adds the feature to show other developers actions (e.g. a separate text-cursor with remote-Developer's name above it, like "Google documents").
For example, VS Code has the so-called "Live share" extension:
https://code.visualstudio.com/learn/collaboration/live-share
Or, develop a plugin that does add such feature to your IDE, as most IDE's provide SDK.
Actively use communication method's in an advanced way (e.g. like working on exactly some file over LAN, some software do support that).
I've built a complex site for a client, who wants this duplicated, and re-skinned, so it can be used for other means.
What is the best way of doing this? I'm concerned about copying every file as this means any bugs must be fixed twice, and any improvements must be implmented twice.
I'd look to refactor your code.
Move common functions into a library you can reference from both projects. As you mention that the new site is for a different purpose then you are likely to see divergence and you don't want to hamper yourself later, so extract the common parts and then modify copies (or if appropriate new files) of the remainder to complete your fork.
If you haven't applied good practice already then now is the time to do it and it'll make your work on both sites easier moving forward.
If all the functionality is the same and only the layout is different you could just create a new css file. 2 websites could have exactly the same code base but have different stylesheets and look completely different.
I think that using a version control system like subversion or preferably git, is a good way to duplicate your website. You will be able to track the changes that you make and revert to older versions if things do not work out.
You should implement some kind of instantiation, so look and feel, content and data will be shown depending of what instance of the application is accessed.
In other words, each application access to the code with a different application identifier, meaning content will be served depending on it.
Both application identifier will be pointing to different settings, so stylesheet and content will be absolutely isolated, and both domain will be living in the same IIS application.
If you want to duplicate a whole site it's probably best to copy the whole thing and amend as necessary. Obviously taking great care not to copy large portions of text or else you may be penalised by the search engines.
There are ways you could put the new site onto the same shared host (say within a subdirectory of the original site) and literally 'share' some files. If a unique change is required, you could instead reference a 'local' version of a particular file.
However that sounds like a recipe for a headache to me. I'd prefer to duplicate the whole site. It would be much easier to replace one or two functions on separate websites than it would to try and work out which website(s) are affected by a particular change to your source.