Editing Large Scripts is Faster

Monte Goulding monte at sweattechnologies.com
Tue Sep 8 23:32:10 EDT 2015

> On 9 Sep 2015, at 10:37 am, Richard Gaskin <ambassador at fourthworld.com> wrote:
> If we can just get a review process in place for community enhancements to the IDE to be included in the main install, everyone wins.

Are you talking about both script and object property changes or just script? If it’s just script (at least for starters) then let me make the following suggestion:

- The user that wants to make the change checks out the development head of the livecode version they want to update. For example develop-7.0 in this discussion. 
- They build and run (which will load the ide from the repo). 
- They open the script they want to edit and copy it. 
- They go to github and create a gist with
  - the first line being the long name of the objec
  - second line being the commit reference for the previous change to the file before this script version (git log -n 1 — stackname.livecode)
  - the rest of the gist is the script from that version of the stack
- They edit the script in livecode and get it how they want
- They copy the script again and go and add a revision to their gist
- They open up a bug report and link to the gist

The LiveCode team can see the exact changes made on the revisions page like this:
https://gist.github.com/montegoulding/d0e3b0dc0fb5a94ff2d7/revisions <https://gist.github.com/montegoulding/d0e3b0dc0fb5a94ff2d7/revisions>

They can comment and discuss further changes required for it to be copied in.

This way if there is a new commit between the one the user based the gist on and the most recent in the repo then the team know that they need to ask the contributor to base the change off the latest or merge them.



More information about the use-livecode mailing list