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

Problem naming convention exporting to android #2085

Closed
holandaeric opened this Issue Jul 9, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@holandaeric

holandaeric commented Jul 9, 2018

  • Version: 3.1.1

  • Web/Desktop: Web and desktop

  • Platform/Browser: Windows

  • Avocode e-mail: ehv@cesar.org.br

I am using a naming convention for assets like "ic_home", but when I am exporting it (in web and desktop) is changing to "ic-home". This kind of naming "-" is not supported by android, so I have to renaming one by one before export.

  • For next version: Would be very nice if we could set up the android folders "drawable_..." as a prefix when exporting assets :))))

Thanks!!!

@jakubzitny

This comment has been minimized.

Member

jakubzitny commented Jul 9, 2018

Hi @holandaeric, thanks a lot for these comments. We definitely have to change the underscore to dash behaviour. As for the second request, we already know about it and we're planning to support it, however for now we've had more urgent features to address. Please vote for the feature on our UserVoice.

@jakubzitny jakubzitny self-assigned this Jul 9, 2018

@jakubzitny jakubzitny added this to the 3.3.0 milestone Jul 9, 2018

@jakubzitny jakubzitny added the onGitlab label Jul 10, 2018

@jakubzitny

This comment has been minimized.

Member

jakubzitny commented Jul 25, 2018

Hi @holandaeric, the naming conventions are improved in latest version of Avocode 3.3.1. For the future we'll be also adding the scaled Android drawables to appropriate folders.

I'll close this issue for now, we can track the drawables on our UserVoice.

@jakubzitny jakubzitny closed this Jul 25, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment