Where goes stacks, included stacks and externals? (was Dialogs inlibrary organization)
dsc at swcp.com
Thu Feb 5 13:21:00 CST 2004
On Thursday, February 5, 2004, at 10:31 AM, Rob Cozens wrote:
> Why allow multiple placement options for libraries & other files?:
> 1. Some O/S environments dictate that modifiable files cannot exist
> in the same folder as the application.
Right. I limited my focus on stacks that would not be modified, but
this provides a more general approach. A stack should know whether the
stack it needs is modifiable or not, though.
> 2. Some people might decide to place a library stack inside an OS X
> application bundle to achieve a monolithic structure, while other
> might chose to place the library in the folder containing the
> application bundle so it is visible to the user for replacement
> without opening the bundle itself.
Right. I made the distinction of shallow and deep and the using stack
needed to know. Your way is better in that it does not need to know.
I'd look deep first.
Is there a performance impact?
(The subject of the mail I got from you through the list got strange
accent marks added, somehow.)
Now, if you got Chipp's Really Cool 3D Rendering stack that used Dar's
Totally Adequate High Precision Decimal Math stack, how would you
expect to use them? Just drop them into your folder scheme someplace
and then 'start using' Chipp's with your general start-using handler
and assume the math gets loaded? Chipp's library might not know about
your cool start-using handler.
More information about the use-livecode