Relative Paths

[Dar Scott]

On Wednesday, April 7, 2004, at 08:12 PM, Monte Goulding wrote:

>> It took a while for me to get into the Rev notion of splitting apps
>> into a small app and lots of support stacks, now I go the other way?
>
> The other way? I don't get that. All these complex relationships are
> transferred into your app. You can now have whatever relative paths 
> you want
> and they will be retained when you build your app.

I'm willing to try it the recommended way, if Rev will just explain it.

This is what I've inferred so far from the clues.

1.  The relationship among stacks and externals is static and fixed at 
standalone build time.
2.  That relationship is specified by the stackFiles and externals in 
the stacks and substacks.
3.  One stack is put into the app and all other stacks are placed 
relative to the core excutable
     based on stackFiles of all stack recursively found, folders built 
as needed.
4.  All externals are static.  The externals property of all stacks are
     adjusted so that all externals go in one place.  When the app is 
built,
     externals must be in the same folder as the model revolution app, 
depending
     on the target platform.
5.  The final product is either a bundle for OS X or a collection of 
files for
     others.

Did I get that right?

Dar Scott