> They already are different. On Windows, stacks included in
> applications are put in the same folder as the app, but on OS X they
> are put down inside the applications.
Not if you think of the MacOS folder as the application directory. Don't
forget the application bundle is just a set of fold
On Wednesday, February 4, 2004, at 08:42 PM, Monte Goulding wrote:
Not if you think of the MacOS folder as the application directory.
Don't
forget the application bundle is just a set of folders.
I don't think most users would think of it that way. It is really
handy for me, of course.
I don't
Another scheme would be to have all stacks find (create paths for)
needed stacks based on a location relative to that stack.
Dar,
Take this one step further by creating a generalized stack search
handler that will look in several different folders, relative to the
main app folder and/or in Rev'
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 modi
On Thursday, February 5, 2004, at 01:14 PM, Rob Cozens wrote:
In my designs, a standalone generally starts using all libraries it
needs on startUp or preOpenStack, so the time taken to determine the
actual location of the libraries is factored into the "application
startup delay."
OK. So in th
On 2/5/04 4:14 PM, Dar Scott wrote:
On Thursday, February 5, 2004, at 01:14 PM, Rob Cozens wrote:
In my designs, a standalone generally starts using all libraries it
needs on startUp or preOpenStack, so the time taken to determine the
actual location of the libraries is factored into the "appli
On Thursday, February 5, 2004, at 03:38 PM, J. Landman Gay wrote:
I am starting to lose track of what we are talking about, but maybe
this helps: you can start using a stack any number of times, but it
only actually gets used once. So it doesn't matter who starts to use
what when.
But what if i
On Thursday, February 5, 2004, at 01:14 PM, Rob Cozens wrote:
In my designs, a standalone generally starts using all libraries it
needs on startUp or preOpenStack, so the time taken to determine the
actual location of the libraries is factored into the "application
startup delay."
So if a libra
On 2/5/04 4:57 PM, Dar Scott wrote:
But what if it is not in the expected location?
Library A' from vender A needs library B' from vender B. Library A' has
some notion where B' is and refers to it there. Developer C puts B' in
a different location and then makes the developer's app C' start u
On Thursday, February 5, 2004, at 04:14 PM, J. Landman Gay wrote:
But what if it is not in the expected location?
Library A' from vender A needs library B' from vender B. Library A'
has some notion where B' is and refers to it there. Developer C puts
B' in a different location and then makes t
On 2/5/04 5:52 PM, Dar Scott wrote:
On Thursday, February 5, 2004, at 04:14 PM, J. Landman Gay wrote:
I don't think there is an official established procedure, but I'd put
all my library stacks together in one folder. When it was loading
time, I'd set the directory to that folder and start usin
11 matches
Mail list logo
