Re: [off]sublimeText update

[Trevor DeVore via use-livecode]

On Tue, Mar 26, 2019 at 11:08 AM Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> The watcher would also be a nice addition to the fileBrowser
> dataViewTree...
>

Indeed it would!

It would be great it someone could wrap fswatch up in an LCB extension that
people could easily install and include with their projects. It would be
useful in a number of cases.

-- 
Trevor DeVore
ScreenSteps
www.screensteps.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Mike Kerner via use-livecode]

The watcher would also be a nice addition to the fileBrowser dataViewTree...

On Tue, Mar 26, 2019 at 10:25 AM Ralf Bitter via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Trevor, this looks very promising. Thanks
> for looking into it.
>
> Ralf
>
>
> > On 26. Mar 2019, at 15:05, Trevor DeVore via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > On Tue, Mar 26, 2019 at 8:28 AM Ralf Bitter via use-livecode <
> > use-livecode@lists.runrev.com >
> wrote:
> >
> >>
> >>> On 13. Mar 2019, at 15:17, Mike Kerner via use-livecode <
> >> use-livecode@lists.runrev.com >
> wrote:
> >>>
> >>> The ST kluge works great for updating scripts live in
> >>> LC, except when it doesn't, and I don't think we have a way to do it
> with
> >>> Atom, yet.
> >>
> >> There are definitely ways to do it in Atom too.
> >> Here is how I managed to send notifications to
> >> a Levure application running in the LiveCode IDE
> >> using Atom:
> >>
> >>  ...
> >>
> >
> > Thanks for sharing this Ralf!
> >
> > As I read over this thread it reminded me that ideally the LiveCode IDE
> > would be watching files/folders rather than having to be notified by the
> > text editor. One of these days I want to investigate using something like
> > fswatch  https://github.com/emcrisostomo/fswatch>> to monitor for changes
> > and then reload them in the LiveCode IDE. Since a Levure app knows where
> > all of the project files are stored there is a straight forward way of
> > knowing which folders to monitor.
> >
> > --
> > Trevor DeVore
> > ScreenSteps
> > www.screensteps.com 
> > 
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>


-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Ralf Bitter via use-livecode]

Trevor, this looks very promising. Thanks
for looking into it.

Ralf


> On 26. Mar 2019, at 15:05, Trevor DeVore via use-livecode 
>  wrote:
> 
> On Tue, Mar 26, 2019 at 8:28 AM Ralf Bitter via use-livecode <
> use-livecode@lists.runrev.com > wrote:
> 
>> 
>>> On 13. Mar 2019, at 15:17, Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com > wrote:
>>> 
>>> The ST kluge works great for updating scripts live in
>>> LC, except when it doesn't, and I don't think we have a way to do it with
>>> Atom, yet.
>> 
>> There are definitely ways to do it in Atom too.
>> Here is how I managed to send notifications to
>> a Levure application running in the LiveCode IDE
>> using Atom:
>> 
>>  ...
>> 
> 
> Thanks for sharing this Ralf!
> 
> As I read over this thread it reminded me that ideally the LiveCode IDE
> would be watching files/folders rather than having to be notified by the
> text editor. One of these days I want to investigate using something like
> fswatch  > to monitor for changes
> and then reload them in the LiveCode IDE. Since a Levure app knows where
> all of the project files are stored there is a straight forward way of
> knowing which folders to monitor.
> 
> -- 
> Trevor DeVore
> ScreenSteps
> www.screensteps.com 
> 


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Trevor DeVore via use-livecode]

On Tue, Mar 26, 2019 at 8:28 AM Ralf Bitter via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> > On 13. Mar 2019, at 15:17, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > The ST kluge works great for updating scripts live in
> > LC, except when it doesn't, and I don't think we have a way to do it with
> > Atom, yet.
>
>  There are definitely ways to do it in Atom too.
>  Here is how I managed to send notifications to
>  a Levure application running in the LiveCode IDE
>  using Atom:
>
>   ...
>

Thanks for sharing this Ralf!

As I read over this thread it reminded me that ideally the LiveCode IDE
would be watching files/folders rather than having to be notified by the
text editor. One of these days I want to investigate using something like
fswatch  to monitor for changes
and then reload them in the LiveCode IDE. Since a Levure app knows where
all of the project files are stored there is a straight forward way of
knowing which folders to monitor.

-- 
Trevor DeVore
ScreenSteps
www.screensteps.com
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Ralf Bitter via use-livecode]

> On 13. Mar 2019, at 15:17, Mike Kerner via use-livecode 
>  wrote:
> 
> The ST kluge works great for updating scripts live in
> LC, except when it doesn't, and I don't think we have a way to do it with
> Atom, yet.

 There are definitely ways to do it in Atom too.
 Here is how I managed to send notifications to
 a Levure application running in the LiveCode IDE
 using Atom:
 
 - Installed the atom-shell-commands package.
 This is needed to call a shell script every time you
 save a .livecodescript file in Atom.
 
 - Wrote a LC script which is called by the atom-shell-commands
 package. This script writes to the socket the Levure
 script external_editor_server.livecodescript listens to.
 
 - Configured atom-shell-commands (added arguments, a keymap
 and the path to the shell script).
 
 - That's it, works like a charm.
 
 Note: Of course, you could use a modified version of the Python
 script notify_levure_app_of_save.py included in Trevor's LC
 Sublime Text package. But as I know nothing about Python I chose
 the LC route and as a variant the PHP route.
 
 You can find scripts and a configuration example here:
 
 https://gist.github.com/revig
 
 Note: There is a PHP version and a LC version. I you prefer to
 use the LC shell script version you need the modified version of
 external_editor_server.livecodescript.
 This is because the LC version uses UDP sockets as there is an
 issue with writing to sockets on LC server.
 
 
 Ralf
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Geoff Canyon via use-livecode]

Don't forget that you can iterate over the keys if you need them:

repeat for each key tStack in tStacks

or over the elements if you don't need the keys:

repeat for each element V in tStacks

On Mon, Mar 18, 2019 at 4:10 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 3/18/19 3:50 PM, Bob Sneidar via use-livecode wrote:
> > Nice little shortcut. I usually put the keys into a variable first so I
> can see what they are when debugging.
>
> I do too, but this was just a one-off proof of concept.
>
> --
>   Mark Wieder
>   ahsoftw...@gmail.com
>
> ___
> use-livecode mailing list
> use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Mark Wieder via use-livecode]

On 3/18/19 3:50 PM, Bob Sneidar via use-livecode wrote:

Nice little shortcut. I usually put the keys into a variable first so I can see 
what they are when debugging.


I do too, but this was just a one-off proof of concept.

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Bob Sneidar via use-livecode]

Nice little shortcut. I usually put the keys into a variable first so I can see 
what they are when debugging. 

Bob S


> On Mar 16, 2019, at 10:21 , Mark Wieder via use-livecode 
>  wrote:
> 
>   repeat for each line tStack in the keys of tStacks


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Geoff Canyon via use-livecode]

On Sat, Mar 16, 2019 at 9:33 AM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 3/16/19 7:43 AM, AndyP via use-livecode wrote:
> >
> >> But I agree that Navigator having a crap-ton of script-only behaviors is
> >> cumbersome in the IDE if you're showing IDE stacks.
> >
> > At the moment we can hide plugins but only by prefixing the stack name
> with
> > rev. It would be great if we could have another prefix for plugins so
> that
> > they do not get shown in the project browser as standard.
>
> It should be pretty easy to hack the PB to hide plugins when desired...
> If the stack name is among the keys of revIDEPlugins(), ignore it.
>
> Unfortunately, that won't help the Navigator problem.
> Maybe "if the mainstack of stack  is among"...
>

A more general solution would be to have an option to hide SoS in the PB.

As an aside -- why is the scriptonly of stack "revMenuBar" true?? That just
cost me fifteen minutes of debugging Navigator when the only issue was that
Nav was set to not show SoS.
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Mark Wieder via use-livecode]

On 3/16/19 9:33 AM, Mark Wieder via use-livecode wrote:


It should be pretty easy to hack the PB to hide plugins when desired...
If the stack name is among the keys of revIDEPlugins(), ignore it.


Insert the following code before the call to itemise in command 
buildProjectView in stack "revProjectBrowser". I put it at line 472 
(after gathering tStacks) and it did the trick.


   -- ignore plugin stacks
   repeat for each line tStack in the keys of tStacks
  if tStacks[tStack]["short name"] is among the keys of 
revIDEPlugins() then

 delete variable tStacks[tStack]
  end if
   end repeat

...and obviously you'd want a button to toggle this when desired.

Still doesn't help with all those Navigator SO stacks, though.

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Mark Wieder via use-livecode]

On 3/16/19 7:43 AM, AndyP via use-livecode wrote:



But I agree that Navigator having a crap-ton of script-only behaviors is
cumbersome in the IDE if you're showing IDE stacks.


At the moment we can hide plugins but only by prefixing the stack name with
rev. It would be great if we could have another prefix for plugins so that
they do not get shown in the project browser as standard.


It should be pretty easy to hack the PB to hide plugins when desired...
If the stack name is among the keys of revIDEPlugins(), ignore it.

Unfortunately, that won't help the Navigator problem.
Maybe "if the mainstack of stack  is among"...

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[AndyP via use-livecode]

> But I agree that Navigator having a crap-ton of script-only behaviors is
> cumbersome in the IDE if you're showing IDE stacks.

At the moment we can hide plugins but only by prefixing the stack name with
rev. It would be great if we could have another prefix for plugins so that
they do not get shown in the project browser as standard.




-
Andy Piddock 


My software never has bugs. It just develops random features. 

TinyIDE  a Free alternative minimalist IDE Plugin for LiveCode 


Script editor Themer for LC http://2108.co.uk  

PointandSee is a FREE simple but full featured under cursor colour picker / 
finder.
http://www.pointandsee.co.uk  - made with LiveCode
--
Sent from: 
http://runtime-revolution.278305.n4.nabble.com/Revolution-User-f278306.html

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Geoff Canyon via use-livecode]

One of the reasons (the only reason?) I don't do something like this with
Navigator is that there are at least a few people that clone the Navigator
repo directly. I'd rather have everyone (Except Brian!) using the same
exact form of Navigator rather than some using the version with script-only
stacks and the rest using binary.

But I agree that Navigator having a crap-ton of script-only behaviors is
cumbersome in the IDE if you're showing IDE stacks.

gc

On Thu, Mar 14, 2019 at 5:32 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 3/14/19 9:53 AM, Brian Milby via use-livecode wrote:
>
> > 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.
>
> Yeah... if only we could treat script-only stacks as substacks, eh?
>
> --
>   Mark Wieder
>   ahsoftw...@gmail.com
>
> ___
> use-livecode mailing list
> use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Mark Wieder via use-livecode]

On 3/14/19 9:53 AM, Brian Milby via use-livecode wrote:


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.


Yeah... if only we could treat script-only stacks as substacks, eh?

--
 Mark Wieder
 ahsoftw...@gmail.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Brian Milby via use-livecode]

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 
, wrote:
> On Wed, Mar 13, 2019 at 12:30 PM Brian Milby via use-livecode <
> use-livecode@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@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Trevor DeVore via use-livecode]

On Wed, Mar 13, 2019 at 12:30 PM Brian Milby via use-livecode <
use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Geoff Canyon via use-livecode]

I wrote an XML exporter about fifteen years ago. I don't think I have a
copy of it anywhere, and of course it probably would break with all the
changes since then. But it wasn't *that* complex; Navigator has built-in
code to return a list of all the controls within a given group/card/stack,
and separately all the properties/custom properties etc.

gc

On Wed, Mar 13, 2019 at 10:30 AM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> My stack is a different take on the problem.  It allows the benefit of
> tracking the scripts in a VCS while retaining the convenience of a binary
> stack file.  It also allows easy editing of scripts outside of the IDE
> without moving to SOS.  I’m still not convinced that SOS use makes sense
> all of the time (why put a single level of indirect reference in every
> object if the script isn’t shared for example).  Even though I name them
> and format them like a valid SOS, I do not convert them to actual behaviors.
>
> 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.
>
> Monte had another project that did export an entire stack into a
> collection of text files compatible with VCS.  His solution allowed
> multiple developers to work on a stack using the VCS processes to merge
> work.  That is much more ambitious than my goal.  My solution would only
> facilitate distributed work on the scripts of a stack with someone being
> the gatekeeper of the binary stack file.
>
> Exporting properties of each object would not be that difficult to add,
> but doing so in a way compatible with VCS would take a bit of thought.
> Monte would encode binary stuff into an ASCII friendly format.  [I do
> include a few items as comments at the top of each script (behavior, long
> name/ID).]  Format could be XML, JSON, YAML, some new TLA format to appear
> this year...
>
> Thanks,
> Brian
> On Mar 13, 2019, 10:59 AM -0400, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
> > Navigator also has an exporter, and Monte wrote "Scriptifier", which is
> > included in the LC bundle, for exporting scripts to SOS's. Once they're
> in
> > SOS's, there's no reason to put them back in the stack, since you can
> edit
> > them using the LC SE or in an external editor. I thought about writing
> > something to export the properties of objects in a stack into text files,
> > and then at startup using that information to build the stack, but that's
> > as far as it's gotten is thinking about it.
> >
> > On Wed, Mar 13, 2019 at 10:28 AM Brian Milby via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> > > I have a tool that exports the scripts of a stack and can facilitate
> > > editing in any external editor. I want to hook it up in Atom like ST,
> but
> > > have not figured out how to rewrite the module in JS. ScriptTracker
> works
> > > by watching a directory for changes to the files. The ST plugin works
> by
> > > sending messages to a server process running in the IDE.
> > >
> > > forums.livecode.com/viewtopic.php?f=77&t=31079
> > > github.com/bwmilby/lc-misc/tree/master/ScriptTracker
> > > github.com/bwmilby/lc-misc/blob/master/ScriptTracker/ScriptTracker.md
> > >
> > > Thanks,
> > > Brian
> > > On Mar 13, 2019, 10:18 AM -0400, Mike Kerner via use-livecode <
> > > use-livecode@lists.runrev.com>, wrote:
> > > > The new sublimeText update dropped this morning, and it's pretty
> sweet.
> > > > It now has things like git status integration, which is very cool.
> > > > It would be really cool if we could get better integration between
> > > external
> > > > text editors and ST. The ST kluge works great for updating scripts
> live
> > > in
> > > > LC, except when it doesn't, and I don't think we have a way to do it
> with
> > > > Atom, yet.
> > > > It would also be cool if we had a better way to have stack files be
> > > > represented as text files instead of binary files for easier version
> > > > control and editing.
> > > > Anyway,
> > > > https://www.sublimetext.com/blog/articles/sublime-text-3-point-2
> > > >
> > > > --
> > > > On the first day, God created the heavens and the Earth
> > > > On the second day, God created the oceans.
> > > > On the third day, God put the animals on hold for a few hours,
> > > > and did a little diving.
> > > > And God said, "This is good."
> > > > ___
> > > > use-livecode mailing list
> > > > use-livecode@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@lists.runrev.com
> > > Please visit this url to subscribe, unsubscribe and manage your
> > > subscrip

Re: [off]sublimeText update

[Brian Milby via use-livecode]

My stack is a different take on the problem.  It allows the benefit of tracking 
the scripts in a VCS while retaining the convenience of a binary stack file.  
It also allows easy editing of scripts outside of the IDE without moving to 
SOS.  I’m still not convinced that SOS use makes sense all of the time (why put 
a single level of indirect reference in every object if the script isn’t shared 
for example).  Even though I name them and format them like a valid SOS, I do 
not convert them to actual behaviors.

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.

Monte had another project that did export an entire stack into a collection of 
text files compatible with VCS.  His solution allowed multiple developers to 
work on a stack using the VCS processes to merge work.  That is much more 
ambitious than my goal.  My solution would only facilitate distributed work on 
the scripts of a stack with someone being the gatekeeper of the binary stack 
file.

Exporting properties of each object would not be that difficult to add, but 
doing so in a way compatible with VCS would take a bit of thought.  Monte would 
encode binary stuff into an ASCII friendly format.  [I do include a few items 
as comments at the top of each script (behavior, long name/ID).]  Format could 
be XML, JSON, YAML, some new TLA format to appear this year...

Thanks,
Brian
On Mar 13, 2019, 10:59 AM -0400, Mike Kerner via use-livecode 
, wrote:
> Navigator also has an exporter, and Monte wrote "Scriptifier", which is
> included in the LC bundle, for exporting scripts to SOS's. Once they're in
> SOS's, there's no reason to put them back in the stack, since you can edit
> them using the LC SE or in an external editor. I thought about writing
> something to export the properties of objects in a stack into text files,
> and then at startup using that information to build the stack, but that's
> as far as it's gotten is thinking about it.
>
> On Wed, Mar 13, 2019 at 10:28 AM Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > I have a tool that exports the scripts of a stack and can facilitate
> > editing in any external editor. I want to hook it up in Atom like ST, but
> > have not figured out how to rewrite the module in JS. ScriptTracker works
> > by watching a directory for changes to the files. The ST plugin works by
> > sending messages to a server process running in the IDE.
> >
> > forums.livecode.com/viewtopic.php?f=77&t=31079
> > github.com/bwmilby/lc-misc/tree/master/ScriptTracker
> > github.com/bwmilby/lc-misc/blob/master/ScriptTracker/ScriptTracker.md
> >
> > Thanks,
> > Brian
> > On Mar 13, 2019, 10:18 AM -0400, Mike Kerner via use-livecode <
> > use-livecode@lists.runrev.com>, wrote:
> > > The new sublimeText update dropped this morning, and it's pretty sweet.
> > > It now has things like git status integration, which is very cool.
> > > It would be really cool if we could get better integration between
> > external
> > > text editors and ST. The ST kluge works great for updating scripts live
> > in
> > > LC, except when it doesn't, and I don't think we have a way to do it with
> > > Atom, yet.
> > > It would also be cool if we had a better way to have stack files be
> > > represented as text files instead of binary files for easier version
> > > control and editing.
> > > Anyway,
> > > https://www.sublimetext.com/blog/articles/sublime-text-3-point-2
> > >
> > > --
> > > On the first day, God created the heavens and the Earth
> > > On the second day, God created the oceans.
> > > On the third day, God put the animals on hold for a few hours,
> > > and did a little diving.
> > > And God said, "This is good."
> > > ___
> > > use-livecode mailing list
> > > use-livecode@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@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
> and did a little diving.
> And God said, "This is good."
> ___
> use-livecode mailing list
> use-livecode@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-li

Re: [off]sublimeText update

[Bob Sneidar via use-livecode]

That's been mulled over before. It's a huge undertaking. Arrays in properties 
would have to be arrayEncoded of course, which makes putting it all in a flat 
text file extremely problematic. Where does the array data begin and end you 
see? 

An XML file would be better. 

Bob S


> On Mar 13, 2019, at 07:58 , Mike Kerner via use-livecode 
>  wrote:
> 
> Navigator also has an exporter, and Monte wrote "Scriptifier", which is
> included in the LC bundle, for exporting scripts to SOS's.  Once they're in
> SOS's, there's no reason to put them back in the stack, since you can edit
> them using the LC SE or in an external editor.  I thought about writing
> something to export the properties of objects in a stack into text files,
> and then at startup using that information to build the stack, but that's
> as far as it's gotten is thinking about it.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Mike Kerner via use-livecode]

