Re: lcVCS - Getting started
On 13/09/2013, at 3:53 PM, Mark Wieder mwie...@ahsoftware.net wrote: Monte- Thursday, September 12, 2013, 5:34:28 PM, you wrote: I hadn't thought about supporting multiple script editors yet. How does one tell if GLX is the user's current choice of script editor? I suppose you could check to see if GLX2 is in the frontscripts. function GLX2IsActive local tIsActive put false into tIsActive -- see if GLX2 is available if GLX2 is in the frontscripts then -- see if GLX2 is active if the cUseGLX2 of stack revGLX2 Code is true then -- GLX2 is active put true into tIsActive end if end if return tIsActive end GLX2IsActive OK, thanks. Once I've re-designed the exported files to cope with Windows I'll look at adding GLX2 support. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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
lcVCS - Getting started
Hello, I was going to contact Monte off list but I thought the info might be useful to others. I wanted to give your lcVCS a try on a couple of stacks to see how it does. When I go to the github page I download the repo but I think the repo itself is just the lcVCS code being stored by lcVCS. Is there anywhere I can get my hands on the plugin and maybe a little info on how to get started beyond the readme on the github page? -- Regards, Andrew Kluthe and...@ctech.me ___ 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: lcVCS - Getting started
Ahh, thanks for that info monte. I am on windows here too so that would definitely keep me from getting running with it and that is a very tricky problem indeed to solve without a lot of re-engineering of the whole system. Let me know if I can help test anything on windows or there is anything specific I could contribute to. Kind regards, Andrew On Thu, Sep 12, 2013 at 3:59 PM, Monte Goulding mo...@sweattechnologies.com wrote: On 13/09/2013, at 12:25 AM, Andrew Kluthe and...@ctech.me wrote: I was going to contact Monte off list but I thought the info might be useful to others. I wanted to give your lcVCS a try on a couple of stacks to see how it does. When I go to the github page I download the repo but I think the repo itself is just the lcVCS code being stored by lcVCS. Is there anywhere I can get my hands on the plugin and maybe a little info on how to get started beyond the readme on the github page? Previously I had the lcVCS stackFiles in the repo as a way to deliver them but they have been removed now that I have a project file based system that builds them directly into your plugins folder. It's a bit of a chicken and an egg thing though because you need the stackFiles first but from then on you can update via the repo. I emailed them to Rolf the other day and I should put them up on mergExt but I've just discovered a fairly big issue for using it on Windows that I need to do some significant changes to resolve. After the changes the exports wouldn't be compatible so I'm hesitant to get too many people using it right now. The problem is windows can't handle paths longer than 260 chars and deeply nested groups can create really long paths in lcVCS because there's heaps of nested folders named with UUIDs. It's annoying because it's starting to get pretty slick and possibly turning into an open source project delivery system using a GitHub search feature. So the question is whether I should ignore the issue on Windows for now and share what I have done openly with some docs or fix it first. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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 -- Regards, Andrew Kluthe and...@ctech.me ___ 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: lcVCS - Getting started
On 13/09/2013, at 7:58 AM, Andrew Kluthe and...@ctech.me wrote: Ahh, thanks for that info monte. I am on windows here too so that would definitely keep me from getting running with it and that is a very tricky problem indeed to solve without a lot of re-engineering of the whole system. Not the whole system, just the object storage. I have a plan which I think will work I just need to find some time to implement it. Let me know if I can help test anything on windows or there is anything specific I could contribute to. Well one thing I'd like to work out is if it's possible to open up a script editor with the scroll so that a specific char offset from the beginning of the script is visible. I think it's possible but it probably involves poking around in the script editor to work it out. This is for the conflict resolution UI. If you want to work that out it would be one less thing on my todo list ;-) Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: lcVCS - Getting started
On 13/09/2013, at 12:25 AM, Andrew Kluthe and...@ctech.me wrote: I was going to contact Monte off list but I thought the info might be useful to others. I wanted to give your lcVCS a try on a couple of stacks to see how it does. When I go to the github page I download the repo but I think the repo itself is just the lcVCS code being stored by lcVCS. Is there anywhere I can get my hands on the plugin and maybe a little info on how to get started beyond the readme on the github page? Previously I had the lcVCS stackFiles in the repo as a way to deliver them but they have been removed now that I have a project file based system that builds them directly into your plugins folder. It's a bit of a chicken and an egg thing though because you need the stackFiles first but from then on you can update via the repo. I emailed them to Rolf the other day and I should put them up on mergExt but I've just discovered a fairly big issue for using it on Windows that I need to do some significant changes to resolve. After the changes the exports wouldn't be compatible so I'm hesitant to get too many people using it right now. The problem is windows can't handle paths longer than 260 chars and deeply nested groups can create really long paths in lcVCS because there's heaps of nested folders named with UUIDs. It's annoying because it's starting to get pretty slick and possibly turning into an open source project delivery system using a GitHub search feature. So the question is whether I should ignore the issue on Windows for now and share what I have done openly with some docs or fix it first. Cheers -- Monte Goulding M E R Goulding - software development services mergExt - There's an external for that! ___ 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: lcVCS - Getting started
Monte- Thursday, September 12, 2013, 3:14:43 PM, you wrote: Well one thing I'd like to work out is if it's possible to open up a script editor with the scroll so that a specific char offset from the beginning of the script is visible. I think it's possible but it probably involves poking around in the script editor to work it out. This is for the conflict resolution UI. If you want to work that out it would be one less thing on my todo list ;-) I had to figure this out for glx2 as well: dispatch goLine to group Editor of stack revNewScriptEditor \ with pLineNumber, pType, pStartPosition, pEndPosition -- where pType is one of selection or position ...for glx2 just replace revNewScriptEditor with revGLX2 Code -- -Mark Wieder mwie...@ahsoftware.net ___ 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: lcVCS - Getting started
This works even better than what I had just mailed monte. Thanks! On Thu, Sep 12, 2013 at 6:33 PM, Mark Wieder mwie...@ahsoftware.net wrote: Monte- Thursday, September 12, 2013, 3:14:43 PM, you wrote: Well one thing I'd like to work out is if it's possible to open up a script editor with the scroll so that a specific char offset from the beginning of the script is visible. I think it's possible but it probably involves poking around in the script editor to work it out. This is for the conflict resolution UI. If you want to work that out it would be one less thing on my todo list ;-) I had to figure this out for glx2 as well: dispatch goLine to group Editor of stack revNewScriptEditor \ with pLineNumber, pType, pStartPosition, pEndPosition -- where pType is one of selection or position ...for glx2 just replace revNewScriptEditor with revGLX2 Code -- -Mark Wieder mwie...@ahsoftware.net ___ 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 -- Regards, Andrew Kluthe and...@ctech.me ___ 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: lcVCS - Getting started
On 13/09/2013, at 9:33 AM, Mark Wieder wrote: Monte- Thursday, September 12, 2013, 3:14:43 PM, you wrote: Well one thing I'd like to work out is if it's possible to open up a script editor with the scroll so that a specific char offset from the beginning of the script is visible. I think it's possible but it probably involves poking around in the script editor to work it out. This is for the conflict resolution UI. If you want to work that out it would be one less thing on my todo list ;-) I had to figure this out for glx2 as well: dispatch goLine to group Editor of stack revNewScriptEditor \ with pLineNumber, pType, pStartPosition, pEndPosition -- where pType is one of selection or position ...for glx2 just replace revNewScriptEditor with revGLX2 Code So I'd just need to have a line offset rather than a char offset. I think I can change my conflict parser to do that... Does this support script editors in both tabbed and multi-window mode? What would be nice is an extension of the edit script command with a chunk so the editScript handler got two parameters theObject,theChunk and then any IDE could be upgraded to handle this nicely... edit [chunk of] the script of objectRef Cheers -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! ___ 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: lcVCS - Getting started
On 13/09/2013, at 10:01 AM, Mark Wieder wrote: So I'd just need to have a line offset rather than a char offset. I think I can change my conflict parser to do that... I think both are necessary: a line offset and a char offset into the line. Ah, well the conflict markers will always be the start of the line so I guess 0 there. Does this support script editors in both tabbed and multi-window mode? No idea, sorry. OK... needs some experimentation What would be nice is an extension of the edit script command with a chunk so the editScript handler got two parameters theObject,theChunk and then any IDE could be upgraded to handle this nicely... That would indeed be nice, but I suppose we have to wait until the IDE team is ready to accept pull requests. The goLine command was as close as I could come to an exposed api call. Well I guess if we upgraded the edit command then submit an enhancement request the IDE team might help out... I hadn't thought about supporting multiple script editors yet. How does one tell if GLX is the user's current choice of script editor? Cheers -- M E R Goulding Software development services Bespoke application development for vertical markets mergExt - There's an external for that! ___ 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: lcVCS - Getting started
Monte- Thursday, September 12, 2013, 4:58:01 PM, you wrote: So I'd just need to have a line offset rather than a char offset. I think I can change my conflict parser to do that... I think both are necessary: a line offset and a char offset into the line. Does this support script editors in both tabbed and multi-window mode? No idea, sorry. What would be nice is an extension of the edit script command with a chunk so the editScript handler got two parameters theObject,theChunk and then any IDE could be upgraded to handle this nicely... That would indeed be nice, but I suppose we have to wait until the IDE team is ready to accept pull requests. The goLine command was as close as I could come to an exposed api call. -- -Mark Wieder mwie...@ahsoftware.net ___ 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: lcVCS - Getting started
Monte- Thursday, September 12, 2013, 5:34:28 PM, you wrote: I hadn't thought about supporting multiple script editors yet. How does one tell if GLX is the user's current choice of script editor? I suppose you could check to see if GLX2 is in the frontscripts. function GLX2IsActive local tIsActive put false into tIsActive -- see if GLX2 is available if GLX2 is in the frontscripts then -- see if GLX2 is active if the cUseGLX2 of stack revGLX2 Code is true then -- GLX2 is active put true into tIsActive end if end if return tIsActive end GLX2IsActive -- -Mark Wieder mwie...@ahsoftware.net ___ 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
