building custom libs (was Re: Building a standalone)

[Marian Petrides]

Thanks for the tip, Andre!  I think this will prove very useful.

M
On Jul 5, 2004, at 2:07 PM, Andre Garzia wrote:

>
> On Jul 5, 2004, at 2:38 PM, hershbp at verizon.net wrote:
>
>> I wish I'd know how to make my own library.
>> Thanks
>
> What do you mean by 'make my own library'?
>
> If you want a image library, just create a stack (even a substack, but 
> reusing substacks is strange) drop your images in it (like, import as 
> control) then in your software, when changing for example the icon 
> property of a button, instead of selecting Revolution Icon lib or 
> MetaCard lib, choose this stack, your images will be there available. 
> Or better, change the icon prop to the ID prop of the image.
>
>
> If you want a code library there are many ways. I use this, I have a 
> simple stack called "soapdog all purpose lib" with all my common 
> handlers, I add this stack to the standalone then on startup I put 
> it's script on the back, now the handlers are available stackwide. (I 
> just coined the term stackwide and I liked it)
>
> Anyone here got more tips?
>
> Cheers
> Andre
>
>
> -- 
> Andre Alves Garzia ð 2004
> Soap Dog Studios - BRAZIL
> http://studio.soapdog.org
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>