Re: Contributing to the IDE

On Fri, Apr 20, 2018 at 2:46 AM, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > > You might make a change to a file which looks identical in 9 and 9.1 - but > how do you know it will work in 9.1 without running it in 9.1? ​As someone who was, until about four months

Re: Contributing to the IDE

>Monte Goulding via >use-livecode > Fri, 20 Apr 2018 01:49:50 >-0700 > wrote >I’m fairly sure

Re: Contributing to the IDE

On 2018-04-20 11:15, Geoff Canyon via use-livecode wrote: ​I get that -- my point is that *many* of the IDE script files are unchanged from 9.0 release to the current(?) develop branch. So working on files in 9.0, making changes, and then submitting a pull request, unless git somehow makes

Re: Contributing to the IDE

On Fri, Apr 20, 2018 at 1:49 AM, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > >> > Yes - my point about the engine and IDE versions being mutually dependent > :) ​I get that -- my point is that *many* of the IDE script files are unchanged from 9.0 release to the

Re: Contributing to the IDE

> ​Sorry, one other point: yes, you are correct, working from a pre-built > distribution is exactly the question I was asking, and if the only issue is > syncing the IDE files with the development versions, that seems like a > small issue: many of the files at >

Re: Contributing to the IDE

On 2018-04-20 10:39, Geoff Canyon via use-livecode wrote: ​Sorry, one other point: yes, you are correct, working from a pre-built distribution is exactly the question I was asking, and if the only issue is syncing the IDE files with the development versions, that seems like a small issue: many

Re: Contributing to the IDE

> On 20 Apr 2018, at 6:29 pm, Geoff Canyon via use-livecode > wrote: > > Two questions: > > 1. Are older versions closed to changes? If I find a bug in LC 8.1.8 (or > some update to it) is it pointless to fix the bug and submit a pull request? If it is still

Re: Contributing to the IDE

On 2018-04-20 10:29, Geoff Canyon via use-livecode wrote: Thanks for the clear rationale. I'll take a shot at building the whole thing tomorrow. I should have mentioned in my post (although I think Monte made it clear) that docs can be done entirely on GitHub. Doc entries are a special case

Re: Contributing to the IDE

On Fri, Apr 20, 2018 at 1:08 AM, Mark Waddingham via use-livecode < use-livecode@lists.runrev.com> wrote: > What you are asking for is slightly different: "How do I make it so that I > can modify the IDE in a pre-built distribution and submit patches/PR from > that". > > The main issue here (and

Re: Contributing to the IDE

e > > no interest in reading about git or github. The very best thing you can > do > > before anything else is understand git. There is bucket loads of freely > > available information online. This is a great free book > > https://git-scm.com/book/en/v2 <https://git-scm.com/bo

Re: Contributing to the IDE

Thanks for the clear rationale. I'll take a shot at building the whole thing tomorrow. Two questions: 1. Are older versions closed to changes? If I find a bug in LC 8.1.8 (or some update to it) is it pointless to fix the bug and submit a pull request? 2. Is it fair to submit IDE pull requests

Re: Contributing to the IDE

Thanks, on the basis of this document I *think* I was able to submit a pull request for an update to the documentation for the itemOffset function. We'll see if that's what I really did, and if successfully so. I'd highly recommend removing/updating the reference to a specific version in this

Re: Contributing to the IDE

On 2018-04-17 03:44, Geoff Canyon via use-livecode wrote: Are there instructions available somewhere on how to set up the IDE in GitHub so I can make changes and submit pull requests? Not in the way you are trying to - no. Pretty much all our documentation is centered around the initial step

Re: Contributing to the IDE

I also just remembered that much of the information that you may find helpful is in the contributing to docs page which you may not have read if your interest is in source contributions. https://github.com/livecode/livecode/blob/develop/docs/contributing_to_docs.md

Re: Contributing to the IDE

t loads of freely > available information online. This is a great free book > https://git-scm.com/book/en/v2 <https://git-scm.com/book/en/v2> > > > > To be clear: reasonable documentation for contributing to the IDE would > include a section something like: > > > &g

Re: Contributing to the IDE

est thing you can do before anything else is understand git. There is bucket loads of freely available information online. This is a great free book https://git-scm.com/book/en/v2 <https://git-scm.com/book/en/v2> > > To be clear: reasonable documentation for contributing to the IDE wou

Re: Contributing to the IDE

I have to admit, this is very frustrating. I *have* read both documents referenced, and neither comes close to answering my question. I remember reading those documents, or their ancestors, when LC first went open source, and I would likely have started contributing to the IDE then except

Re: Contributing to the IDE

Just a guessing based on your response that you possibly didn’t read the docs that you asked for and Brian responded with ;-) > On 20 Apr 2018, at 5:43 am, Geoff Canyon via use-livecode > wrote: > > I have GitKraken; is it as simple as initializing a new

Re: Contributing to the IDE

I have GitKraken; is it as simple as initializing a new repository in /Applications/LiveCode Indy 8.1.8.app/Contents/Tools/Toolset/libraries? On Mon, Apr 16, 2018 at 7:48 PM, Brian Milby wrote: > https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md > >

Re: Contributing to the IDE

https://github.com/livecode/livecode/blob/develop/CONTRIBUTING.md https://github.com/livecode/livecode/blob/develop/README.md Those two docs have most of what you will need. If you have purchased LiveCode Global 2018 then you can watch the talk I gave last month on setting up your system to

Contributing to the IDE

Are there instructions available somewhere on how to set up the IDE in GitHub so I can make changes and submit pull requests? gc ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your