Livecode / Github

[Pi Digital]

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 <use-livecode at lists.runrev.com> 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
> brian at milby7.com
> 
>> On Sep 1, 2022, at 2:27 PM, Sean Cole via use-livecode <use-livecode at lists.runrev.com> 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 <sean at pidigital.co.uk> 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 at 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
>>>> ahsoftware at gmail.com
>>>> 
>>>> _______________________________________________
>>>> use-livecode mailing list
>>>> use-livecode at lists.runrev.com
>>>> Please visit this url to subscribe, unsubscribe and manage your
>>>> subscription preferences:
>>>> http://lists.runrev.com/mailman/listinfo/use-livecode
>>>> 
>>> 
>> _______________________________________________
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>> http://lists.runrev.com/mailman/listinfo/use-livecode
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode