Re: Livecode / Github

[Mark Wieder via use-livecode]

On 9/1/22 18:47, Brian Milby via use-livecode wrote:

Mark, this is the same bug that you already filed:
https://quality.livecode.com/show_bug.cgi?id=23910


Hah! Forgot about that one. Same root cause but different symptoms, 
since it also results in a complete failure of the Plugins feature 
without throwing any errors.


--
 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: Livecode / Github

[Brian Milby via use-livecode]

I would agree that a LC specific (smartcrumbs specific actually) interface
to git would be helpful.  On the back end, it would just be native git
add/commit/push/fetch/pull/merge commands to get data into the repository.
The JSON file structure looks to be a mainstack key with the GUID value and
then GUID keys for each stack in the file that have all objects as a
dictionary. It should be relatively easy to turn it into an array. The
challenge will be dealing with diffs.  The structure is something like this:

{
  "guid of stack a": {
"object guid": {
}
  },
  "guid of stack b": {
"guid of stack b": {
  "name": "Main Stack Name"
}
  },
  "mainstack": "guid of stack b"
}



On Thu, Sep 1, 2022 at 9:41 PM Pi Digital via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Thanks Brian for your comprehensive response. What I meant was, though,
> that ‘ideally’ we need some instructions in the Guide and preferably a GUI
> for github and the like built into LC specifically for SmartCrumbs. That
> way the UIDs can be auto converted to the object names and laid out in
> filestruct format to make sense. Roundtripping to SourceTree or anything
> else is not really what we want, is it?
>
> Let me see if I get a chance to knock something up quickly over the
> weekend. I need to try out these new polylist and polygrid widgets anyway.
> Linking it to GitHub and remote servers shouldn’t be an issue. I understand
> how they work so I won’t have a problem. It just needs to be made much much
> simpler for others.
>
> Sean Cole
> Pi Digital Productions Ltd
>
> eMail Ts & Cs
>
>
> > On 2 Sep 2022, at 02:26, Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > I think some of this is a bit too much to address in a list post.  I'll
> > make some comments though.
> > (i) Make a repo at https://github.com;
> > https://www.atlassian.com/git/tutorials/setting-up-a-repository; you can
> > view tons of docs at https://docs.github.com/en
> > (ii)-(iv) I use https://www.sourcetreeapp.com (Mac and Win app
> available)
> > to manage my repos (many other options available). They also have other
> > tutorials at https://www.atlassian.com/git
> >
> > When you create a GitHub repository currently, it will make a default
> > branch called "main".  Initially you would take your stack and commit
> > (really another word for "save") to the main branch.  If you had 2
> > developers that were working on the same stack at the same time, then one
> > way would be to have 2 branches off of main.  Let's say "brian" and
> "sean"
> > for example.  So each of us would check out our branch (initially the
> same
> > as main).  We would make any changes we needed and each would commit to
> our
> > own branch.  When whatever we are working on is ready to incorporate into
> > the product, we would merge our branch into the main branch.  Since
> > everything is text files (except for the images and other binary
> resources
> > like that), git can detect which pieces have changed and integrate them
> > together.  So instead of a zip going back and forth of the full project,
> > the individual changes would be tracked and integrated.  The biggest
> > difference is that multiple developers can work on the same stack at the
> > same time and have their changes integrated together.
> >
> > The down side that I do see with this implementation is that it is
> > difficult to know what object is being changed.  Since everything is
> stored
> > by GUID it can be hard to know what is being updated by looking at the
> > commit logs.  Due to the Mac CR issue, I probably won't be able to do
> much
> > for demonstrating how it works until there is a good workaround (I guess
> I
> > could manually convert the JSON each time for now).  I did fix the JSON
> > file on my ScriptTracker repo so it could be viewed on GitHub.  I need to
> > make a change to a script that hasn't been fixed to see how it shows up.
> > The JSON fix showed pretty much as a whole new file (line 1 was updated
> to
> > lines 1-1000+).
> >
> > My approach with ScriptTracker is a bit different.  First is that my tool
> > is much more limited (just does the scripts).  But, my tool adds a bit of
> > information to the header of each exported script to give it context and
> > the scripts are named by the object ID (mainly to avoid issues with
> illegal
> > characters in the object name).  It might be something that could be done
> > with plugins to add some info to the JSON and script files.  I'll need to
> > take a look - it would make working with the scripts easier.  For the
> JSON,
> > I think it may be helpful to have full object names included with the
> GUID
> > so you have more of an idea what was changed when looking at the diff.
> >
> > Also, if you just want to track your changes (and not work with another
> dev
> > to merge), it does get a bit easier.  Then you don't even need to use a
> > server (GitHub) but can run git completely on your seat.  The

Re: Livecode / Github

[Brian Milby via use-livecode]

Mark, this is the same bug that you already filed:
https://quality.livecode.com/show_bug.cgi?id=23910

On Thu, Sep 1, 2022 at 9:29 PM Brian Milby  wrote:

> Actually, that is a bug that needs to be fixed.  I don't have "My
> Livecode" running from my documents folder.  So the extension itself is in
> the correct place, but all of the stuff it writes is in the wrong place.
>
> On Thu, Sep 1, 2022 at 9:04 PM Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> Got it figured out. It just doesn't work on linux.
>>
>> On OSX when executing scEnabledPlugin  I get the error
>>
>> A stack with the same name as ...
>> Before loading /Users//Documents/My
>> LiveCode/SmartCrumbsVCW/extensions...
>> what do you want to do with stack:
>> /Users//Downloads/smartCrumbs/...
>>
>> So it looks like scInstallPlugin installs a copy of the plugin into a
>> *very* specific hardcoded directory, no matter where I placed the source
>> to start with. And no doubt calls specialFolderPath("documents") in
>> order to figure out where that should be and of course that call
>> doesn't work on linux, so it probably just gives up silently. I'm
>> guessing the correct call should really be to
>> revEnvironmentUserPluginsPath().
>>
>> Not going to bother filing a bug on this. I rather expect LC to drop
>> linux support any day now anyway.
>>
>>
>> --
>>   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: Livecode / Github

[Pi Digital via use-livecode]

Thanks Brian for your comprehensive response. What I meant was, though, that 
‘ideally’ we need some instructions in the Guide and preferably a GUI for 
github and the like built into LC specifically for SmartCrumbs. That way the 
UIDs can be auto converted to the object names and laid out in filestruct 
format to make sense. Roundtripping to SourceTree or anything else is not 
really what we want, is it? 

Let me see if I get a chance to knock something up quickly over the weekend. I 
need to try out these new polylist and polygrid widgets anyway. Linking it to 
GitHub and remote servers shouldn’t be an issue. I understand how they work so 
I won’t have a problem. It just needs to be made much much simpler for others. 

Sean Cole
Pi Digital Productions Ltd

eMail Ts & Cs


> On 2 Sep 2022, at 02:26, Brian Milby via use-livecode 
>  wrote:
> 
> I think some of this is a bit too much to address in a list post.  I'll
> make some comments though.
> (i) Make a repo at https://github.com;
> https://www.atlassian.com/git/tutorials/setting-up-a-repository; you can
> view tons of docs at https://docs.github.com/en
> (ii)-(iv) I use https://www.sourcetreeapp.com (Mac and Win app available)
> to manage my repos (many other options available). They also have other
> tutorials at https://www.atlassian.com/git
> 
> When you create a GitHub repository currently, it will make a default
> branch called "main".  Initially you would take your stack and commit
> (really another word for "save") to the main branch.  If you had 2
> developers that were working on the same stack at the same time, then one
> way would be to have 2 branches off of main.  Let's say "brian" and "sean"
> for example.  So each of us would check out our branch (initially the same
> as main).  We would make any changes we needed and each would commit to our
> own branch.  When whatever we are working on is ready to incorporate into
> the product, we would merge our branch into the main branch.  Since
> everything is text files (except for the images and other binary resources
> like that), git can detect which pieces have changed and integrate them
> together.  So instead of a zip going back and forth of the full project,
> the individual changes would be tracked and integrated.  The biggest
> difference is that multiple developers can work on the same stack at the
> same time and have their changes integrated together.
> 
> The down side that I do see with this implementation is that it is
> difficult to know what object is being changed.  Since everything is stored
> by GUID it can be hard to know what is being updated by looking at the
> commit logs.  Due to the Mac CR issue, I probably won't be able to do much
> for demonstrating how it works until there is a good workaround (I guess I
> could manually convert the JSON each time for now).  I did fix the JSON
> file on my ScriptTracker repo so it could be viewed on GitHub.  I need to
> make a change to a script that hasn't been fixed to see how it shows up.
> The JSON fix showed pretty much as a whole new file (line 1 was updated to
> lines 1-1000+).
> 
> My approach with ScriptTracker is a bit different.  First is that my tool
> is much more limited (just does the scripts).  But, my tool adds a bit of
> information to the header of each exported script to give it context and
> the scripts are named by the object ID (mainly to avoid issues with illegal
> characters in the object name).  It might be something that could be done
> with plugins to add some info to the JSON and script files.  I'll need to
> take a look - it would make working with the scripts easier.  For the JSON,
> I think it may be helpful to have full object names included with the GUID
> so you have more of an idea what was changed when looking at the diff.
> 
> Also, if you just want to track your changes (and not work with another dev
> to merge), it does get a bit easier.  Then you don't even need to use a
> server (GitHub) but can run git completely on your seat.  The same GUI
> tools mentioned above can be used there as well.
> 
> Command line tools are there but not required.  As I mentioned above, I use
> a GUI for just about all of my git usage.  They make it easy to see what
> happened and when.
> 
> Hopefully this helps a little.  I think there are a couple of videos from
> conferences over the past few years covering Git.  I know that there is at
> least one that I did (but it was targeted at building LC from source).
> 
> Thanks,
> Brian
> 
>> On Thu, Sep 1, 2022 at 5:39 PM Pi Digital via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> Fab :D
>> 
>> however, ‘how’ does one…
>> (i) set up a GitHub (I know how, this is for the benefit of others),
>> (ii) perform commits, push, pulls (perhaps using LC and having an LC
>> library/widget for this would be best),
>> (iii) merge to a branch,
>> (iv) switch branches
>> All the while making it simple for even the most beginner of beginners to
>> understand, like 

Re: Livecode / Github

[Brian Milby via use-livecode]

Actually, that is a bug that needs to be fixed.  I don't have "My Livecode"
running from my documents folder.  So the extension itself is in the
correct place, but all of the stuff it writes is in the wrong place.

On Thu, Sep 1, 2022 at 9:04 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Got it figured out. It just doesn't work on linux.
>
> On OSX when executing scEnabledPlugin  I get the error
>
> A stack with the same name as ...
> Before loading /Users//Documents/My
> LiveCode/SmartCrumbsVCW/extensions...
> what do you want to do with stack:
> /Users//Downloads/smartCrumbs/...
>
> So it looks like scInstallPlugin installs a copy of the plugin into a
> *very* specific hardcoded directory, no matter where I placed the source
> to start with. And no doubt calls specialFolderPath("documents") in
> order to figure out where that should be and of course that call
> doesn't work on linux, so it probably just gives up silently. I'm
> guessing the correct call should really be to
> revEnvironmentUserPluginsPath().
>
> Not going to bother filing a bug on this. I rather expect LC to drop
> linux support any day now anyway.
>
>
> --
>   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: Livecode / Github

[Brian Milby via use-livecode]

I think some of this is a bit too much to address in a list post.  I'll
make some comments though.
(i) Make a repo at https://github.com;
https://www.atlassian.com/git/tutorials/setting-up-a-repository; you can
view tons of docs at https://docs.github.com/en
(ii)-(iv) I use https://www.sourcetreeapp.com (Mac and Win app available)
to manage my repos (many other options available). They also have other
tutorials at https://www.atlassian.com/git

When you create a GitHub repository currently, it will make a default
branch called "main".  Initially you would take your stack and commit
(really another word for "save") to the main branch.  If you had 2
developers that were working on the same stack at the same time, then one
way would be to have 2 branches off of main.  Let's say "brian" and "sean"
for example.  So each of us would check out our branch (initially the same
as main).  We would make any changes we needed and each would commit to our
own branch.  When whatever we are working on is ready to incorporate into
the product, we would merge our branch into the main branch.  Since
everything is text files (except for the images and other binary resources
like that), git can detect which pieces have changed and integrate them
together.  So instead of a zip going back and forth of the full project,
the individual changes would be tracked and integrated.  The biggest
difference is that multiple developers can work on the same stack at the
same time and have their changes integrated together.

The down side that I do see with this implementation is that it is
difficult to know what object is being changed.  Since everything is stored
by GUID it can be hard to know what is being updated by looking at the
commit logs.  Due to the Mac CR issue, I probably won't be able to do much
for demonstrating how it works until there is a good workaround (I guess I
could manually convert the JSON each time for now).  I did fix the JSON
file on my ScriptTracker repo so it could be viewed on GitHub.  I need to
make a change to a script that hasn't been fixed to see how it shows up.
The JSON fix showed pretty much as a whole new file (line 1 was updated to
lines 1-1000+).

My approach with ScriptTracker is a bit different.  First is that my tool
is much more limited (just does the scripts).  But, my tool adds a bit of
information to the header of each exported script to give it context and
the scripts are named by the object ID (mainly to avoid issues with illegal
characters in the object name).  It might be something that could be done
with plugins to add some info to the JSON and script files.  I'll need to
take a look - it would make working with the scripts easier.  For the JSON,
I think it may be helpful to have full object names included with the GUID
so you have more of an idea what was changed when looking at the diff.

Also, if you just want to track your changes (and not work with another dev
to merge), it does get a bit easier.  Then you don't even need to use a
server (GitHub) but can run git completely on your seat.  The same GUI
tools mentioned above can be used there as well.

Command line tools are there but not required.  As I mentioned above, I use
a GUI for just about all of my git usage.  They make it easy to see what
happened and when.

Hopefully this helps a little.  I think there are a couple of videos from
conferences over the past few years covering Git.  I know that there is at
least one that I did (but it was targeted at building LC from source).

Thanks,
Brian

On Thu, Sep 1, 2022 at 5:39 PM Pi Digital via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Fab :D
>
> however, ‘how’ does one…
>  (i) set up a GitHub (I know how, this is for the benefit of others),
> (ii) perform commits, push, pulls (perhaps using LC and having an LC
> library/widget for this would be best),
> (iii) merge to a branch,
> (iv) switch branches
> All the while making it simple for even the most beginner of beginners to
> understand, like everything else in LC *Should be?
>
> It’s like giving us the front door but the hallway floor is missing.
>
> There is no guide on real world usage so we are left stranded with it.
>
> Here’s the actual situation myself and my colleague face. At the moment
> one of us works on the app, makes some changes, zips it up, and posts it up
> to a server. Then the other does the same ad infinitum.
>
> But what you have described is not much different. How can we really tell
> who made changes unless we know the uid for the script or card (for layout)
> or object? And are we all supposed to now become command line experts to
> manage an svc? I’m puzzled at the moment.
>
> It shows great promise, but it’s still not fully ready, is it. It’s
> usable, like LCB, if you can do lower level stuff. But not many using LC
> are able, hence why they use LC. Everything LC, and I mean everything, that
> is front end for LC users *Should, note, Should be High Level and easy to
> code & understand. The plug

Re: Livecode / Github

[Mark Wieder via use-livecode]

Got it figured out. It just doesn't work on linux.

On OSX when executing scEnabledPlugin  I get the error

A stack with the same name as ...
Before loading /Users//Documents/My 
LiveCode/SmartCrumbsVCW/extensions...

what do you want to do with stack:
/Users//Downloads/smartCrumbs/...

So it looks like scInstallPlugin installs a copy of the plugin into a 
*very* specific hardcoded directory, no matter where I placed the source 
to start with. And no doubt calls specialFolderPath("documents") in 
order to figure out where that should be and of course that call 
doesn't work on linux, so it probably just gives up silently. I'm 
guessing the correct call should really be to 
revEnvironmentUserPluginsPath().


Not going to bother filing a bug on this. I rather expect LC to drop 
linux support any day now anyway.



--
 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: Livecode / Github

[Mark Wieder via use-livecode]

On 9/1/22 15:55, Pi Digital via use-livecode wrote:

LC9.6.7?


9.6.9rc1

--
 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: Livecode / Github

[Pi Digital via use-livecode]

LC9.6.7?

Sean Cole
Pi Digital Productions Ltd

eMail Ts & Cs


> On 1 Sep 2022, at 23:48, Mark Wieder via use-livecode 
>  wrote:
> 
> On 9/1/22 15:16, Pi Digital via use-livecode wrote:
> 
>> Here are the steps
> 
> Yep. Exactly what I did.
> Oh well. ¯\_ (ツ)_/¯
> 
> -- 
> 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: Livecode / Github

[Mark Wieder via use-livecode]

On 9/1/22 15:16, Pi Digital via use-livecode wrote:


Here are the steps


Yep. Exactly what I did.
Oh well. ¯\_ (ツ)_/¯

--
 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: Livecode / Github

[Pi Digital via use-livecode]

I don’t know who coded it but it really does not follow the standard LC 
conventions. I am going to assume it was someone external to LC so will cut 
them a huge bit of slack. It’s also very clear English is not their first 
language so they did pretty well considering. 

Here are the steps

Create a new plug-in file using
scCreatePlugin “”,””
This will first ask for a name and then for a folder location to put it. I put 
it into the MyLivecode folder in a subfolder called SmartCrumbsPlugins

Edit the code as needed and save. Make sure to ONLY do this in LC, not Atom or 
another text editor.

Next, use
scInstallPlugin “”
This will ask which plug-in to load

Then
scEnabledPlugin “myPlugin”
where myPlugin is the name you have given it, which is not necessarily the same 
as the file name. This will make sure it is running the next time any 
SmartCrumbs import/export operation is performed. 

To find which plugins are installed and enabled, use
put the keys of scListPlugins (“All”)

To find the path where the logs are saved, use
put scGetPathLog(“”)
or
put scGetPathLog()
Either will work



Sean Cole
Pi Digital Productions Ltd

eMail Ts & Cs


> On 1 Sep 2022, at 22:43, Mark Wieder via use-livecode 
>  wrote:
> 
> On 9/1/22 11:25, Sean Cole via use-livecode wrote:
> 
>> By the way, here is an update to the plugin code:
> 
> Sean- good news that you got it working. How in the world did you manage 
> that? I went through what I think are the right steps:
> 
> scCreatePlugin "",""
> edit and save plugin code
> scInstallPlugin pPath
> scEnabledPlugin pPath
> scListPlugins() --- nothing (no array keys)
> scGetPathLog() --- recursion limit reached
> 
> -- 
> 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: Livecode / Github

[Mark Wieder via use-livecode]

On 9/1/22 11:25, Sean Cole via use-livecode wrote:


By the way, here is an update to the plugin code:


Sean- good news that you got it working. How in the world did you manage 
that? I went through what I think are the right steps:


scCreatePlugin "",""
edit and save plugin code
scInstallPlugin pPath
scEnabledPlugin pPath
scListPlugins() --- nothing (no array keys)
scGetPathLog() --- recursion limit reached

--
 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: Livecode / Github

[Pi Digital via use-livecode]

Fab :D

however, ‘how’ does one…
 (i) set up a GitHub (I know how, this is for the benefit of others), 
(ii) perform commits, push, pulls (perhaps using LC and having an LC 
library/widget for this would be best), 
(iii) merge to a branch, 
(iv) switch branches
All the while making it simple for even the most beginner of beginners to 
understand, like everything else in LC *Should be?

It’s like giving us the front door but the hallway floor is missing. 

There is no guide on real world usage so we are left stranded with it. 

Here’s the actual situation myself and my colleague face. At the moment one of 
us works on the app, makes some changes, zips it up, and posts it up to a 
server. Then the other does the same ad infinitum. 

But what you have described is not much different. How can we really tell who 
made changes unless we know the uid for the script or card (for layout) or 
object? And are we all supposed to now become command line experts to manage an 
svc? I’m puzzled at the moment. 

It shows great promise, but it’s still not fully ready, is it. It’s usable, 
like LCB, if you can do lower level stuff. But not many using LC are able, 
hence why they use LC. Everything LC, and I mean everything, that is front end 
for LC users *Should, note, Should be High Level and easy to code & understand. 
The plug-in language for SmartCrumbs is dreamy. Thank you whoever came up with 
that. I love it! LCB is a nightmare and could have been done so much better - 
much more in line with the HyperCard principle. 

Sean Cole
Pi

> On 1 Sep 2022, at 20:13, Brian Milby via use-livecode 
>  wrote:
> 
> Here is the workflow that I think is intended:
> 
> Export stack to files
> Commit files to GitHub or other VCS
> —
> Fetch/pull latest from GitHub
> Import stack from files
> Make changes
> Export stack to files
> Commit changes to GitHub
> —
> At any point changes between branches can be merged due to structure of 
> exports so you could have parallel development happening.
> 
> Brian Milby
> br...@milby7.com
> 
>> On Sep 1, 2022, at 2:27 PM, Sean Cole via use-livecode 
>>  wrote:
>> 
>> I managed to get the stack and all substacks to export finally. There was
>> an issue with an old extension library two of the stacks use (Chart Maker)
>> so just removed the stacks for now and all ported properly.
>> 
>> Now, it occurs to me that this is all well and good, but there is a lack of
>> instruction on how to make use of it now. How do you link it to something
>> like GitHub or some other external or local server? How do we collaborate
>> with other users? How will they know which scripts are which when they only
>> see a folder full or GUIDs?
>> 
>> I 'think' these are valid questions. Or maybe I'm just stupid or missed
>> something somewhere.
>> 
>> By the way, here is an update to the plugin code:
>> global gLastObject
>> 
>> on savingProperties pLongId, @pProperteis
>>  // I'm loving all the typos like pProperteis - Really rushed out the
>> door.
>>  put "saving properties of" && pLongId into gLastObject
>>  put gLastObject
>>  wait 0.001 millisec with messages
>> end savingProperties
>> 
>> on savingScript pLongId, @pScript
>>  put "saving script of" && pLongId into gLastObject
>>  put gLastObject
>>  wait 0.001 millisec with messages
>> end savingScript
>> 
>> Sean
>> 
 On Thu, 1 Sept 2022 at 05:08, Sean Cole  wrote:
>>> 
>>> Yeah, I could really do with it giving me some feedback as to where this
>>> object is. Actually, I could...
>>> ... I just wrote a plugin for it. Use scCreatePlugin "","" (scCreatePlugin
>>> on its own doesn't work from the message box like the dictionary suggests).
>>> Then in the script I used
>>> 
>>> global gLastObject
>>> 
>>> on savingProperties pLongId, @pProperteis
>>>  --> your code
>>>  put "saving properties of" && pLongId into gLastObject
>>>  put word -2 to -1 of gLastObject
>>>  wait 0.01 millisec with messages
>>> end savingProperties
>>> 
>>> 
>>> 
>>> Once I ran this it displayed which substack it was working on in the
>>> message box and once it had failed the global showed me the last parameter
>>> it had successfully accessed. Cool. But I still can't work out which
>>> parameter of either that object (a standard text field) or the next (a
>>> group with no behaviours or anything out of the ordinary as far as I can
>>> tell). I'll come back to it tomorrow. It's silly o'clock now.
>>> 
>>> Sean
>>> 
>>> On Wed, 31 Aug 2022 at 17:13, Mark Wieder via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
> On 8/31/22 03:00, Sean Cole via use-livecode wrote:
 
> LC Team: :-) It would be REALLY handy if proper errors were thrown when
 one
> occurs that can help us easily understand what the issues are. Also, if
> prior to release documentation were gone through to make sure they are
> legible. And if plugins released actually work as described. :-)
 
 Actually, it's even worse.
 The result is empty if no error occurred and

Re: Livecode / Github

[Brian Milby via use-livecode]

Here is the workflow that I think is intended:

Export stack to files
Commit files to GitHub or other VCS
—
Fetch/pull latest from GitHub
Import stack from files
Make changes
Export stack to files
Commit changes to GitHub
—
At any point changes between branches can be merged due to structure of exports 
so you could have parallel development happening.

Brian Milby
br...@milby7.com

> On Sep 1, 2022, at 2:27 PM, Sean Cole via use-livecode 
>  wrote:
> 
> I managed to get the stack and all substacks to export finally. There was
> an issue with an old extension library two of the stacks use (Chart Maker)
> so just removed the stacks for now and all ported properly.
> 
> Now, it occurs to me that this is all well and good, but there is a lack of
> instruction on how to make use of it now. How do you link it to something
> like GitHub or some other external or local server? How do we collaborate
> with other users? How will they know which scripts are which when they only
> see a folder full or GUIDs?
> 
> I 'think' these are valid questions. Or maybe I'm just stupid or missed
> something somewhere.
> 
> By the way, here is an update to the plugin code:
> global gLastObject
> 
> on savingProperties pLongId, @pProperteis
>   // I'm loving all the typos like pProperteis - Really rushed out the
> door.
>   put "saving properties of" && pLongId into gLastObject
>   put gLastObject
>   wait 0.001 millisec with messages
> end savingProperties
> 
> on savingScript pLongId, @pScript
>   put "saving script of" && pLongId into gLastObject
>   put gLastObject
>   wait 0.001 millisec with messages
> end savingScript
> 
> Sean
> 
>> On Thu, 1 Sept 2022 at 05:08, Sean Cole  wrote:
>> 
>> Yeah, I could really do with it giving me some feedback as to where this
>> object is. Actually, I could...
>> ... I just wrote a plugin for it. Use scCreatePlugin "","" (scCreatePlugin
>> on its own doesn't work from the message box like the dictionary suggests).
>> Then in the script I used
>> 
>> global gLastObject
>> 
>> on savingProperties pLongId, @pProperteis
>>   --> your code
>>   put "saving properties of" && pLongId into gLastObject
>>   put word -2 to -1 of gLastObject
>>   wait 0.01 millisec with messages
>> end savingProperties
>> 
>> 
>> 
>> Once I ran this it displayed which substack it was working on in the
>> message box and once it had failed the global showed me the last parameter
>> it had successfully accessed. Cool. But I still can't work out which
>> parameter of either that object (a standard text field) or the next (a
>> group with no behaviours or anything out of the ordinary as far as I can
>> tell). I'll come back to it tomorrow. It's silly o'clock now.
>> 
>> Sean
>> 
>> On Wed, 31 Aug 2022 at 17:13, Mark Wieder via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
 On 8/31/22 03:00, Sean Cole via use-livecode wrote:
>>> 
 LC Team: :-) It would be REALLY handy if proper errors were thrown when
>>> one
 occurs that can help us easily understand what the issues are. Also, if
 prior to release documentation were gone through to make sure they are
 legible. And if plugins released actually work as described. :-)
>>> 
>>> Actually, it's even worse.
>>> The result is empty if no error occurred and "* successful" if it
>>> worked. To me that seems backwards.
>>> 
>>> https://quality.livecode.com/show_bug.cgi?id=23911
>>> 
>>> --
>>>  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

___
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: Livecode / Github

[Sean Cole via use-livecode]

I managed to get the stack and all substacks to export finally. There was
an issue with an old extension library two of the stacks use (Chart Maker)
so just removed the stacks for now and all ported properly.

Now, it occurs to me that this is all well and good, but there is a lack of
instruction on how to make use of it now. How do you link it to something
like GitHub or some other external or local server? How do we collaborate
with other users? How will they know which scripts are which when they only
see a folder full or GUIDs?

I 'think' these are valid questions. Or maybe I'm just stupid or missed
something somewhere.

By the way, here is an update to the plugin code:
global gLastObject

on savingProperties pLongId, @pProperteis
   // I'm loving all the typos like pProperteis - Really rushed out the
door.
   put "saving properties of" && pLongId into gLastObject
   put gLastObject
   wait 0.001 millisec with messages
end savingProperties

on savingScript pLongId, @pScript
   put "saving script of" && pLongId into gLastObject
   put gLastObject
   wait 0.001 millisec with messages
end savingScript

Sean

On Thu, 1 Sept 2022 at 05:08, Sean Cole  wrote:

> Yeah, I could really do with it giving me some feedback as to where this
> object is. Actually, I could...
> ... I just wrote a plugin for it. Use scCreatePlugin "","" (scCreatePlugin
> on its own doesn't work from the message box like the dictionary suggests).
> Then in the script I used
>
> global gLastObject
>
> on savingProperties pLongId, @pProperteis
>--> your code
>put "saving properties of" && pLongId into gLastObject
>put word -2 to -1 of gLastObject
>wait 0.01 millisec with messages
> end savingProperties
>
> 
>
> Once I ran this it displayed which substack it was working on in the
> message box and once it had failed the global showed me the last parameter
> it had successfully accessed. Cool. But I still can't work out which
> parameter of either that object (a standard text field) or the next (a
> group with no behaviours or anything out of the ordinary as far as I can
> tell). I'll come back to it tomorrow. It's silly o'clock now.
>
> Sean
>
> On Wed, 31 Aug 2022 at 17:13, Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> On 8/31/22 03:00, Sean Cole via use-livecode wrote:
>>
>> > LC Team: :-) It would be REALLY handy if proper errors were thrown when
>> one
>> > occurs that can help us easily understand what the issues are. Also, if
>> > prior to release documentation were gone through to make sure they are
>> > legible. And if plugins released actually work as described. :-)
>>
>> Actually, it's even worse.
>> The result is empty if no error occurred and "* successful" if it
>> worked. To me that seems backwards.
>>
>> https://quality.livecode.com/show_bug.cgi?id=23911
>>
>> --
>>   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: Livecode / Github

[Geoff Canyon via use-livecode]

So all this discussion reminded me that I wrote an export/import stack
some time ago. I definitely don't still have a copy on my computer, so I
went looking on the web:

geoff canyon livecode export -- nothing useful, maybe it was in the runrev
era?

geoff canyon runrev export -- no luck.

I remembered that I used XML formatting for the export. Something like XML
Geoff Canyon export did the trick.

21 years ago? What??

Then off to archive.org to find the actual file: mcripper.mc And... I'm
looking at my ancient history!

I'm curious to try it on a large stack and see how it does.

gc


