LiveCode Forums

I have a stack where almost all the code is in the script of the main stack. I am looking for some kind of version control. To keep things simple, I am happy to have it just for that script (some 6000 lines) to be on a version control system. So what are my choices? I have tried to use Levure in the past but wonder if that is overcomplicating, considering I just need one script to keep track of.

You can export that script as a behavior, and then use any VCS that you like.
This is only applicable at newer versions of v. 9, and earlier versions of 9 have some issues with this.
The totally manual way is
bring up the properties pane for the stack
choose the advanced tab
tap the behavior button (looks like a bullseye)
choose "create behavior from script only stack"
choose "create stack using existing control script"

Less manual:
Find "scriptifier" in the LC bundle. That's a little stack Monte wrote to convert all the scripts in a stack to behaviors.

Less manual:
Use Navigator to convert your scripts to behaviors

How many people are on your team, and which VCS do they have the most familiarity with?

Thanks Mike for the info. Richard, just two people, mainly myself, but another to put in comments mostly.

I am not very familiar with any but have used bitbucket. Colleague used Github and also set up Levure once.

GitHub is pretty popular, though free accounts are limited to open source, if memory serves. Got (the underlying engine of GitHub) is open source and can be installed on nearly any server, but without the conveniences of GitHub.

If it's comments, maybe those become technical documentation and could be managed via Google Docs maybe?

github now allows private repos as well on free accounts.

Mikey wrote: ↑

Mon Sep 30, 2019 5:03 pm

github now allows private repos as well on free accounts.

Thanks, Mikey. That could be useful on some things I have coming up. I'll go look into what restrictions may apply....

ScriptTracker is an option that I created. Ideal for a single developer that wants to keep track of changes to scripts in a binary stack without converting everything to behaviors.