Updating Data Substacks

[Dan Shafer]

>Recently, Dan Shafer wrote:
>
>>>  Good) Keep your data separate from the UI.  This way you can update the UI
>>>  independently of the data.
>>
>>  Thanks for the fast reply, Scott.
>>
>>  But this would require storing it in a text file and managing all the
>>  data manipulation stuff or alternatively using a database, right? If
>>  I have to do those things to keep data from being munged when I
>>  upgrade the app, I might just as well use a conventional programming
>>  environment! Transparency of data storage is crucial to stackware
>>  applications.
>
>If I understand your correctly, the answer is no.  Data can be stored in a
>stack, in fields, user props, whatever you want.  Personally, I use mirrored
>controls in the UI stack and the data stack -- this makes it easy to keep
>track of where the data is going.  To write/store the data, I open the data
>stack invisibly and write any data changes/updates in the UI stack to the
>data stack on closeField messages.

That sounds like an efficient way of doing things. that should make 
it unnecessary to change the data stack unless I make some 
fundamental change in data structures, which I don't anticipate.

Thanks. This feels like it might work, though it is less and less 
like HyperCard!

>Regards,
>
>Scott Rossi
>Creative Director
>
>Tactile Media, Multimedia & Design
>Email: scott at tactilemedia.com
>Web: www.tactilemedia.com
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/use-revolution


-- 
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
Dan Shafer
Technology Visionary - Technology Assessment - Documentation
"Looking at technology from every angle"
http://www.danshafer.com
831-392-1127 Voice - 831-401-2531 Fax