make standalone (was 2 quick questions)

[Bob Sneidar]

The caveat about saving anything in a compiled rev app is that no runtime app can be modified. Otherwise, anyone could interject their own malicious code and you would run that code simply by launching the app next time you ran it.

Normally this would not be a problem for apps that only used cards as forms as a front end to a database. But you want your app itself to contain the data as card, old HyperCard style. 

So the way to write this for an app is to have the main stack that gets compiled launch the actual stack that is your app. Some have the main stack be a kind of splash screen that shows for a few seconds, then hides itself and opens the real stack which you would add as a file that gets included with the "main" app. Make sense?

Bob

Sent from my iPad

On Jun 18, 2010, at 5:37 PM, Mark Smith <Mark_Smith at cpe.umanitoba.ca> wrote:

> Funny you should mention that. My first app is something similar... a notepad (just for its simplicity and completeness). It has (appropriately) a text field, cards are numbered (so I know how many there are), and buttons for forwards, backwards, begin, end, create, delete and save notes. Now, I want to compile to a standalone but I don;t understand the instruction to split my stack so I can save the notes? I just have the one stack. Any suggestions?
> 
> Mark Smith
> 
> ________________________________________
> From: use-revolution-bounces at lists.runrev.com [use-revolution-bounces at lists.runrev.com] On Behalf Of Peter Brigham MD [pmbrig at gmail.com]
> Sent: Thursday, June 17, 2010 6:33 AM
> To: How to use Revolution
> Subject: Re: 2 quick questions
> 
> On Jun 16, 2010, at 4:17 PM, Mark Smith wrote:
> 
>> Hi Peter, no doubt the day will come. Thanks for the tip (I'm filing
>> these away in a word document. Mark Schonewille will undoubtedly
>> need something to base his FAQ on!)
>> 
>> -- M
> 
> I save my collected tips in a Rev stack. Searchable. And poetically
> appropriate.
> 
> -- Peter
> 
> Peter M. Brigham
> pmbrig at gmail.com
> http://home.comcast.net/~pmbrig
> 
> 
>> -----Original Message-----
>> From: Peter Brigham MD
>> Sent: Wednesday, June 16, 2010 8:27 AM
>> 
>> A useful nugget -- if you need to get the current card of a stack that
>> is not the frontmost stack, use the undocumented term
>> "currentcard" (note lack of space character) -- as in:
>> put the currentcard of stack "myStack" into cc
>> which gets you something like:
>> card id 1002
>> 
>> "Currentcard" is equivalent to "this card" but works with any open
>> stack, returning the id of the card that is currently showing in that
>> stack. In your case this is unnecessary, as you are apparently needing
>> to deal only with the one stack, so "this card" will do fine.
> 
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution