The way I've done it in the past is to have a "template" for each
type of object that contains the default values. This gets stored
once for each object type, then for each object just send the
properties that have changed from the default.
All the Best
Dave
On 4 Mar 2008, at 09:07, Richmond Mathewson wrote:
I wrote (probably in a moment of fairly naive
euphoria):
"it would be perfectly possible to write a
description in the text format and write a reader to
reimport that to make a stack!"
Well, I suppose it would.
BUT
It would probably then be necessary to spit out
details of ALL properties for each object (472 last
time I looked) which would be both silly and involve a
lot of redundancy . . .
feedback required . . .
sincerely, Richmond
____________________________________________________________
A Thorn in the flesh is better than a failed Systems Development
Life Cycle.
____________________________________________________________
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html
_______________________________________________
use-revolution mailing list
use-revolution@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
