Auto icon scaling.

Solar2D General Questions/Discussion
#1

I know it’s mainly Apple’s fault, but the number of Icon files of various sizes now required is verging on the ludicrous. It clutters up parent root directories something rotten :slight_smile:

With that in mind, would it be possible for one of the following -

(i) have a separate directory, maybe called releaseIcons or similar, where they could live, and then the Corona build system could move them if necessary for building ?

(ii) have a system whereby icons can be derived from either a large PNG which is scaled appropriately if a required icon is not present, or possibly even converted from an SVG file ?

#2

+1.

I share your apple (and google) frustrations with the bazillion icons they require these days, along with the launch images too. I think if they were to implement this system, then launch images should also be able to be put in a separate directory.

#3

Have you looked at generating the icons via the Angry Marmot system? This has literally saved me hours and grey hairs. http://icon.angrymarmot.org.

This would at least you get up and running more quickly.

best,

Jen

#4

Indeed Angry Marmot is great but I agree with @paulscottrobson in that if we were allowed to keep these files in a subdirectory off our main project directory life would be so much better. 

#5

I’ve a lua script that generates the icons from an Inkscape SVG. It’s more about neatness ( => clarity ) than anything else. 

#6

I have been thinking about this issue today and have planned out a decent solution in the form of a helper app.

The way this would work is you would create a file in your projects directory, with the path to your icons and launch images, per platform, and when you want to do a corona build they would be copied into your projects root directory automatically for you, then removed afterward.

This app could also handle platform specific assets such as audio and sounds. As well as data files etc. Allowing you to make per platform projects, without splitting up your project.

As i said, i have *planned* it. This would be something I would be interested in doing if there were enough interest. Thoughts?

#7

I have created a quick and simple alternative which reduces all the icons to one - an SVG file icon.svg - this is a lua script that leverages the free SVG editor Inkscape to create the umpteen icon files that Apple and Android need. It’s free to anyone to use/tinker with/extend etc.

http://coronadev.blogspot.co.uk/2014/04/icons.html

I quite like your idea, which is an extension of the same thing, but would allow more generality, but I’m not quite sure how you’d make the Corona build system build it, I don’t see any hooks in the Simulator ?

#8

There are no direct hooks, but there are ways of working around that. If I get time this week i’ll see what I can knock up.

#9

I’m always a little wary of sending command messages or scripts :slight_smile:

#10

Tut tut :wink: the idea would be to go as far as launching the build dialog window, after the files are copied over, but not actually trigger a build.

#11

+1.

I share your apple (and google) frustrations with the bazillion icons they require these days, along with the launch images too. I think if they were to implement this system, then launch images should also be able to be put in a separate directory.

#12

Have you looked at generating the icons via the Angry Marmot system? This has literally saved me hours and grey hairs. http://icon.angrymarmot.org.

This would at least you get up and running more quickly.

best,

Jen

#13

Indeed Angry Marmot is great but I agree with @paulscottrobson in that if we were allowed to keep these files in a subdirectory off our main project directory life would be so much better. 

#14

I’ve a lua script that generates the icons from an Inkscape SVG. It’s more about neatness ( => clarity ) than anything else. 

#15

I have been thinking about this issue today and have planned out a decent solution in the form of a helper app.

The way this would work is you would create a file in your projects directory, with the path to your icons and launch images, per platform, and when you want to do a corona build they would be copied into your projects root directory automatically for you, then removed afterward.

This app could also handle platform specific assets such as audio and sounds. As well as data files etc. Allowing you to make per platform projects, without splitting up your project.

As i said, i have *planned* it. This would be something I would be interested in doing if there were enough interest. Thoughts?

#16

I have created a quick and simple alternative which reduces all the icons to one - an SVG file icon.svg - this is a lua script that leverages the free SVG editor Inkscape to create the umpteen icon files that Apple and Android need. It’s free to anyone to use/tinker with/extend etc.

http://coronadev.blogspot.co.uk/2014/04/icons.html

I quite like your idea, which is an extension of the same thing, but would allow more generality, but I’m not quite sure how you’d make the Corona build system build it, I don’t see any hooks in the Simulator ?

#17

There are no direct hooks, but there are ways of working around that. If I get time this week i’ll see what I can knock up.

#18

I’m always a little wary of sending command messages or scripts :slight_smile:

#19

Tut tut :wink: the idea would be to go as far as launching the build dialog window, after the files are copied over, but not actually trigger a build.