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 perhaps the only issue) is that the HEAD versions
> of the version branches (release-* branches for specific releases,
> develop-* for the frontier of maintenance releases and develop for the next
> release) in the three main community repositories are all mutually
> dependent to a greater or lesser degree. Whilst you can try and use the
> develop HEAD version of the IDE with an engine built from develop-9.0 or
> earlier, the reality is that it might not work.


​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
https://github.com/livecode/livecode-ide/tree/develop/Toolset/libraries are
months to years from their last update. Ditto for
https://github.com/livecode/livecode-ide/tree/develop/Toolset/palettes/script%20editor/behaviors.
That
makes it seem as though it would absolutely be possible to work on the IDE
in the current 9.x release, with the caveat that merge conflicts would be
*slightly* more likely. ​

Or am I missing something?

Thanks again,

gc
_______________________________________________
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

Reply via email to