[off]sublimeText update

Brian Milby brian at milby7.com
Thu Mar 14 12:53:04 EDT 2019


I noticed that the plugin was a single file and wondered how you did that.  When I convert Navigator, I create a single sub stack and map each behavior to a new button with the same name as the script only stack name.  I’ll need to read your script a little more closely to see what is happening.

Thanks,
Brian
On Mar 14, 2019, 11:43 AM -0400, Trevor DeVore via use-livecode <use-livecode at lists.runrev.com>, wrote:
> On Wed, Mar 13, 2019 at 12:30 PM Brian Milby via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
> >
> > One area where I prefer binary stacks is plugins. It seems cleaner to
> > keep the code self contained inside the IDE. I actually consolidate
> > Navigator to a single binary file on my systems and do not notice anything
> > different in operation.
> >
>
> I prefer binary stacks for plugins as well. I'll offer up one approach I
> have been experimenting with recently for a plugin developed using Levure.
> While I develop the plugin in Levure, I package it up into a single binary
> stack for distribution. Aside from the benefits of tracking development
> changes using Script only stacks, I like that I never have to worry about
> whether or not I've exported/imported scripts and that I only create the
> binary version when I'm ready to release.
>
> The repo can be found here:
>
> https://github.com/trevordevore/bakers-assistant
>
> The script that creates the binary stack for distribution can be found here:
>
> https://github.com/trevordevore/bakers-assistant/blob/master/app/package%20bakers%20assistant.livecodescript
>
> --
> Trevor DeVore
> ScreenSteps
> www.screensteps.com
> _______________________________________________
> 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



More information about the use-livecode mailing list