Dialogs in library organization

[Monte Goulding]

> > Yep... The distribution builder will always use the running engine for
> > that
> > platform and engines in the engines folder for other platforms.
>
> I've decided this is an inconvenience, but one I can work around.
>
> One of the customizations I'd like to do is change something in the app
> bundle so I see version info in the name on the doc.  I think it was
> you who told me how to do it Monte, but I forgot and hadn't gotten back
> to that.  Would that affect its use as the prototype?

You might want to use an alias for that. Make an alias. Rename it with the
version number. Then drag to the dock.
>
> I've been mocking up app bundle layout there, so that has to be done
> some other way.
>
> On the other hand, one has to fiddle with the bundle anyway.  If
> libraries are included in a build, they are put in the MacOS
> subdirectory, which Apple has assigned for dynamically loadable stuff.

Wouldn't you class stackFiles as dymanically loadable stuff? No matter what
Apple says it's far simpler for Revers to think of the MacOS directory as
the  application directory and put all our files there. Having one directory
structure for OS X and another for all other platforms just doesn't make
sense.

Cheers

Monte