The Case For A RunRev Player (was "Stack and Substacks")

[Rob Cozens]

>any changeable information must be stored outside of the application itself

>Actually, the application can run on all platforms...its just that any
>changes to the data won't be there the next time it is started.

If there were a RunRev Player app, this consideration would be 
non-sequitur and main stacks would not have to be "flash screens" 
that open the real working stack(s).  In building a splash screen to 
open the working files and contain the MC engine, each of us is, in 
effect, creating a custom RunRev Player.  With each new app, we do it 
again.

A generalized RunRev Player would make it unnecessary to design RR 
mainStack "apps" differently from HyperCard stacks, and an extensible 
Home stack would provide a framework for integrating multiple RR 
"applications".

Why hasn't anyone built a generalized RunRev Player?
-- 

Rob Cozens
CCW, Serendipity Software Company
http://www.oenolog.com/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)