"Should be"? Why?
Do you have a multi-developer team whose workflow includes dependencies on version control tools designed for other languages?
That's why script-only stacks were invented.
"Should be"? Why?
That's an opinion. Or did you see that mentioned in a document from the LC team?multi-developer team (…) That's why script-only stacks were invented.
I was a contractor with LiveCode before v1.0. I was the LC Community Liaison during the open source years (2013-2021). I've read pretty much every post to the LiveCode mailing list since it was started just after the turn of the century, including many discussions of version control.
I know from direct firsthand experience that the engine can open stack files, and once opened they behave just like any other stack file.Not many people around here know for sure (doc…) the answer to my question: can I use script-only stacks as plugins?. I asked in case someone here was able to point to some document, blog, whatever, from the LC team.
I've never seen the corn fields of Wisconsin, because I've never lived there. But when friends who do live there tell me about them, I have no reason to doubt what they're telling me.BTW, I see no link between script-only stacks and multi-developpers teams…
The additional space is negligible (less than 1k IIRC; you can test it by just creating a new stack with nothing in it and saving it). If you need any persistent GUI elements or custom properties, those would require scripts to instantiate, which are generally much larger than their finished binary object form.One might think of other virtues of script-only stacks; from the top of my mind: smaller space, ability to use any text editor… which have nothing to do with multi-developer teams.
I agree with Richard that "diffing" can be quite useful.FourthWorld wrote: ↑Thu Aug 04, 2022 10:59 am....
I'll close with a juicy trivia tidbit as a reward for those who read this long post all the way to the end:
At the heart of git are two key functions, diff and merge.
Diff takes two blocks of text and outputs a concise listing of the differences between them.
Merge takes the master script and the diff list and produces the changed script.
The benefit of using merge rather than just using the newer file is that you can edit the diff file to merge only the changes you want to accept, leaving other things as they were.
Both of these have quietly found their way into the LC engine, in the form of gitDiff and gitMerge functions in the LiveCode Script language.
If one had enough time on their hands they could use those to make a wide range of useful and convenient GUI version control tools.
Code: Select all
DiffCompare DiffCompareFiles DiffPatch
Why remove it? There would be no practical consequences. There are 71 forks of that repository currently. Who should gain what from removing the original?
Presumably for the same reason as the download page suddenly lost all the Open Source versions: because theyWhy remove it?
GitHub for one. That's a lot of space for a project that is no longer active.LostinLC wrote: ↑Sun Aug 07, 2022 12:18 pmWhy remove it? There would be no practical consequences. There are 71 forks of that repository currently. Who should gain what from removing the original?
That's what most of the engine is written in.
And yet:richmond62 wrote: ↑Mon Aug 08, 2022 8:33 amRead it and, erm, cough:
https://www.theregister.com/2022/08/04/ ... on_policy/