Benefits or problem splash screen

Thomas J McGrath III 3mcgrath at adelphia.net
Fri Dec 5 13:24:14 EST 2003


Rob, I came up with three questions after I wrote two. Oh well, I do 
that alot.

If I read you correctly my "Splash Screen" is built and has the Rev 
engine built into it. I then put my non-built rev stacks into the 
distribution folder were they will be called by the "Splash Screen" 
app. OK that makes sense to me. But all of the rest of my stacks in 
this case are in the Main stack so I would have a built "Splash Screen" 
app and a Main stack with substacks in it. Is this OK?

I worry about the filePath for my Main stack being 'changed' by the 
"Splash Screen" apps location IE:

Distribution Folder
	Splash Screen.app
	Main.rev
	Images Folder
		img1.png
		img2.png
		etc.

OR

Distribution Folder
	Splash Screen.app
	Needed Files Folder
		Main.rev
		Images Folder
			img1.png
			img2.png
			etc.

It is hard enough keeping track of folder path in development and then 
keeping it right in standalones.

Thanks for your insight Rob

Tom

On Dec 5, 2003, at 10:08 AM, Rob Cozens wrote:

> Hi Tom,
>
>> I created a stack with a lot of substacks and NOW decided that I will 
>> need a splash screen before the Main stack loads.
>>
>> I have two questions:
>
> Three, actually; but that's OK.    :{`)
>
>> Q3: When Building the standalone how would I deal with these two 
>> stacks? Should they be separate builds? If not How/What should I do 
>> about it. Should I use the "Files for inclusion" in DB? How will that 
>> affect the MAIN mainstack? What about the "Make mainstack" in DB? How 
>> will that affect my MAIN main stack?
>>
>
> The "traditional" approach is to identify the splash screen as the 
> mainStack to the Application Builder, identify all other stacks to be 
> included, and specify a folder to contain the "auxiliary" stacks.
>
> As a practical matter, I personally find this cumbersome and difficult 
> to maintain--especially with the advent of Mac OS 10 application 
> bundles and for standalones that utilize files that are not stacks.
>
> I create a distribution folder containing everything the application 
> needs (except Revolution items which are bundled into the standalone). 
>  I identify ONLY the splash screen stack and any needed Revolution 
> resources to the Distribution Builder, and drag the finished 
> standAlone or application bundle into my distribution folder.  Note 
> that this approach also facilitates easy updates of component files & 
> stacks: just drag the new version into the distribution folder.
> -- 
>
> Rob Cozens
> CCW, Serendipity Software Company
> http://www.oenolog.net/who.htm
>
> "And I, which was two fooles, do so grow three;
> Who are a little wise, the best fooles bee."
>
> from "The Triple Foole" by John Donne (1572-1631)
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>

Macintosh PowerBook G-4 OSX 10.3.1, OS 9.2.2, 1.25 GHz, 512MB RAM, Rev 
2.1.2


Advanced Media Group
Thomas J McGrath III	• 2003 •	3mcgrath at adelphia.net
220 Drake Road, Bethel Park, PA 15102





More information about the Use-livecode mailing list