Team Development / Exporting stuff to text files
len-morgan at crcom.net
Tue Mar 4 06:56:19 EST 2008
Perhaps the way to solve this would be to dump all the properties of the
template objects of this stack and then dump only properties of the
objects that are different than the templates. This buys you a couple
1) You only dump what's different
2) If someone has modified their template objects for a particular
project (say text font) and most of the objects in the stack used this
new object instead of the one that comes with Rev out of the box, you'd
have a smaller export file.
3) It would give you a fairly simple way to make wholesale changes to a
stack by modifying the text file and reloading. For example, if you
wanted to change the type face completely across an app, if you exported
the stack as text, then changed the type face in the saved text file
(only on the template object(s)), then reloaded, you'd end up changing
all of the objects by changing one line! Handy.
Richmond Mathewson wrote:
> I wrote (probably in a moment of fairly naive
> "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.
> 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 at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode