Levure update 0.9.5

[Trevor DeVore]

Hi Graham,

1) You do not need to scriptify (move code into script only stacks) your
stacks to use them in Levure. Levure supports an organizational structure
(the `ui` folder in Levure) which makes it easy to organize binary stacks
that use script only stacks as behaviors.

2) You are not required to use Git in order to use Levure. Levure helps you
organize your code so that you can benefit from version control. It doesn’t
require it.

3) You can still benefit from using Levure if you don’t use script only
stacks or git yet. Levure provides a powerful packaging system for
packaging your apps for distribution. Helpers allow you to drop in
functionality that your app may need such as Prefernces, Inno Setup,
DropDMG, etc. (On a somewhat related note I’m currently updating SQL Yoga
to work as a helper which will simplify its usage considerably as all of
the configuration is done with YAML files.)

What I’ve done in the past when converting an app is move my stacks into
the appropriate Levure folders without worrying about scriptifying them. I
then move any app initialization code into the appropriate handlers in the
Levure `app.livecodescript` file.

Once the app is working again then I go back and scriptify stacks as
needed. Libraries that don’t use any internal custom properties are easy to
convert as are front and back scripts. You can then slowly go through each
folder in the `app/ui` folder and move the scripts into a `behavior` folder
that sits along each stack. No rush though.

—
Trevor DeVore


On Mon, Feb 19, 2018 at 4:33 AM Graham Samuel via use-livecode <
use-livecode at lists.runrev.com> wrote:

> I have not tried to look at Levure until now, but since I am in
> difficulties trying to create a user-oriented update system (the kind that
> professionals use Sparkle for on Mac, and other techniques on other
> platforms), I have some hopes (from previous emails from Trevor) that
> Levure might help me. However, on first looking at the wiki, I think that
> what Levure needs is a big commitment to work in a specific way - a good
> way, bien sure, but not the way us primitive old coders have been doing for
> the last few decades. This means, if I am right (and I could so easily not
> be) that a ‘traditional’ app development, where stacks contain code in
> various forms, could not be retrofitted to the Levure environment. Rather,
> one would have to start from scratch, or at the very least do a great deal
> of restructuring of such an existing app, so that pretty much all the code
> is script-only. Plus of course learning the philosophy of Levure, and
> feeling comfortable with Github...
>
> Can anyone comment on this enough to clear my head a little?
>
> TIA
>
> Graham
> (A very old coder, who in his twilight years is trying to stick purely to
> LC rather than try to recycle his misspent youth, where several now extinct
> low- and high-level languages had to be mastered).
>
> > On 16 Feb 2018, at 00:42, Trevor DeVore via use-livecode <
> use-livecode at lists.runrev.com> wrote:
> >
> > On Thu, Feb 15, 2018 at 4:30 PM Mike Kerner via use-livecode <
> > use-livecode at lists.runrev.com> wrote:
> >
> >> Check the wiki instead of the readme.md.  The documentation is
> extensive.
> >> https://github.com/trevordevore/levure/wiki
> >
> >
> > The wiki is definitely where you want to end up. The readme has a short
> > description and points users to the wiki documentation to learn more.
> >
> > —
> > Trevor DeVore
> >
> >> <https://github.com/trevordevore/levure/wiki>
> > _______________________________________________
> > use-livecode mailing list
> > use-livecode at lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode