That's been mulled over before. It's a huge undertaking. Arrays in properties 
would have to be arrayEncoded of course, which makes putting it all in a flat 
text file extremely problematic. Where does the array data begin and end you 
see? 

An XML file would be better. 

Bob S


> On Mar 13, 2019, at 07:58 , Mike Kerner via use-livecode 
> <use-livecode@lists.runrev.com> wrote:
> 
> Navigator also has an exporter, and Monte wrote "Scriptifier", which is
> included in the LC bundle, for exporting scripts to SOS's.  Once they're in
> SOS's, there's no reason to put them back in the stack, since you can edit
> them using the LC SE or in an external editor.  I thought about writing
> something to export the properties of objects in a stack into text files,
> and then at startup using that information to build the stack, but that's
> as far as it's gotten is thinking about it.


_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Reply via email to