On Wed, Aug 31, 2022 at 9:10 PM Sean Cole via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Yeah, I could really do with it giving me some feedback as to where this
> object is. Actually, I could...
> ... I just wrote a plugin for it. Use scCreatePlugin "","" (scCreatePlugin
> on its own doesn't work from the message box like the dictionary suggests).
> Then in the script I used
>
> global gLastObject
>
> on savingProperties pLongId, @pProperteis
>--> your code
>put "saving properties of" && pLongId into gLastObject
>put word -2 to -1 of gLastObject
>wait 0.01 millisec with messages
> end savingProperties
>
> 
>
> Once I ran this it displayed which substack it was working on in the
> message box and once it had failed the global showed me the last parameter
> it had successfully accessed. Cool. But I still can't work out which
> parameter of either that object (a standard text field) or the next (a
> group with no behaviours or anything out of the ordinary as far as I can
> tell). I'll come back to it tomorrow. It's silly o'clock now.
>
> Sean
>
> On Wed, 31 Aug 2022 at 17:13, Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > On 8/31/22 03:00, Sean Cole via use-livecode wrote:
> >
> > > LC Team: :-) It would be REALLY handy if proper errors were thrown when
> > one
> > > occurs that can help us easily understand what the issues are. Also, if
> > > prior to release documentation were gone through to make sure they are
> > > legible. And if plugins released actually work as described. :-)
> >
> > Actually, it's even worse.
> > The result is empty if no error occurred and "* successful" if it
> > worked. To me that seems backwards.
> >
> > https://quality.livecode.com/show_bug.cgi?id=23911
> >
> > --
> >   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
>
___
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: Livecode / Github

[Sean Cole via use-livecode]

Yeah, I could really do with it giving me some feedback as to where this
object is. Actually, I could...
... I just wrote a plugin for it. Use scCreatePlugin "","" (scCreatePlugin
on its own doesn't work from the message box like the dictionary suggests).
Then in the script I used

global gLastObject

on savingProperties pLongId, @pProperteis
   --> your code
   put "saving properties of" && pLongId into gLastObject
   put word -2 to -1 of gLastObject
   wait 0.01 millisec with messages
end savingProperties



Once I ran this it displayed which substack it was working on in the
message box and once it had failed the global showed me the last parameter
it had successfully accessed. Cool. But I still can't work out which
parameter of either that object (a standard text field) or the next (a
group with no behaviours or anything out of the ordinary as far as I can
tell). I'll come back to it tomorrow. It's silly o'clock now.

Sean

On Wed, 31 Aug 2022 at 17:13, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 8/31/22 03:00, Sean Cole via use-livecode wrote:
>
> > LC Team: :-) It would be REALLY handy if proper errors were thrown when
> one
> > occurs that can help us easily understand what the issues are. Also, if
> > prior to release documentation were gone through to make sure they are
> > legible. And if plugins released actually work as described. :-)
>
> Actually, it's even worse.
> The result is empty if no error occurred and "* successful" if it
> worked. To me that seems backwards.
>
> https://quality.livecode.com/show_bug.cgi?id=23911
>
> --
>   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: Livecode / Github

[Mark Wieder via use-livecode]

On 8/31/22 03:00, Sean Cole via use-livecode wrote:


LC Team: :-) It would be REALLY handy if proper errors were thrown when one
occurs that can help us easily understand what the issues are. Also, if
prior to release documentation were gone through to make sure they are
legible. And if plugins released actually work as described. :-)


Actually, it's even worse.
The result is empty if no error occurred and "* successful" if it 
worked. To me that seems backwards.


https://quality.livecode.com/show_bug.cgi?id=23911

--
 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: Livecode / Github

[Mark Wieder via use-livecode]

On 8/31/22 07:58, Sean Cole via use-livecode wrote:

Thanks for the confirmation, Brian.

I tried again from the message box. With a stack this large it takes about
10 seconds before the mainStack disappears for exporting and then reappears
1 min later. About 4-8 mins after that it truely finishes where it flashes
up a white window for a moment then the error appears in the message box,
same as before, object does not have this property. Because everything is
handled using a GUID, I have no idea how far it has got nor which
particular object is causing the problem. We'll find it eventually, I'm
certain.


Was a log file created? scGetPathLog()
No logs were created for me, but just a thought.

https://quality.livecode.com/show_bug.cgi?id=23910

--
 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: Livecode / Github

[Sean Cole via use-livecode]

Thanks for the confirmation, Brian.

I tried again from the message box. With a stack this large it takes about
10 seconds before the mainStack disappears for exporting and then reappears
1 min later. About 4-8 mins after that it truely finishes where it flashes
up a white window for a moment then the error appears in the message box,
same as before, object does not have this property. Because everything is
handled using a GUID, I have no idea how far it has got nor which
particular object is causing the problem. We'll find it eventually, I'm
certain.

Sean

On Wed, 31 Aug 2022 at 15:48, Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> https://github.com/bwmilby/scriptTracker
>
> It appears that the JSON file does include all substacks.
>
> Brian Milby
> br...@milby7.com
>
> > On Aug 31, 2022, at 10:37 AM, Brian Milby  wrote:
> >
> > I’ll run it on my much smaller ScriptTracker stack (which has a couple
> substacks) and report my findings.
> >
> > Brian Milby
> > br...@milby7.com
> >
> >> On Aug 31, 2022, at 10:34 AM, Pi Digital via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>
> >> It created a smartcrumbs folder which contained 1 .livecode.sc folder
> which contained 3 subfolders, medias, scripts and shareTexts. medias
> contained 1 images folder with 2,325 jpeg files. The scripts folder
> contained 22,006 livecodescript files. The sharedTexts folders contained
> 7,352 GUID ref’d folders with one or more html files as well as 7,462
> separate html files. And that is all.
> >>
> >> Having tried again using the Export button from the magicPallet (which,
> because of the delay between pressing the button and it actually exporting,
> should have a spinner or something to show its working on it) I get the
> same result but this time with nothing in the message box or any log file.
> >>
> >> I’ll try again but from the message box. The guide definitely says it
> will create a json file in each .livecode.sc folder that contains
> information about other objects and substacks. It doesn’t say we need to
> export each substack individually. But the json file should hold info about
> all the other stuff as well. We’ll see.
> >>
> >> Sean Cole
> >> Pi Digital Productions Ltd
> >>
> >> eMail Ts & Cs
> >>
> >>
>  On 31 Aug 2022, at 13:46, Brian Milby via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> Had it created any of the script or other objects?  Curious whether
> it builds the JSON first or if it is done while exporting the other assets.
> >>>
> >>> Thanks,
> >>> Brian
> >>>
> > On Aug 31, 2022, at 6:02 AM, Sean Cole via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>  Well, I had to leave it overnight to finish exporting as it was
> clear to
>  take some time. This was for just the main stack, not my long list of
>  stacks. Looking at the message box this morning, though, has a
> response
> 
>  Message execution error:
>  Error description: Object: object does not have this property
>  Hint:
> 
>  'Object does not have this property' ?? What property? Thanks LC for
> giving
>  me all the information I need to fix it [shrugs]. It hasn't created
> the
>  JSON file in the main .sc folder so it must have abandoned the
> operation at
>  some point.
> 
>  I'll give it another go now after a reset and to another faster drive
> to
>  see if that improves things but with no other info to go on I have no
> idea
>  what needs to be done.
> 
>  LC Team: :-) It would be REALLY handy if proper errors were thrown
> when one
>  occurs that can help us easily understand what the issues are. Also,
> if
>  prior to release documentation were gone through to make sure they are
>  legible. And if plugins released actually work as described. :-)
> 
>  Sean
> 
> 
> > On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> >
> >>> On 8/30/22 19:36, Sean Cole via use-livecode wrote:
> >>> just another 96 stacks to go.
> >>> Looks like I'll set up an automation script.
> >
> > Ouch! I think the library would do well to check the password status
> and
> > allow entering and cacheing the password as necessary. Too bad it's
> > closed source so we can't fix it.
> >
> > --
> > 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://lis

Re: Livecode / Github

[Brian Milby via use-livecode]

https://github.com/bwmilby/scriptTracker

It appears that the JSON file does include all substacks.

Brian Milby
br...@milby7.com

> On Aug 31, 2022, at 10:37 AM, Brian Milby  wrote:
> 
> I’ll run it on my much smaller ScriptTracker stack (which has a couple 
> substacks) and report my findings.
> 
> Brian Milby
> br...@milby7.com
> 
>> On Aug 31, 2022, at 10:34 AM, Pi Digital via use-livecode 
>>  wrote:
>> 
>> It created a smartcrumbs folder which contained 1 .livecode.sc folder which 
>> contained 3 subfolders, medias, scripts and shareTexts. medias contained 1 
>> images folder with 2,325 jpeg files. The scripts folder contained 22,006 
>> livecodescript files. The sharedTexts folders contained 7,352 GUID ref’d 
>> folders with one or more html files as well as 7,462 separate html files. 
>> And that is all. 
>> 
>> Having tried again using the Export button from the magicPallet (which, 
>> because of the delay between pressing the button and it actually exporting, 
>> should have a spinner or something to show its working on it) I get the same 
>> result but this time with nothing in the message box or any log file. 
>> 
>> I’ll try again but from the message box. The guide definitely says it will 
>> create a json file in each .livecode.sc folder that contains information 
>> about other objects and substacks. It doesn’t say we need to export each 
>> substack individually. But the json file should hold info about all the 
>> other stuff as well. We’ll see. 
>> 
>> Sean Cole
>> Pi Digital Productions Ltd
>> 
>> eMail Ts & Cs
>> 
>> 
 On 31 Aug 2022, at 13:46, Brian Milby via use-livecode 
  wrote:
>>> 
>>> Had it created any of the script or other objects?  Curious whether it 
>>> builds the JSON first or if it is done while exporting the other assets.
>>> 
>>> Thanks,
>>> Brian
>>> 
> On Aug 31, 2022, at 6:02 AM, Sean Cole via use-livecode 
>  wrote:
 
 Well, I had to leave it overnight to finish exporting as it was clear to
 take some time. This was for just the main stack, not my long list of
 stacks. Looking at the message box this morning, though, has a response
 
 Message execution error:
 Error description: Object: object does not have this property
 Hint:
 
 'Object does not have this property' ?? What property? Thanks LC for giving
 me all the information I need to fix it [shrugs]. It hasn't created the
 JSON file in the main .sc folder so it must have abandoned the operation at
 some point.
 
 I'll give it another go now after a reset and to another faster drive to
 see if that improves things but with no other info to go on I have no idea
 what needs to be done.
 
 LC Team: :-) It would be REALLY handy if proper errors were thrown when one
 occurs that can help us easily understand what the issues are. Also, if
 prior to release documentation were gone through to make sure they are
 legible. And if plugins released actually work as described. :-)
 
 Sean
 
 
> On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> 
>>> On 8/30/22 19:36, Sean Cole via use-livecode wrote:
>>> just another 96 stacks to go.
>>> Looks like I'll set up an automation script.
> 
> Ouch! I think the library would do well to check the password status and
> allow entering and cacheing the password as necessary. Too bad it's
> closed source so we can't fix it.
> 
> --
> 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
>>> 
>>> ___
>>> 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
___
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: Livecode / Github

[Brian Milby via use-livecode]

I’ll run it on my much smaller ScriptTracker stack (which has a couple 
substacks) and report my findings.

Brian Milby
br...@milby7.com

> On Aug 31, 2022, at 10:34 AM, Pi Digital via use-livecode 
>  wrote:
> 
> It created a smartcrumbs folder which contained 1 .livecode.sc folder which 
> contained 3 subfolders, medias, scripts and shareTexts. medias contained 1 
> images folder with 2,325 jpeg files. The scripts folder contained 22,006 
> livecodescript files. The sharedTexts folders contained 7,352 GUID ref’d 
> folders with one or more html files as well as 7,462 separate html files. And 
> that is all. 
> 
> Having tried again using the Export button from the magicPallet (which, 
> because of the delay between pressing the button and it actually exporting, 
> should have a spinner or something to show its working on it) I get the same 
> result but this time with nothing in the message box or any log file. 
> 
> I’ll try again but from the message box. The guide definitely says it will 
> create a json file in each .livecode.sc folder that contains information 
> about other objects and substacks. It doesn’t say we need to export each 
> substack individually. But the json file should hold info about all the other 
> stuff as well. We’ll see. 
> 
> Sean Cole
> Pi Digital Productions Ltd
> 
> eMail Ts & Cs
> 
> 
>> On 31 Aug 2022, at 13:46, Brian Milby via use-livecode 
>>  wrote:
>> 
>> Had it created any of the script or other objects?  Curious whether it 
>> builds the JSON first or if it is done while exporting the other assets.
>> 
>> Thanks,
>> Brian
>> 
 On Aug 31, 2022, at 6:02 AM, Sean Cole via use-livecode 
  wrote:
>>> 
>>> Well, I had to leave it overnight to finish exporting as it was clear to
>>> take some time. This was for just the main stack, not my long list of
>>> stacks. Looking at the message box this morning, though, has a response
>>> 
>>> Message execution error:
>>> Error description: Object: object does not have this property
>>> Hint:
>>> 
>>> 'Object does not have this property' ?? What property? Thanks LC for giving
>>> me all the information I need to fix it [shrugs]. It hasn't created the
>>> JSON file in the main .sc folder so it must have abandoned the operation at
>>> some point.
>>> 
>>> I'll give it another go now after a reset and to another faster drive to
>>> see if that improves things but with no other info to go on I have no idea
>>> what needs to be done.
>>> 
>>> LC Team: :-) It would be REALLY handy if proper errors were thrown when one
>>> occurs that can help us easily understand what the issues are. Also, if
>>> prior to release documentation were gone through to make sure they are
>>> legible. And if plugins released actually work as described. :-)
>>> 
>>> Sean
>>> 
>>> 
 On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode <
 use-livecode@lists.runrev.com> wrote:
 
>> On 8/30/22 19:36, Sean Cole via use-livecode wrote:
>> just another 96 stacks to go.
>> Looks like I'll set up an automation script.
 
 Ouch! I think the library would do well to check the password status and
 allow entering and cacheing the password as necessary. Too bad it's
 closed source so we can't fix it.
 
 --
 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
>> 
>> ___
>> 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

___
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: Livecode / Github

[Pi Digital via use-livecode]

It created a smartcrumbs folder which contained 1 .livecode.sc folder which 
contained 3 subfolders, medias, scripts and shareTexts. medias contained 1 
images folder with 2,325 jpeg files. The scripts folder contained 22,006 
livecodescript files. The sharedTexts folders contained 7,352 GUID ref’d 
folders with one or more html files as well as 7,462 separate html files. And 
that is all. 

Having tried again using the Export button from the magicPallet (which, because 
of the delay between pressing the button and it actually exporting, should have 
a spinner or something to show its working on it) I get the same result but 
this time with nothing in the message box or any log file. 

I’ll try again but from the message box. The guide definitely says it will 
create a json file in each .livecode.sc folder that contains information about 
other objects and substacks. It doesn’t say we need to export each substack 
individually. But the json file should hold info about all the other stuff as 
well. We’ll see. 

Sean Cole
Pi Digital Productions Ltd

eMail Ts & Cs


> On 31 Aug 2022, at 13:46, Brian Milby via use-livecode 
>  wrote:
> 
> Had it created any of the script or other objects?  Curious whether it 
> builds the JSON first or if it is done while exporting the other assets.
> 
> Thanks,
> Brian
> 
>> On Aug 31, 2022, at 6:02 AM, Sean Cole via use-livecode 
>>  wrote:
>> 
>> Well, I had to leave it overnight to finish exporting as it was clear to
>> take some time. This was for just the main stack, not my long list of
>> stacks. Looking at the message box this morning, though, has a response
>> 
>> Message execution error:
>> Error description: Object: object does not have this property
>> Hint:
>> 
>> 'Object does not have this property' ?? What property? Thanks LC for giving
>> me all the information I need to fix it [shrugs]. It hasn't created the
>> JSON file in the main .sc folder so it must have abandoned the operation at
>> some point.
>> 
>> I'll give it another go now after a reset and to another faster drive to
>> see if that improves things but with no other info to go on I have no idea
>> what needs to be done.
>> 
>> LC Team: :-) It would be REALLY handy if proper errors were thrown when one
>> occurs that can help us easily understand what the issues are. Also, if
>> prior to release documentation were gone through to make sure they are
>> legible. And if plugins released actually work as described. :-)
>> 
>> Sean
>> 
>> 
>>> On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode <
>>> use-livecode@lists.runrev.com> wrote:
>>> 
> On 8/30/22 19:36, Sean Cole via use-livecode wrote:
> just another 96 stacks to go.
> Looks like I'll set up an automation script.
>>> 
>>> Ouch! I think the library would do well to check the password status and
>>> allow entering and cacheing the password as necessary. Too bad it's
>>> closed source so we can't fix it.
>>> 
>>> --
>>> 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
> 
> ___
> 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: Livecode / Github

[Brian Milby via use-livecode]

Had it created any of the script or other objects?  Curious whether it builds 
the JSON first or if it is done while exporting the other assets.

Thanks,
Brian

> On Aug 31, 2022, at 6:02 AM, Sean Cole via use-livecode 
>  wrote:
> 
> Well, I had to leave it overnight to finish exporting as it was clear to
> take some time. This was for just the main stack, not my long list of
> stacks. Looking at the message box this morning, though, has a response
> 
> Message execution error:
> Error description: Object: object does not have this property
> Hint:
> 
> 'Object does not have this property' ?? What property? Thanks LC for giving
> me all the information I need to fix it [shrugs]. It hasn't created the
> JSON file in the main .sc folder so it must have abandoned the operation at
> some point.
> 
> I'll give it another go now after a reset and to another faster drive to
> see if that improves things but with no other info to go on I have no idea
> what needs to be done.
> 
> LC Team: :-) It would be REALLY handy if proper errors were thrown when one
> occurs that can help us easily understand what the issues are. Also, if
> prior to release documentation were gone through to make sure they are
> legible. And if plugins released actually work as described. :-)
> 
> Sean
> 
> 
>> On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>>> On 8/30/22 19:36, Sean Cole via use-livecode wrote:
>>> just another 96 stacks to go.
>>> Looks like I'll set up an automation script.
>> 
>> Ouch! I think the library would do well to check the password status and
>> allow entering and cacheing the password as necessary. Too bad it's
>> closed source so we can't fix it.
>> 
>> --
>>  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

___
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: Livecode / Github

[Sean Cole via use-livecode]

Well, I had to leave it overnight to finish exporting as it was clear to
take some time. This was for just the main stack, not my long list of
stacks. Looking at the message box this morning, though, has a response

Message execution error:
Error description: Object: object does not have this property
Hint:

'Object does not have this property' ?? What property? Thanks LC for giving
me all the information I need to fix it [shrugs]. It hasn't created the
JSON file in the main .sc folder so it must have abandoned the operation at
some point.

I'll give it another go now after a reset and to another faster drive to
see if that improves things but with no other info to go on I have no idea
what needs to be done.

LC Team: :-) It would be REALLY handy if proper errors were thrown when one
occurs that can help us easily understand what the issues are. Also, if
prior to release documentation were gone through to make sure they are
legible. And if plugins released actually work as described. :-)

Sean


On Wed, 31 Aug 2022 at 04:05, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 8/30/22 19:36, Sean Cole via use-livecode wrote:
> > just another 96 stacks to go.
> > Looks like I'll set up an automation script.
>
> Ouch! I think the library would do well to check the password status and
> allow entering and cacheing the password as necessary. Too bad it's
> closed source so we can't fix it.
>
> --
>   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: Livecode / Github

[Mark Wieder via use-livecode]

On 8/30/22 19:36, Sean Cole via use-livecode wrote:

just another 96 stacks to go.
Looks like I'll set up an automation script.


Ouch! I think the library would do well to check the password status and 
allow entering and cacheing the password as necessary. Too bad it's 
closed source so we can't fix it.


--
 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: Livecode / Github

[Sean Cole via use-livecode]

Don't worry, it was password protected. I thought it had managed to remove
the protection but the script I ran to remove it from the 97 stacks didn;t
do it properly. So I did it again and then needed to restart LC first for
it to fully recognise the protection removed. All good now. MainStack
exported (it's massive so it took some time). just another 96 stacks to go.
Looks like I'll set up an automation script.

Sean Cole
*Pi Digital Productions Ltd*
www.pidigital.co.uk
+44(1634)402193
+44(7702)116447

'Don't try to think outside the box. Just remember the truth: There is no
box!'
'For then you realise it is not the box you are trying to look outside of,
but it is yourself!'

eMail Ts & Cs    Pi Digital
Productions Ltd is a UK registered limited company, no. 5255609


On Wed, 31 Aug 2022 at 03:02, Sean Cole  wrote:

> Hi Mark,
>
> When you said this, how did you use it to get it to work? I'm getting the
> same issues as you were.
>
> Thanks
> Sean
>
> On Mon, 29 Aug 2022 at 20:06, Mark Wieder via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>>
>> Ah. OK - So I had to look up the filename of the stack first.
>>
>>
___
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: Livecode / Github

[Sean Cole via use-livecode]

Hi Mark,

When you said this, how did you use it to get it to work? I'm getting the
same issues as you were.

Thanks
Sean

On Mon, 29 Aug 2022 at 20:06, Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

>
> Ah. OK - So I had to look up the filename of the stack first.
>
>
___
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: Livecode / Github

[Mark Wieder via use-livecode]

On 8/29/22 12:22, Pi Digital via use-livecode wrote:

Look at the guide in the guide section of the dictionary app. It formats okay 
(although I’m going through and rewriting the grammar to send for an update).


Thanks, Sean. Yeah - that does format much better in a browser.

--
 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: Livecode / Github

[Pi Digital via use-livecode]

Look at the guide in the guide section of the dictionary app. It formats okay 
(although I’m going through and rewriting the grammar to send for an update).

Thanks Brian for the heads up on MagicPallet. I hadn’t looked to see what that 
was for yet. It’s all early stages yet but it’s looking very promising. 

Sean Cole
Pi Digital Productions Ltd

eMail Ts & Cs


> On 29 Aug 2022, at 20:06, Mark Wieder via use-livecode 
>  wrote:
> 
> On 8/29/22 10:53, Brian Milby via use-livecode wrote:
>> I used Magic Palette to do the export.  It should create the folder
>> structure next to the stack file that was the topstack in the IDE.
> 
> Ah. OK - So I had to look up the filename of the stack first.
> Would have been nice if the nonexistent log file told me that.
> 
>> I have not looked at the lesson though.
> 
> Not missing anything there.
> I've just been going by the dictionary entries.
> But now I've opened the guide.md file and see more, although the formatting 
> is wonky. Gotta love the fact that the TOC entry is "Unknown". Looks like it 
> was rushed out the door.
> 
> -- 
> -- 
> 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: Livecode / Github

[Mark Wieder via use-livecode]

On 8/29/22 10:53, Brian Milby via use-livecode wrote:

I used Magic Palette to do the export.  It should create the folder
structure next to the stack file that was the topstack in the IDE.


Ah. OK - So I had to look up the filename of the stack first.
Would have been nice if the nonexistent log file told me that.


I have not looked at the lesson though.


Not missing anything there.
I've just been going by the dictionary entries.
But now I've opened the guide.md file and see more, although the 
formatting is wonky. Gotta love the fact that the TOC entry is 
"Unknown". Looks like it was rushed out the door.


--
--
 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: Livecode / Github

[Brian Milby via use-livecode]

I used Magic Palette to do the export.  It should create the folder
structure next to the stack file that was the topstack in the IDE.
I have not looked at the lesson though.

On Mon, Aug 29, 2022 at 1:31 PM Mark Wieder via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On 8/28/22 20:45, Brian Milby via use-livecode wrote:
> > If you want to see what the JSON export looks like for a fairly small
> > stack, you can view this:
> >
> https://github.com/bwmilby/SvgIconTool/blob/main/smartcrumbs/SvgIconTool.livecode.sc/stackFileProperties.json
> >
> > Unfortunately you will need to download and view it with something that
> > understands the CR line ending since GitHub doesn't.  That repo has both
> > ScriptTracker exports and SmartCrumbs exports of the stack.  The former
> is
> > designed with two things in mind:  allowing changes in the scripts that
> are
> > part of a binary stack to be tracked and allowing the editing of those
> > scripts in an external editor (I like Atom for the linting, have not
> tried
> > the newer option).  The latter looks to be a way to completely decompose
> a
> > stack into mostly text files (images being one exception) that can be
> > tracked (and in theory changes merged together I'm guessing).
>
> OK - I just tried out smartcrumbs to check it out. Not quite sure what's
> going on here. Outsmarted by smartcrumbs.
>
> According to the lesson you just drag this onto a stack.
> Nope.
> Click the "Export Stack" button.
> Stack flickers.
> Did anything happen?
> According to the dictionary there's an scGetPathLog().
> Maybe that will give me a clue.
> /My LiveCode/SmartCrumbsVCW/logs//2022-08-29
> Eh?
> What's this "/My LiveCode" thing? I don't have one of those.
> And why is it trying to store that off my root directory?
> Let's try that one again.
> "Recursion limit reached"
> I'll try scExportStack from the message box.
> It gives "can't find handler"
>
> OK - back to real work.
>
> --
>   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: Livecode / Github

[Mark Wieder via use-livecode]

On 8/28/22 20:45, Brian Milby via use-livecode wrote:

If you want to see what the JSON export looks like for a fairly small
stack, you can view this:
https://github.com/bwmilby/SvgIconTool/blob/main/smartcrumbs/SvgIconTool.livecode.sc/stackFileProperties.json

Unfortunately you will need to download and view it with something that
understands the CR line ending since GitHub doesn't.  That repo has both
ScriptTracker exports and SmartCrumbs exports of the stack.  The former is
designed with two things in mind:  allowing changes in the scripts that are
part of a binary stack to be tracked and allowing the editing of those
scripts in an external editor (I like Atom for the linting, have not tried
the newer option).  The latter looks to be a way to completely decompose a
stack into mostly text files (images being one exception) that can be
tracked (and in theory changes merged together I'm guessing).


OK - I just tried out smartcrumbs to check it out. Not quite sure what's 
going on here. Outsmarted by smartcrumbs.


According to the lesson you just drag this onto a stack.
Nope.
Click the "Export Stack" button.
Stack flickers.
Did anything happen?
According to the dictionary there's an scGetPathLog().
Maybe that will give me a clue.
/My LiveCode/SmartCrumbsVCW/logs//2022-08-29
Eh?
What's this "/My LiveCode" thing? I don't have one of those.
And why is it trying to store that off my root directory?
Let's try that one again.
"Recursion limit reached"
I'll try scExportStack from the message box.
It gives "can't find handler"

OK - back to real work.

--
 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: Livecode / Github

[Mike Kerner via use-livecode]

I would love for us to get to a place where we could have it both ways.

On Sun, Aug 28, 2022 at 11:46 PM Brian Milby via use-livecode <
use-livecode@lists.runrev.com> wrote:

> If you want to see what the JSON export looks like for a fairly small
> stack, you can view this:
>
> https://github.com/bwmilby/SvgIconTool/blob/main/smartcrumbs/SvgIconTool.livecode.sc/stackFileProperties.json
>
> Unfortunately you will need to download and view it with something that
> understands the CR line ending since GitHub doesn't.  That repo has both
> ScriptTracker exports and SmartCrumbs exports of the stack.  The former is
> designed with two things in mind:  allowing changes in the scripts that are
> part of a binary stack to be tracked and allowing the editing of those
> scripts in an external editor (I like Atom for the linting, have not tried
> the newer option).  The latter looks to be a way to completely decompose a
> stack into mostly text files (images being one exception) that can be
> tracked (and in theory changes merged together I'm guessing).
>
> Since the JSON file is keyed off of the GUIDs of each object, it really
> doesn't lend itself to human inspection.  Assuming line endings are sane
> (probably would work for Windows and definitely will work for Linux), Git
> should easily be able to track the changes.  Whether someone could easily
> discern which object was being touched is another matter (which would be
> necessary to merge changes together).
>
> On Sun, Aug 28, 2022 at 9:31 PM Pi Digital via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > It will be good to see, once available, how using the new SmartCrumbs add
> > on will help with this. All objects in JSON form and then use stack
> scripts
> > (and htmlText, AudioClip and VideoClip data) in your GitHub repository.
> > This is something I really want to start implementing.
> >
> > Sean
> >
> >
> > > On 28 Aug 2022, at 20:29, Geoff Canyon  wrote:
> > >
> > > 
> > > To be clear: if anyone wants to try Navigator's export to script
> > behaviors function -- work on a copy, and I'd love feedback.
> > >
> > >> On Sun, Aug 28, 2022 at 10:35 AM Geoff Canyon 
> > wrote:
> > >> The same applies to the code in Navigator. I wrote it about five years
> > ago when I was preparing to transform Navigator itself to use script
> > behaviors.
> > >>
> > >> Always work on a copy.
> > >>
> > >> That said, it worked fine for Navigator, and no one has ever told me
> it
> > broke anything.
> > >>
> > >> gc
> > >>
> > >>> On Thu, Aug 18, 2022 at 10:06 PM Pi Digital via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> > >>> I tried scriptifier and it broke stuff so just be careful with it and
> > check its output.
> > >>>
> > >>> Sean
> > >>>
> > >>>
> > >>> > On 19 Aug 2022, at 01:39, Mike Kerner via use-livecode <
> > use-livecode@lists.runrev.com> wrote:
> > >>> >
> > >>> > Hey Skip, long time...
> > >>> > I don't know if you were around when script-only-stack behaviors
> > came into
> > >>> > being, but you can now rip all of the code out of your stacks and
> > happily
> > >>> > use vc/git. The stacks themselves are still binary (although
> several
> > of us
> > >>> > have been messing with dumping that paradigm completely, it's less
> > >>> > practical than I would have hoped, as of today).
> > >>> > Navigator will export every script in a project into behavior
> > stacks, and
> > >>> > Monte wrote a stack called "Scriptifier", if memory serves. It's
> > embedded
> > >>> > in the LC bundle, and it does the same thing, namely extracting all
> > the
> > >>> > scripts out of a project and putting them into .livecodescript text
> > files.
> > >>> > Levure is great. I have used it with every project I've worked on
> for
> > >>> > several years, BUT you don't have to use it to go this route.
> > >>> >
> > >>> >> On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
> > >>> >> use-livecode@lists.runrev.com> wrote:
> > >>> >>
> > >>> >> Hi SKIP
> > >>> >>
> > >>> >> Welcome back to the list!
> > >>> >>
> > >>> >> There is Levure which I knew of as a third party application
> > framework
> > >>> >> created by Trevor DeVore but I just did a search for it and I see
> > it now on
> > >>> >> the LiveCode website described as an App Collaboration Framework.
> > >>> >> https://livecode.com/products/livecode-platform/levure/ <
> > >>> >> https://livecode.com/products/livecode-platform/levure/>  So it
> > must have
> > >>> >> at some point migrated to the mother ship.
> > >>> >>
> > >>> >> I haven’t used it but I have considered migrating my application
> to
> > it.
> > >>> >> It works with version control systems as long as you follow its
> > >>> >> recommendations about how to organize your code into behaviours
> > that are
> > >>> >> stored in script only stacks which are just text files that a
> > version
> > >>> >> control system can read (These are somewhat new so depending on
> > when you
> > >>> >> last used LiveCode they may be new to you.

Re: Livecode / Github

[Brian Milby via use-livecode]

If you want to see what the JSON export looks like for a fairly small
stack, you can view this:
https://github.com/bwmilby/SvgIconTool/blob/main/smartcrumbs/SvgIconTool.livecode.sc/stackFileProperties.json

Unfortunately you will need to download and view it with something that
understands the CR line ending since GitHub doesn't.  That repo has both
ScriptTracker exports and SmartCrumbs exports of the stack.  The former is
designed with two things in mind:  allowing changes in the scripts that are
part of a binary stack to be tracked and allowing the editing of those
scripts in an external editor (I like Atom for the linting, have not tried
the newer option).  The latter looks to be a way to completely decompose a
stack into mostly text files (images being one exception) that can be
tracked (and in theory changes merged together I'm guessing).

Since the JSON file is keyed off of the GUIDs of each object, it really
doesn't lend itself to human inspection.  Assuming line endings are sane
(probably would work for Windows and definitely will work for Linux), Git
should easily be able to track the changes.  Whether someone could easily
discern which object was being touched is another matter (which would be
necessary to merge changes together).

On Sun, Aug 28, 2022 at 9:31 PM Pi Digital via use-livecode <
use-livecode@lists.runrev.com> wrote:

> It will be good to see, once available, how using the new SmartCrumbs add
> on will help with this. All objects in JSON form and then use stack scripts
> (and htmlText, AudioClip and VideoClip data) in your GitHub repository.
> This is something I really want to start implementing.
>
> Sean
>
>
> > On 28 Aug 2022, at 20:29, Geoff Canyon  wrote:
> >
> > 
> > To be clear: if anyone wants to try Navigator's export to script
> behaviors function -- work on a copy, and I'd love feedback.
> >
> >> On Sun, Aug 28, 2022 at 10:35 AM Geoff Canyon 
> wrote:
> >> The same applies to the code in Navigator. I wrote it about five years
> ago when I was preparing to transform Navigator itself to use script
> behaviors.
> >>
> >> Always work on a copy.
> >>
> >> That said, it worked fine for Navigator, and no one has ever told me it
> broke anything.
> >>
> >> gc
> >>
> >>> On Thu, Aug 18, 2022 at 10:06 PM Pi Digital via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>> I tried scriptifier and it broke stuff so just be careful with it and
> check its output.
> >>>
> >>> Sean
> >>>
> >>>
> >>> > On 19 Aug 2022, at 01:39, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >>> >
> >>> > Hey Skip, long time...
> >>> > I don't know if you were around when script-only-stack behaviors
> came into
> >>> > being, but you can now rip all of the code out of your stacks and
> happily
> >>> > use vc/git. The stacks themselves are still binary (although several
> of us
> >>> > have been messing with dumping that paradigm completely, it's less
> >>> > practical than I would have hoped, as of today).
> >>> > Navigator will export every script in a project into behavior
> stacks, and
> >>> > Monte wrote a stack called "Scriptifier", if memory serves. It's
> embedded
> >>> > in the LC bundle, and it does the same thing, namely extracting all
> the
> >>> > scripts out of a project and putting them into .livecodescript text
> files.
> >>> > Levure is great. I have used it with every project I've worked on for
> >>> > several years, BUT you don't have to use it to go this route.
> >>> >
> >>> >> On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
> >>> >> use-livecode@lists.runrev.com> wrote:
> >>> >>
> >>> >> Hi SKIP
> >>> >>
> >>> >> Welcome back to the list!
> >>> >>
> >>> >> There is Levure which I knew of as a third party application
> framework
> >>> >> created by Trevor DeVore but I just did a search for it and I see
> it now on
> >>> >> the LiveCode website described as an App Collaboration Framework.
> >>> >> https://livecode.com/products/livecode-platform/levure/ <
> >>> >> https://livecode.com/products/livecode-platform/levure/>  So it
> must have
> >>> >> at some point migrated to the mother ship.
> >>> >>
> >>> >> I haven’t used it but I have considered migrating my application to
> it.
> >>> >> It works with version control systems as long as you follow its
> >>> >> recommendations about how to organize your code into behaviours
> that are
> >>> >> stored in script only stacks which are just text files that a
> version
> >>> >> control system can read (These are somewhat new so depending on
> when you
> >>> >> last used LiveCode they may be new to you.)  This was an
> enhancement that
> >>> >> has enabled the use of version control for scripts in a project. It
> is the
> >>> >> binary stacks that versions control systems can’t track so in
> Levure those
> >>> >> are just used for user interface.
> >>> >>
> >>> >> Hope this helps.
> >>> >>
> >>> >> Martin
> >>> >>
> >>> >>
> >>> >>> On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode <
> >>>

Re: Livecode / Github

[Pi Digital via use-livecode]

It will be good to see, once available, how using the new SmartCrumbs add on 
will help with this. All objects in JSON form and then use stack scripts (and 
htmlText, AudioClip and VideoClip data) in your GitHub repository. This is 
something I really want to start implementing. 

Sean


> On 28 Aug 2022, at 20:29, Geoff Canyon  wrote:
> 
> 
> To be clear: if anyone wants to try Navigator's export to script behaviors 
> function -- work on a copy, and I'd love feedback.
> 
>> On Sun, Aug 28, 2022 at 10:35 AM Geoff Canyon  wrote:
>> The same applies to the code in Navigator. I wrote it about five years ago 
>> when I was preparing to transform Navigator itself to use script behaviors. 
>> 
>> Always work on a copy.
>> 
>> That said, it worked fine for Navigator, and no one has ever told me it 
>> broke anything.
>> 
>> gc
>> 
>>> On Thu, Aug 18, 2022 at 10:06 PM Pi Digital via use-livecode 
>>>  wrote:
>>> I tried scriptifier and it broke stuff so just be careful with it and check 
>>> its output. 
>>> 
>>> Sean
>>> 
>>> 
>>> > On 19 Aug 2022, at 01:39, Mike Kerner via use-livecode 
>>> >  wrote:
>>> > 
>>> > Hey Skip, long time...
>>> > I don't know if you were around when script-only-stack behaviors came into
>>> > being, but you can now rip all of the code out of your stacks and happily
>>> > use vc/git. The stacks themselves are still binary (although several of us
>>> > have been messing with dumping that paradigm completely, it's less
>>> > practical than I would have hoped, as of today).
>>> > Navigator will export every script in a project into behavior stacks, and
>>> > Monte wrote a stack called "Scriptifier", if memory serves. It's embedded
>>> > in the LC bundle, and it does the same thing, namely extracting all the
>>> > scripts out of a project and putting them into .livecodescript text files.
>>> > Levure is great. I have used it with every project I've worked on for
>>> > several years, BUT you don't have to use it to go this route.
>>> > 
>>> >> On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
>>> >> use-livecode@lists.runrev.com> wrote:
>>> >> 
>>> >> Hi SKIP
>>> >> 
>>> >> Welcome back to the list!
>>> >> 
>>> >> There is Levure which I knew of as a third party application framework
>>> >> created by Trevor DeVore but I just did a search for it and I see it now 
>>> >> on
>>> >> the LiveCode website described as an App Collaboration Framework.
>>> >> https://livecode.com/products/livecode-platform/levure/ <
>>> >> https://livecode.com/products/livecode-platform/levure/>  So it must have
>>> >> at some point migrated to the mother ship.
>>> >> 
>>> >> I haven’t used it but I have considered migrating my application to it.
>>> >> It works with version control systems as long as you follow its
>>> >> recommendations about how to organize your code into behaviours that are
>>> >> stored in script only stacks which are just text files that a version
>>> >> control system can read (These are somewhat new so depending on when you
>>> >> last used LiveCode they may be new to you.)  This was an enhancement that
>>> >> has enabled the use of version control for scripts in a project. It is 
>>> >> the
>>> >> binary stacks that versions control systems can’t track so in Levure 
>>> >> those
>>> >> are just used for user interface.
>>> >> 
>>> >> Hope this helps.
>>> >> 
>>> >> Martin
>>> >> 
>>> >> 
>>> >>> On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode <
>>> >> use-livecode@lists.runrev.com> wrote:
>>> >>> 
>>> >>> Greetings!
>>> >>> 
>>> >>> Been a while since I have been on this list.  Working on a new project
>>> >> and
>>> >>> wondering if the backing up of Livecode files to Github was ever
>>> >>> implemented and created.  I know there was talk of it at one time.
>>> >>> 
>>> >>> I apologize if it has been in place for a while and I am just out of the
>>> >>> loop.  Actually, I HOPE that is the case!
>>> >>> 
>>> >>> Regards,
>>> >>> 
>>> >>> SKIP
>>> >>> ___
>>> >>> 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, un

Re: Livecode / Github

[Geoff Canyon via use-livecode]

To be clear: if anyone wants to try Navigator's export to script behaviors
function -- work on a copy, and I'd love feedback.

On Sun, Aug 28, 2022 at 10:35 AM Geoff Canyon  wrote:

> The same applies to the code in Navigator. I wrote it about five years ago
> when I was preparing to transform Navigator itself to use script behaviors.
>
> Always work on a copy.
>
> That said, it worked fine for Navigator, and no one has ever told me it
> broke anything.
>
> gc
>
> On Thu, Aug 18, 2022 at 10:06 PM Pi Digital via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
>> I tried scriptifier and it broke stuff so just be careful with it and
>> check its output.
>>
>> Sean
>>
>>
>> > On 19 Aug 2022, at 01:39, Mike Kerner via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> >
>> > Hey Skip, long time...
>> > I don't know if you were around when script-only-stack behaviors came
>> into
>> > being, but you can now rip all of the code out of your stacks and
>> happily
>> > use vc/git. The stacks themselves are still binary (although several of
>> us
>> > have been messing with dumping that paradigm completely, it's less
>> > practical than I would have hoped, as of today).
>> > Navigator will export every script in a project into behavior stacks,
>> and
>> > Monte wrote a stack called "Scriptifier", if memory serves. It's
>> embedded
>> > in the LC bundle, and it does the same thing, namely extracting all the
>> > scripts out of a project and putting them into .livecodescript text
>> files.
>> > Levure is great. I have used it with every project I've worked on for
>> > several years, BUT you don't have to use it to go this route.
>> >
>> >> On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
>> >> use-livecode@lists.runrev.com> wrote:
>> >>
>> >> Hi SKIP
>> >>
>> >> Welcome back to the list!
>> >>
>> >> There is Levure which I knew of as a third party application framework
>> >> created by Trevor DeVore but I just did a search for it and I see it
>> now on
>> >> the LiveCode website described as an App Collaboration Framework.
>> >> https://livecode.com/products/livecode-platform/levure/ <
>> >> https://livecode.com/products/livecode-platform/levure/>  So it must
>> have
>> >> at some point migrated to the mother ship.
>> >>
>> >> I haven’t used it but I have considered migrating my application to it.
>> >> It works with version control systems as long as you follow its
>> >> recommendations about how to organize your code into behaviours that
>> are
>> >> stored in script only stacks which are just text files that a version
>> >> control system can read (These are somewhat new so depending on when
>> you
>> >> last used LiveCode they may be new to you.)  This was an enhancement
>> that
>> >> has enabled the use of version control for scripts in a project. It is
>> the
>> >> binary stacks that versions control systems can’t track so in Levure
>> those
>> >> are just used for user interface.
>> >>
>> >> Hope this helps.
>> >>
>> >> Martin
>> >>
>> >>
>> >>> On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode <
>> >> use-livecode@lists.runrev.com> wrote:
>> >>>
>> >>> Greetings!
>> >>>
>> >>> Been a while since I have been on this list.  Working on a new project
>> >> and
>> >>> wondering if the backing up of Livecode files to Github was ever
>> >>> implemented and created.  I know there was talk of it at one time.
>> >>>
>> >>> I apologize if it has been in place for a while and I am just out of
>> the
>> >>> loop.  Actually, I HOPE that is the case!
>> >>>
>> >>> Regards,
>> >>>
>> >>> SKIP
>> >>> ___
>> >>> 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-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: Livecode / Github

[Geoff Canyon via use-livecode]

The same applies to the code in Navigator. I wrote it about five years ago
when I was preparing to transform Navigator itself to use script behaviors.

Always work on a copy.

That said, it worked fine for Navigator, and no one has ever told me it
broke anything.

gc

On Thu, Aug 18, 2022 at 10:06 PM Pi Digital via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I tried scriptifier and it broke stuff so just be careful with it and
> check its output.
>
> Sean
>
>
> > On 19 Aug 2022, at 01:39, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Hey Skip, long time...
> > I don't know if you were around when script-only-stack behaviors came
> into
> > being, but you can now rip all of the code out of your stacks and happily
> > use vc/git. The stacks themselves are still binary (although several of
> us
> > have been messing with dumping that paradigm completely, it's less
> > practical than I would have hoped, as of today).
> > Navigator will export every script in a project into behavior stacks, and
> > Monte wrote a stack called "Scriptifier", if memory serves. It's embedded
> > in the LC bundle, and it does the same thing, namely extracting all the
> > scripts out of a project and putting them into .livecodescript text
> files.
> > Levure is great. I have used it with every project I've worked on for
> > several years, BUT you don't have to use it to go this route.
> >
> >> On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>
> >> Hi SKIP
> >>
> >> Welcome back to the list!
> >>
> >> There is Levure which I knew of as a third party application framework
> >> created by Trevor DeVore but I just did a search for it and I see it
> now on
> >> the LiveCode website described as an App Collaboration Framework.
> >> https://livecode.com/products/livecode-platform/levure/ <
> >> https://livecode.com/products/livecode-platform/levure/>  So it must
> have
> >> at some point migrated to the mother ship.
> >>
> >> I haven’t used it but I have considered migrating my application to it.
> >> It works with version control systems as long as you follow its
> >> recommendations about how to organize your code into behaviours that are
> >> stored in script only stacks which are just text files that a version
> >> control system can read (These are somewhat new so depending on when you
> >> last used LiveCode they may be new to you.)  This was an enhancement
> that
> >> has enabled the use of version control for scripts in a project. It is
> the
> >> binary stacks that versions control systems can’t track so in Levure
> those
> >> are just used for user interface.
> >>
> >> Hope this helps.
> >>
> >> Martin
> >>
> >>
> >>> On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode <
> >> use-livecode@lists.runrev.com> wrote:
> >>>
> >>> Greetings!
> >>>
> >>> Been a while since I have been on this list.  Working on a new project
> >> and
> >>> wondering if the backing up of Livecode files to Github was ever
> >>> implemented and created.  I know there was talk of it at one time.
> >>>
> >>> I apologize if it has been in place for a while and I am just out of
> the
> >>> loop.  Actually, I HOPE that is the case!
> >>>
> >>> Regards,
> >>>
> >>> SKIP
> >>> ___
> >>> 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-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: Livecode / Github

[Pi Digital via use-livecode]

I tried scriptifier and it broke stuff so just be careful with it and check its 
output. 

Sean


> On 19 Aug 2022, at 01:39, Mike Kerner via use-livecode 
>  wrote:
> 
> Hey Skip, long time...
> I don't know if you were around when script-only-stack behaviors came into
> being, but you can now rip all of the code out of your stacks and happily
> use vc/git. The stacks themselves are still binary (although several of us
> have been messing with dumping that paradigm completely, it's less
> practical than I would have hoped, as of today).
> Navigator will export every script in a project into behavior stacks, and
> Monte wrote a stack called "Scriptifier", if memory serves. It's embedded
> in the LC bundle, and it does the same thing, namely extracting all the
> scripts out of a project and putting them into .livecodescript text files.
> Levure is great. I have used it with every project I've worked on for
> several years, BUT you don't have to use it to go this route.
> 
>> On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>> 
>> Hi SKIP
>> 
>> Welcome back to the list!
>> 
>> There is Levure which I knew of as a third party application framework
>> created by Trevor DeVore but I just did a search for it and I see it now on
>> the LiveCode website described as an App Collaboration Framework.
>> https://livecode.com/products/livecode-platform/levure/ <
>> https://livecode.com/products/livecode-platform/levure/>  So it must have
>> at some point migrated to the mother ship.
>> 
>> I haven’t used it but I have considered migrating my application to it.
>> It works with version control systems as long as you follow its
>> recommendations about how to organize your code into behaviours that are
>> stored in script only stacks which are just text files that a version
>> control system can read (These are somewhat new so depending on when you
>> last used LiveCode they may be new to you.)  This was an enhancement that
>> has enabled the use of version control for scripts in a project. It is the
>> binary stacks that versions control systems can’t track so in Levure those
>> are just used for user interface.
>> 
>> Hope this helps.
>> 
>> Martin
>> 
>> 
>>> On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode <
>> use-livecode@lists.runrev.com> wrote:
>>> 
>>> Greetings!
>>> 
>>> Been a while since I have been on this list.  Working on a new project
>> and
>>> wondering if the backing up of Livecode files to Github was ever
>>> implemented and created.  I know there was talk of it at one time.
>>> 
>>> I apologize if it has been in place for a while and I am just out of the
>>> loop.  Actually, I HOPE that is the case!
>>> 
>>> Regards,
>>> 
>>> SKIP
>>> ___
>>> 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-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: Livecode / Github

[Mike Kerner via use-livecode]

Hey Skip, long time...
I don't know if you were around when script-only-stack behaviors came into
being, but you can now rip all of the code out of your stacks and happily
use vc/git. The stacks themselves are still binary (although several of us
have been messing with dumping that paradigm completely, it's less
practical than I would have hoped, as of today).
Navigator will export every script in a project into behavior stacks, and
Monte wrote a stack called "Scriptifier", if memory serves. It's embedded
in the LC bundle, and it does the same thing, namely extracting all the
scripts out of a project and putting them into .livecodescript text files.
Levure is great. I have used it with every project I've worked on for
several years, BUT you don't have to use it to go this route.

On Thu, Aug 18, 2022 at 7:04 PM Martin Koob via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Hi SKIP
>
> Welcome back to the list!
>
> There is Levure which I knew of as a third party application framework
> created by Trevor DeVore but I just did a search for it and I see it now on
> the LiveCode website described as an App Collaboration Framework.
> https://livecode.com/products/livecode-platform/levure/ <
> https://livecode.com/products/livecode-platform/levure/>  So it must have
> at some point migrated to the mother ship.
>
> I haven’t used it but I have considered migrating my application to it.
> It works with version control systems as long as you follow its
> recommendations about how to organize your code into behaviours that are
> stored in script only stacks which are just text files that a version
> control system can read (These are somewhat new so depending on when you
> last used LiveCode they may be new to you.)  This was an enhancement that
> has enabled the use of version control for scripts in a project. It is the
> binary stacks that versions control systems can’t track so in Levure those
> are just used for user interface.
>
> Hope this helps.
>
> Martin
>
>
> > On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode <
> use-livecode@lists.runrev.com> wrote:
> >
> > Greetings!
> >
> > Been a while since I have been on this list.  Working on a new project
> and
> > wondering if the backing up of Livecode files to Github was ever
> > implemented and created.  I know there was talk of it at one time.
> >
> > I apologize if it has been in place for a while and I am just out of the
> > loop.  Actually, I HOPE that is the case!
> >
> > Regards,
> >
> > SKIP
> > ___
> > 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: Livecode / Github

[Martin Koob via use-livecode]

Hi SKIP

Welcome back to the list!

There is Levure which I knew of as a third party application framework created 
by Trevor DeVore but I just did a search for it and I see it now on the 
LiveCode website described as an App Collaboration Framework.  
https://livecode.com/products/livecode-platform/levure/ 
  So it must have at 
some point migrated to the mother ship.

I haven’t used it but I have considered migrating my application to it.  It 
works with version control systems as long as you follow its recommendations 
about how to organize your code into behaviours that are stored in script only 
stacks which are just text files that a version control system can read (These 
are somewhat new so depending on when you last used LiveCode they may be new to 
you.)  This was an enhancement that has enabled the use of version control for 
scripts in a project. It is the binary stacks that versions control systems 
can’t track so in Levure those are just used for user interface.

Hope this helps.

Martin


> On Aug 18, 2022, at 6:38 PM, Skip Kimpel via use-livecode 
>  wrote:
> 
> Greetings!
> 
> Been a while since I have been on this list.  Working on a new project and
> wondering if the backing up of Livecode files to Github was ever
> implemented and created.  I know there was talk of it at one time.
> 
> I apologize if it has been in place for a while and I am just out of the
> loop.  Actually, I HOPE that is the case!
> 
> Regards,
> 
> SKIP
> ___
> 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