Right Player Approach for Cross-Platform Delivery

Ken Norris pixelbird at interisland.net
Wed Oct 29 00:09:16 EST 2003


Hello Tom,

> Date: Mon, 27 Oct 2003 21:39:22 -0500
> From: Thomas J McGrath III <3mcgrath at adelphia.net>
> Subject: Re: Right Player Approach for Cross-Platform Delivery
> 
> I've always thought it was best to keep large files as externals for
> memory issues and performance issues. It seems REV is the same.
----------
I got into this a bit late, so I apologize for redundancy.

I think it depends what you want to do. The concept is fairly universal.
Small separate clips used for effect in specific places, and probably won't
change, is a place where you will normally want to trade memory for
performance.

Larger player files, image files, and data files which you will need to open
on command will normally be external files. You wouldn't want to embed them
because they will require a sizeable chunk of memory for each, and it makes
no sense to embed copies eveywhere.

E.G., button icons in a single stack will all have different icons according
to what they do, so importing (embedding) images is appropriate.

Using a single player to play many different files means keeping the files
externally, or at least in a substack (which actually end up as connected
files in a standalone build), similar to opening QT from the DT.

As I look back, it's really just a matter of combining results with common
sense.

Ken N.



More information about the Use-livecode mailing list