Can we ONLY create icons?

[AlixH]

I would like to only create the icons without modifying any file, including the AndroidManifest.xml

[martiliones]

Hello. I don't think we have such an option, but we can implement it.

What exact functionality are you looking for? Please tell me more. Do you want to generate icons inside specific directory without overwriting ic_launcher? or do you still want to create the icons inside android/ios directories without overwriting manifest files?

[martiliones]

Thanks for your contributing. I just merged #26 and published a new version (icon-set-creator@1.2.6) with additional Android support. Let me know if this solves your issue.

[AlixH]

Thank you so much for quick feedback !
Ideally I would like to be able to generate icons inside a custom directory AND not modify any other existing files. So neither AndroidManifest.xml, nor colors.xml
I think manifest file update can be done manually when option enabled, and colors.xml can be renamed colors-launcher.xml , or just colors.xml inside the custom dir

[martiliones]

What about this: I will create "custom directory" option that will generate the icons with all the files in the same structure it would in the project (e.g. customDirectory/android/app/src/main/) and you will be able to combine it with disableLaunchIcon to generate only icons without the structure

[AlixH]

What about this: I will create "custom directory" option that will generate the icons with all the files in the same structure it would in the project (e.g. customDirectory/android/app/src/main/) and you will be able to combine it with disableLaunchIcon to generate only icons without the structure

What do you mean by "without the structure" ?
I will give an example of what I have in mind :
iconset --outputDir android/app/src/main/iconsetRes
This would generate all asset folders and colors files inside the custom directory relative to the dir where you run the command.

And the command disableLaunchIcon would additionally leave existing files untouched. But I think it would be easier to always leave them untouched when the custom dir option is used because otherwise you will have to add the custom dirs inside the manifest and build.gradle to link the generated colors and assets

[martiliones]

This what I had in my head:

When you try to generate icons in custom directory without --disable-launcher-icon flag, it would create icons with the entire android/ios directories structure and manifest files examples:

$ iconset --output customDir/

customDir
├── android
│   └── app
│       └── src
│           └── main
│               └── res
└── ios
    ├── project
    │   └── Images.xcassets
    └── project.xcodeproj

This way you could just drag&drop content of the customDir into your project.

When using with --disable-launcher-icon:

$ iconset -disable-launcher-icon --output customDir/

customDir
├── android
│   ├── myicon.png
│   └── myicon_round.png
└── ios
    └── myicon-29x29@2x.png

[AlixH]

This what I had in my head:

When you try to generate icons in custom directory without --disable-launcher-icon flag, it would create icons with the entire android/ios directories structure and manifest files examples:

$ iconset --output customDir/

customDir
├── android
│   └── app
│       └── src
│           └── main
│               └── res
└── ios
    ├── project
    │   └── Images.xcassets
    └── project.xcodeproj

This way you could just drag&drop content of the customDir into your project.

When using with --disable-launcher-icon:

$ iconset -disable-launcher-icon --output customDir/

customDir
├── android
│   ├── myicon.png
│   └── myicon_round.png
└── ios
    └── myicon-29x29@2x.png

Well, my scenario is: I have a RN project with no assets. I need to be able to generate all assets dynamically inside a custom directory inside both android and ios directories. By one command I could change the app assets and build it with new icons without needing to copy paste anything and without impacting my git working tree