Pros and cons of where to store image data

[erik hansen]

--- Rob Cozens <rcozens at pon.net> wrote:

Change one character in C library source =
recompile library, relink all applications,
and distribute new copies of the application.

Change one character in Transcript library
source = distribute a new copy of the library

===
> One point not already mentioned:  If one
> modifies a referenced 
> external image, one only needs to replace the
> original image in the 
> referenced folder; if one modifies an imported
> image, the original 
> image must be deleted from and the new image
> must be imported into, 
> each stack that uses it.  (In other words, the
> Rev Dev isn't needed 
> to update referenced images but it is required
> to update imported 
> images.)
> 
> BTW, there is a third option: place the images
> in a library stack 
> that is put in use by the working stack...then
> one can replace the 
> image library stack without modifying the
> working stack.
===
two queries:
1. is there any trade-off downside to libraries?
2. are icons in buttons any different?

better make that three:
3. if one somehow copies all of the icon images
from a stack to a library stack, then erases
the originals, should that run o.k.?
it would be great to be able to change
the icon images as you progress.

=====
erik at erikhansen.org    http://www.erikhansen.org

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com