On 8/28/22 20:45, Brian Milby via use-livecode wrote:
If you want to see what the JSON export looks like for a fairly small
stack, you can view this:
https://github.com/bwmilby/SvgIconTool/blob/main/smartcrumbs/SvgIconTool.livecode.sc/stackFileProperties.json
Unfortunately you will need to download and view it with something that
understands the CR line ending since GitHub doesn't. That repo has both
ScriptTracker exports and SmartCrumbs exports of the stack. The former is
designed with two things in mind: allowing changes in the scripts that are
part of a binary stack to be tracked and allowing the editing of those
scripts in an external editor (I like Atom for the linting, have not tried
the newer option). The latter looks to be a way to completely decompose a
stack into mostly text files (images being one exception) that can be
tracked (and in theory changes merged together I'm guessing).
OK - I just tried out smartcrumbs to check it out. Not quite sure what's
going on here. Outsmarted by smartcrumbs.
According to the lesson you just drag this onto a stack.
Nope.
Click the "Export Stack" button.
Stack flickers.
Did anything happen?
According to the dictionary there's an scGetPathLog().
Maybe that will give me a clue.
/My LiveCode/SmartCrumbsVCW/logs//2022-08-29
Eh?
What's this "/My LiveCode" thing? I don't have one of those.
And why is it trying to store that off my root directory?
Let's try that one again.
"Recursion limit reached"
I'll try scExportStack from the message box.
It gives "can't find handler"
OK - back to real work.
--
Mark Wieder
ahsoftw...@gmail.com
_______________________________________________
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
