Us and them? [was Re: Livecode Dictionary]

[Brian Milby]

I've posted the Documentation Editor code to GitHub.  I'll try to add some
screen shots eventually.

https://github.com/bwmilby/DocEditorPlus
https://github.com/bwmilby/DocEditorPlus/raw/master/DocEditorPlus.livecode

Script index:
https://github.com/bwmilby/DocEditorPlus/blob/master/DocEditorPlus.md

(field "DocText" of card "DocEditor" is where most of the code from the
LiveCode Doc Helper stack landed).

I last worked on this in December 2017 and have not done extensive testing
on it with the latest LC9 release.  I did verify that it did still parse a
LCDOC file and was able to present it in the system browser on my Mac.  The
intended use is for a forked LiveCode repo which includes the dictionary.
There you can use git to create a branch off of develop-9.0 and update
dictionary entries.  Once the edits are done, commit to your new branch and
then on the GitHub site you can create the PR for inclusion into the
dictionary.  However, there is no requirement to have the full repo on your
system, you can just as easily obtain a single LCDOC file and work with it.

Thanks,
Brian

On Tue, Jan 22, 2019 at 12:07 PM David Bovill via use-livecode <
use-livecode at lists.runrev.com> wrote:

> Thanks Brian - if you have the tie to dig out that stack it would be great.
> I have come across the handlers / libs a few times - but as its not
> documented it takes a while to track down :)
>
> It would be great to figure out how to get proper flow back to the main
> project - so any thoughts on that would be great.
>
> On Tue, 22 Jan 2019 at 17:03, Brian Milby via use-livecode <
> use-livecode at lists.runrev.com> wrote:
>
> > GFM syntax is used, but it does go through additional processing before
> > being turned into what we see in the IDE.  All of that code resides in
> the
> > IDE so it can be leveraged to process the updates.  I actually modified a
> > stack that can allow the editing of a doc and then preview it in a
> > browser.  I’ll need to find where that is posted and link here for
> > reference this evening.
> >
> > For license, I was only referring to the flow back into the main project
> > which has the dual commercial/GPL license.
> >
> > Thanks,
> > Brian
> > On Jan 22, 2019, 10:52 AM -0600, David Bovill via use-livecode <
> > use-livecode at lists.runrev.com>, wrote:
> > > On Tue, 22 Jan 2019 at 14:40, Brian Milby via use-livecode <
> > > use-livecode at lists.runrev.com> wrote:
> > >
> > > >
> > > > That license will not allow inclusion into the LiceCode dictionary as
> > it
> > > > requires any derivative works to carry the same license. For
> > integration
> > > > into the LiveCode project a CLA will need to be signed by each author
> > and
> > > > their contributions also submitted with copyright assigned to the
> > company.
> > > >
> > >
> > > The documentation license is GPLv3 (with a modification for ATL and
> > > OpenSSL). It's not an ideal license for documentation - should probably
> > > changed to make things clearer but "on October 8, 2015, Creative
> Commons
> > > concluded
> > > <
> >
> https://creativecommons.org/share-your-work/licensing-considerations/compatible-licenses/
> > >
> > > that the CC BY-SA <https://en.wikipedia.org/wiki/CC_BY-SA> 4.0 is
> > inbound
> > > compatible with the GPLv3". I also spoke with Kevin from the
> Mothership a
> > > couple of times about this issue, and AFAIK there is not intention to
> > > restrict the use / remix of the documentation in this way - ie using
> with
> > > other so called free culture content such as Wikipedia. Here are a few
> > > links:
> > >
> > > - https://bit.ly/2FQfkvH
> > >
> > > Certainly more complicated is the flow back to the mothership for
> > including
> > > the content in the closed source (commercial) distributions - for that
> > we'd
> > > need the CLA, and some sort of care taken to NOT include Wikipedia
> > content
> > > but only completely rewritten content. I'd certainly like to do that -
> so
> > > getting authors to sign the CLA would be useful to figure out for the
> > > community side of things.
> > >
> > > The dictionary uses markdown as the source format. To be easy to
> > > > integrate, it would be a good idea to use that as the storage/native
> > format
> > > > of contributions.
> > >
> > >
> > > Yes - within the json we store Github flavoured markdown. It seems to
> me
> > > that the documentation is not in markdown though?
> > >
> > > -
> > >
> >
> https://github.com/livecode/livecode/blob/develop/docs/dictionary/function/URLEncode.lcdoc
> > > _______________________________________________
> > > 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