clones and scripts

[Thomas McGrath III]

Ok, 1 and 2 makes sense to me.

Now 3 is an actual stack file and not a part of a standalone - i.e. it 
can be saved with changes etc.

Then can the separate file on disk be opened with the main stack - 
right? etc.

Then the main stack will keep a list of these cloned project files. to 
be opened when needed.

Thank you Jeanne for understanding what I am trying to do.

Tom

On Mar 31, 2005, at 2:24 PM, Jeanne A. E. DeVoto wrote:

> I'd do it this way:
>
> 1. All substantive code routines are stored in the standalone's main 
> stack script (which might as well be the splash screen). Because the 
> splash screen is the main stack of the standalone, it is always in the 
> message path whenever the standalone is running.
>
> (Depending on the complexity of your code, you might want to put some 
> of the code into other objects and use the insert command to make 
> those objects into backscripts or frontscripts. But for a relatively 
> simple project, putting it all in the main stack script will work 
> without the need for backscripts, frontscripts, or start using.)
>
> 2. The standalone includes this main stack, plus one substack. The 
> substack is a project window blank template. This template is never 
> actually seen by the user; instead, it is cloned every time you need a 
> project window.
>
> 3. When the user creates a new project, you clone the template 
> substack. This clone can be saved as a separate file on disk.
> -- 
> jeanne a. e. devoto ~ revolution at jaedworks.com

Thomas J. McGrath III
SCS
1000 Killarney Dr.
Pittsburgh, PA 15234
412-885-8541