Navigator also has an exporter, and Monte wrote "Scriptifier", which is
included in the LC bundle, for exporting scripts to SOS's.  Once they're in
SOS's, there's no reason to put them back in the stack, since you can edit
them using the LC SE or in an external editor.  I thought about writing
something to export the properties of objects in a stack into text files,
and then at startup using that information to build the stack, but that's
as far as it's gotten is thinking about it.

On Wed, Mar 13, 2019 at 10:28 AM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I have a tool that exports the scripts of a stack and can facilitate
> editing in any external editor.  I want to hook it up in Atom like ST, but
> have not figured out how to rewrite the module in JS.  ScriptTracker works
> by watching a directory for changes to the files.  The ST plugin works by
> sending messages to a server process running in the IDE.
>
> forums.livecode.com/viewtopic.php?f=77&t=31079
> github.com/bwmilby/lc-misc/tree/master/ScriptTracker
> github.com/bwmilby/lc-misc/blob/master/ScriptTracker/ScriptTracker.md
>
> Thanks,
> Brian
> On Mar 13, 2019, 10:18 AM -0400, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com>, wrote:
> > The new sublimeText update dropped this morning, and it's pretty sweet.
> > It now has things like git status integration, which is very cool.
> > It would be really cool if we could get better integration between
> external
> > text editors and ST. The ST kluge works great for updating scripts live
> in
> > LC, except when it doesn't, and I don't think we have a way to do it with
> > Atom, yet.
> > It would also be cool if we had a better way to have stack files be
> > represented as text files instead of binary files for easier version
> > control and editing.
> > Anyway,
> > https://www.sublimetext.com/blog/articles/sublime-text-3-point-2
> >
> > --
> > On the first day, God created the heavens and the Earth
> > On the second day, God created the oceans.
> > On the third day, God put the animals on hold for a few hours,
> > and did a little diving.
> > And God said, "This is good."
> > ___
> > use-livecode mailing list
> > use-livecode@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@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: [off]sublimeText update

[Brian Milby via use-livecode]

I have a tool that exports the scripts of a stack and can facilitate editing in 
any external editor.  I want to hook it up in Atom like ST, but have not 
figured out how to rewrite the module in JS.  ScriptTracker works by watching a 
directory for changes to the files.  The ST plugin works by sending messages to 
a server process running in the IDE.

forums.livecode.com/viewtopic.php?f=77&t=31079
github.com/bwmilby/lc-misc/tree/master/ScriptTracker
github.com/bwmilby/lc-misc/blob/master/ScriptTracker/ScriptTracker.md

Thanks,
Brian
On Mar 13, 2019, 10:18 AM -0400, Mike Kerner via use-livecode 
, wrote:
> The new sublimeText update dropped this morning, and it's pretty sweet.
> It now has things like git status integration, which is very cool.
> It would be really cool if we could get better integration between external
> text editors and ST. The ST kluge works great for updating scripts live in
> LC, except when it doesn't, and I don't think we have a way to do it with
> Atom, yet.
> It would also be cool if we had a better way to have stack files be
> represented as text files instead of binary files for easier version
> control and editing.
> Anyway,
> https://www.sublimetext.com/blog/articles/sublime-text-3-point-2
>
> --
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
> and did a little diving.
> And God said, "This is good."
> ___
> use-livecode mailing list
> use-livecode@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@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

[off]sublimeText update

[Mike Kerner via use-livecode]

The new sublimeText update dropped this morning, and it's pretty sweet.
It now has things like git status integration, which is very cool.
It would be really cool if we could get better integration between external
text editors and ST.  The ST kluge works great for updating scripts live in
LC, except when it doesn't, and I don't think we have a way to do it with
Atom, yet.
It would also be cool if we had a better way to have stack files be
represented as text files instead of binary files for easier version
control and editing.
Anyway,
https://www.sublimetext.com/blog/articles/sublime-text-3-point-2

-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode