Navigator now supports converting controls to script-only stack behaviors

[Trevor DeVore]

On Thu, Jan 25, 2018 at 3:36 AM Geoff Canyon via use-livecode <
use-livecode at lists.runrev.com> wrote:

>
> I have a fix coded, but I'm in the middle of another update, so I will
> update the whole thing tomorrow morning. (This is the sort of thing GitHub
> is supposed to be good for, right? Heh -- need to figure that out...)


A couple of quick tips. Some of the vocabulary may be new. Just google each
concept and you will find lots of info. Git is really confusing at first
and then one day it isn’t and you wonder how you ever lived without it.

Look into branching. A simple approach for an individual is that your
master branch has the stable version of your app. You work on each feature
in a separate branch that you then merge into master when it is ready.

Whenever you want to make a new public release of your app tag the commit
in master that has the release version. This allows you to easily check out
a branch with that exact version of your app if you need to in the future.

If you want to keep your master branch clean when merging other branches in
(not too many commits) look into interactive rebasing. Interactive rebasing
can be used to squash a bunch of commits in a branch down to one (or more).
That way when you merge a feature branch into master it only appears as one
commit, even if you made 30 commits while working on the feature.

Trevor DeVore
ScreenSteps

>