I wrote an XML exporter about fifteen years ago. I don't think I have a copy of it anywhere, and of course it probably would break with all the changes since then. But it wasn't *that* complex; Navigator has built-in code to return a list of all the controls within a given group/card/stack, and separately all the properties/custom properties etc.
gc On Wed, Mar 13, 2019 at 10:30 AM Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > My stack is a different take on the problem. It allows the benefit of > tracking the scripts in a VCS while retaining the convenience of a binary > stack file. It also allows easy editing of scripts outside of the IDE > without moving to SOS. I’m still not convinced that SOS use makes sense > all of the time (why put a single level of indirect reference in every > object if the script isn’t shared for example). Even though I name them > and format them like a valid SOS, I do not convert them to actual behaviors. > > One area where I prefer binary stacks is plugins. It seems cleaner to > keep the code self contained inside the IDE. I actually consolidate > Navigator to a single binary file on my systems and do not notice anything > different in operation. > > Monte had another project that did export an entire stack into a > collection of text files compatible with VCS. His solution allowed > multiple developers to work on a stack using the VCS processes to merge > work. That is much more ambitious than my goal. My solution would only > facilitate distributed work on the scripts of a stack with someone being > the gatekeeper of the binary stack file. > > Exporting properties of each object would not be that difficult to add, > but doing so in a way compatible with VCS would take a bit of thought. > Monte would encode binary stuff into an ASCII friendly format. [I do > include a few items as comments at the top of each script (behavior, long > name/ID).] Format could be XML, JSON, YAML, some new TLA format to appear > this year... > > Thanks, > Brian > On Mar 13, 2019, 10:59 AM -0400, 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. > > > > On Wed, Mar 13, 2019 at 10:28 AM Brian Milby via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > I have a tool that exports the scripts of a stack and can facilitate > > > editing in any external editor. I want to hook it up in Atom like ST, > but > > > have not figured out how to rewrite the module in JS. ScriptTracker > works > > > by watching a directory for changes to the files. The ST plugin works > by > > > sending messages to a server process running in the IDE. > > > > > > forums.livecode.com/viewtopic.php?f=77&t=31079 > > > github.com/bwmilby/lc-misc/tree/master/ScriptTracker > > > github.com/bwmilby/lc-misc/blob/master/ScriptTracker/ScriptTracker.md > > > > > > Thanks, > > > Brian > > > On Mar 13, 2019, 10:18 AM -0400, Mike Kerner via use-livecode < > > > use-livecode@lists.runrev.com>, wrote: > > > > The new sublimeText update dropped this morning, and it's pretty > sweet. > > > > It now has things like git status integration, which is very cool. > > > > It would be really cool if we could get better integration between > > > external > > > > text editors and ST. The ST kluge works great for updating scripts > live > > > in > > > > LC, except when it doesn't, and I don't think we have a way to do it > with > > > > Atom, yet. > > > > It would also be cool if we had a better way to have stack files be > > > > represented as text files instead of binary files for easier version > > > > control and editing. > > > > Anyway, > > > > https://www.sublimetext.com/blog/articles/sublime-text-3-point-2 > > > > > > > > -- > > > > On the first day, God created the heavens and the Earth > > > > On the second day, God created the oceans. > > > > On the third day, God put the animals on hold for a few hours, > > > > and did a little diving. > > > > And God said, "This is good." > > > > _______________________________________________ > > > > 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 > > > _______________________________________________ > > > 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 > > > > > > > > -- > > On the first day, God created the heavens and the Earth > > On the second day, God created the oceans. > > On the third day, God put the animals on hold for a few hours, > > and did a little diving. > > And God said, "This is good." > > _______________________________________________ > > 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 > _______________________________________________ > 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 _______________________________________________ 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