On 6/4/11 2:50 PM, Keith Clarke wrote:

(I hope it's OK to mention here that the very useful) Summer Academy
project demonstrates storing all of a project's images centrally
within a substack - an approach very familiar to those of us from a
web background. A sound approach but these images are then invisible
to the icon inspector when the time comes to assign them (which is
perhaps why the webinar glossed over that by not using the icon
chooser). It's a bit surreal that RunRev would propose an approach
that suggests best practice that highlights a flaw in the IDE?!?

It's just a difference in personal style. There are lots of ways to do things in LiveCode and which way you choose depends on how you like to work. Both methods you mention are legitimate.

Me personally, I don't like adding extra substacks just for resources, so I tend to put icons in unplaced groups in the mainstack if they need to be accessible all over the stack. This is what the engine has done with imported HyperCard stacks and their icons for the last fifteen years or so, and it's a nice, tidy method.

On the other hand, if an icon is only going to be shared among buttons on a single card, I put the image on the card and hide it. I tend to treat images a little like handlers; put them in a common location closest to the objects that will need them.

While both my methods do enable the library to work, it's funny that I almost never use the icon library. The image ID is easy to see in a number of places, and I usually just type it into the icon field.

So that's a couple of other ways. I'm not sure any of them are "best practice", they all work. There's no particular advantage of one method over another, do whatever works for you.

--
Jacqueline Landman Gay         |     jac...@hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to