Phil,
All of my nested stuff use local images. I use a fairly flat directory
structure, which makes it easier for me. You can use a variable to point to
the correct subdir for your nested apps, or less portable, you can directly
address your code in the subapps. if you are sharing them with multiple
programs, this method on the surface seems like poor programming, but it
will make using the subapps much easier if you are working in a corprate
enviroment and are not porting them around alot.
I use relative addressing in my code, and place my subs in the same root as
the homeapp. In my roll as consultant, this made it simple to add subactions
to customers machines... I just grab the subapp directory...copy it to thier
box.. add the switch code to the homeapp index, and voila!
I have done it both ways. I guess it depends on what you are comfortable
with.
----- Original Message -----
From: "Hulsey, James Phillip" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 20, 2000 10:49 PM
Subject: Images with nested fuseboxes
> In an effort to keep applications as portable as possible...
> Has anyone found a good way to keep images for nested fuseboxes local to
> their respective applications?
> Or, is everyone just dumping them into a local (relative to the
> parent/top-level app) or mapped directory?
>
> Thanks for the info.
> Phil
> --------------------------------------------------------------------------
----
> To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or
send a message to [EMAIL PROTECTED] with 'unsubscribe' in
the body.
__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com
------------------------------------------------------------------------------
To Unsubscribe visit
http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/fusebox or send a
message to [EMAIL PROTECTED] with 'unsubscribe' in the body.
