-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Select target dependency configuration (Android studio scope) #20
Comments
Uhhh...could you provide some examples to explain it? I do not quite understand what you mean |
Sure, so basically there are different product favours inside android application (product flavour is used to create different branding e.g. different logo or free/paid versions - basically the same app but with few differences in behaviour or appearance) By default you put all the resources into (this is what this plugin does) You can place the resources also in different product flavours folders, build variant folders or built type folders. Product flavour are combined with build types:
Example: We can have multiple locations for our logo based on:
I believe the best thing to address this problem would be to add ComboBox Build type containing list of all buildtypes avialable in the project (attach). Also we woudl change 'XML to' to 'Module name' https://drive.google.com/file/d/0B4hXruznbpCVOXZhd1BibThMbEk/view Here is a example updating icon Android build variants Feel free to ask if you need more explanation. |
Generally yes although I am not sure if there is a point of adding resources to 'test' folders, so I am 90% sure they should not be on the list. Also keep in mind that there may be case where folder for particular build type does not exist although build type actually exists, so if you want to handle this you should get full of product flavours from build.gradle and generate proper build types (folder names) + add default ones (main, debug, release) (mabye we should have 'show only existing folders' checkbox)
|
Now all assets go to default scope (main dependency configuration), but sometimes we want to add new resource to other configuration e.g change logo/icons when rebranding app.
It would be nice to have combibox containing list of all avialable configurations to select target of generated resource
The text was updated successfully, but these errors were encountered: