Q. data stacks and app design

[Ron]

Ken, and others,
Would you care to comment on the pro/cons of maintaining a data file or a
preference file as an external text file rather than, say, a user prop of a
data/pref stack? 


Is it simply a matter of 'style' or are there distinct advantages to each?

Thanks
Ron


> From: "Ken Ray" <kray at sonsothunder.com>
> Organization: Sons of Thunder Software
> Reply-To: use-revolution at lists.runrev.com
> Date: Thu, 3 Oct 2002 21:42:28 -0500
> To: <use-revolution at lists.runrev.com>
> Subject: Re: Q. data stacks and app design
> 
> Alex,
> 
> Why don't you just maintain the data in an external text file? Then, you can
> read and write it as simply as:
> 
> put url ("file:" & tFileName) into tData
> 
> and
> 
> put tData into url ("file:" & tFileName)
> 
> Ken Ray
> Sons of Thunder Software
> Email: kray at sonsothunder.com
> Web Site: http://www.sonsothunder.com/
> 
> ----- Original Message -----
> From: "Alex Rice" <alex at mindlube.com>
> To: <use-revolution at lists.runrev.com>
> Sent: Thursday, October 03, 2002 7:35 PM
> Subject: Q. data stacks and app design
> 
>> 
>> So I think I need to use a data stack. What's the most elegant way to
>> get cards and/or stacks to write all it's state out to disk, which I
>> can go check on later from another stack, and write a report from the
>> responses? I hope this question isn't too vague. I'd be glad to tell
>> more about the application if it's not clear what I'm asking.
>> 
>> Thanks in advance!
>> 
>> Alex Rice, Software Developer