Updating Data Substacks
chipp at chipp.com
Fri Jul 12 02:56:27 EDT 2002
You could also store your data as XML outside or in a stack property. Use
one of the available XML libraries to read it. This has the added benefit of
being a 'portable' file format.
just a suggestion,
> -----Original Message-----
> From: use-revolution-admin at lists.runrev.com
> [mailto:use-revolution-admin at lists.runrev.com]On Behalf Of Dan Shafer
> Sent: Friday, July 12, 2002 12:07 AM
> To: use-revolution at lists.runrev.com
> Subject: Updating Data Substacks
> It just occurred to me that the RR model which requires me to create
> a separate stack to hold the data for my app might be an obstacle to
> product upgrades.
> My mainstack is a splasher. My substacks are a palette (which can
> change) and the primary data stack (which will change). If in my next
> rev of the product, I wish to add features (e.g., a menu or even a
> button on that stack with some new functions), I would expect to ask
> my users to replace their current stack with the new one. But that
> will, obviously, result in the loss of all their data.
> How should this work? What am I missing?
> Dan Shafer
> Technology Visionary - Technology Assessment - Documentation
> "Looking at technology from every angle"
> 831-392-1127 Voice - 831-401-2531 Fax
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the Use-livecode