True, but with properties, I can envision a use case for persistent values between sessions. This is quite separate from GUI objects. By saving and reloading properties of a script only stack, everything is still text file only based.
Bob S On Apr 4, 2020, at 11:17 AM, Richard Gaskin via use-livecode <use-livecode@lists.runrev.com<mailto:use-livecode@lists.runrev.com>> wrote: Bob Sneidar wrote: > Hmmm… If that is the case then theoretically, on closeStack the new > properties could be arrayEncoded and saved to disk, and then on > openStack they could be read and then arrayDecoded and reset again. Stacks can also contain controls, each of which can be expressed as an array of properties. You could craft an array-based format to allow storage and recreation of even complex GUI stacks. What you'd have is a binary file dependent on a lot of scripted code. Meanwhile, we already have a binary format handled robustly in the compiled object code of the engine. :) -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web _______________________________________________ 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
