Page 1 of 1

Icon Specification

Posted: Wed Feb 04, 2015 10:23 pm
by Mikey
I'm messing with building a widget, but I see I have to have an icon for it, and a retina icon. Can we have a spec. on what is required for icons? At least in the A1 documentation, there isn't anything mentioned.

Re: Icon Specification

Posted: Thu Feb 05, 2015 3:09 pm
by benjibeaumont
Hi Mike,

Thanks for this. I created a couple of bug reportw here:

http://quality.runrev.com/show_bug.cgi?id=14506
http://quality.runrev.com/show_bug.cgi?id=14507

We'll update the docs in the next release. At the moment the tools palette displays icons at whatever size is provided. The space available is 20px by 10px for non retina and twice that for retina screens. So for now, try and include the following icons:

icon.png - (fit within a bounding box of 20px x 10px)
icon@extra-high.png (fit within a bounding box of 40px x 20px)

In the next build we'll ensure that icons in the tools palette resize if larger ones are provided and also ensure that built packages are checked for icons of the appropriate size.

Warm regards,

Ben

Re: Icon Specification

Posted: Thu Feb 05, 2015 3:13 pm
by Mikey
Ben, I think you need to fix your "icon@extra-high.png"

Re: Icon Specification

Posted: Thu Feb 05, 2015 3:15 pm
by benjibeaumont
Seems to autodetect as an email... not sure why.

Re: Icon Specification

Posted: Wed Oct 07, 2015 7:40 pm
by mwieder
PLEASE change the naming convention.
This is a really stupid name for a file. For a number of reasons.

Re: Icon Specification

Posted: Wed Oct 07, 2015 7:51 pm
by trevordevore
@mwieder - how about some constructive suggestions?

Re: Icon Specification

Posted: Wed Oct 07, 2015 8:55 pm
by scrabbles
Just my interpretation, but @mwieder might be referring to conventions such as Apple's where it is <ImageName><@scaling>.<ext> eg Icon-60@3x.png

https://developer.apple.com/library/ios ... index.html

Or Microsoft's
<name>.<scale-100>.<ext>
https://msdn.microsoft.com/en-us/librar ... 65325.aspx

Re: Icon Specification

Posted: Thu Oct 08, 2015 2:37 am
by mwieder
Yeah, I was indeed referring to the "icon@extra-high.png" thing. Admittedly I haven't been aware of the iPhone/iPad guidelines thing, but I don't see how that has a bearing on widget icon naming.

Re: Icon Specification

Posted: Thu Oct 08, 2015 7:35 am
by LCMark
@mwieder: The image object uses the @<res> convention to allow you to have multiple resolutions of images (i.e. to be used on standard or retina type displays) - thus the naming extends to icons which the IDE uses.

Re: Icon Specification

Posted: Thu Oct 08, 2015 6:15 pm
by mwieder
Mark- thanks... yeah, I understand the 'why' of it, I just shudder at the naming convention. Punctuation other than underscores in filenames just doesn't seem like a good idea. And 'extra-high' doesn't tell me a thing about the png resolution.

Re: Icon Specification

Posted: Thu Oct 08, 2015 7:48 pm
by FourthWorld
mwieder wrote:Mark- thanks... yeah, I understand the 'why' of it, I just shudder at the naming convention. Punctuation other than underscores in filenames just doesn't seem like a good idea. And 'extra-high' doesn't tell me a thing about the png resolution.
It might be helpful if the documentation that describes that naming spec includes links to the relevant iOS and Android dev pages where the details are discussed, so we can know the parameters such images should conform to.

Re: Icon Specification

Posted: Thu Oct 08, 2015 8:14 pm
by mwieder
Documentation? Did I miss something?

Re: Icon Specification

Posted: Thu Oct 08, 2015 10:11 pm
by FourthWorld
mwieder wrote:Documentation? Did I miss something?
Maybe I did, as I was assuming this is documented somewhere. Isn't it?

Re: Icon Specification

Posted: Thu Oct 08, 2015 10:50 pm
by mwieder
OK... I found that there is a LCB guide available. Not easy to find or use. And can't be searched.
Got there from Dictionary | Guide | Extending LiveCode
There's no real documentation on the icon specs, just a reference to them in 'Package requirements' about a third of the way down the page. Or click on 'Packaging Extensions' under 'Extending LiveCode'.