Re: What is old is new again...
Posted: Fri Jan 26, 2018 11:26 am
I really ought to stop living in a fantasy world.
Questions and answers about the LiveCode platform.
https://forums.livecode.com/
That is the pickler. While many Oss licenses are pretty liberal, they (usually) take great care not to trample over proprietary rights, as it should be.FourthWorld wrote: Fri Jan 26, 2018 11:04 am folks using the GPL-governed Community Edition would have difficulty knowing for sure what they can and cannot do with it...
If you're interested in redistributing the modified work for others, perhaps I can get guidance from Kevin on an appropriate license. At that point it isn't LiveCode, but it is derived from their work, so a few different considerations come into play:bogs wrote: Sat Jan 27, 2018 9:35 pm As to what I would like to do with it, starting with the documentation I'd like to cut it out like I did with the Mc help stacks. What the company indicated through email was that they didn't see a problem as long as references were changed or eliminated to prevent confusion in branding, as you mention above.
Well, as of right now, I have a collection of nothing other than the IDE as is. However, what you said is what I meant when I saidFourthWorld wrote: Sat Jan 27, 2018 10:06 pm If you have a collection of stacks you want to redistribute it may help if I could point him to that collection so he can consider them in isolation of the rest of the install...
I just like knowing the ground rules as much as possible before I go nuts, and I know that unlike Mc, this isn't my sole playgroundbogs wrote: Sat Jan 27, 2018 9:35 pm I'll try to make sure I float anything intended past someone before releasing it just to make sure.
...looking for the fine printFourthWorld wrote: Sat Jan 27, 2018 11:57 pm FWIW, if there's anything with my name on it that came included with either LC or MC, it's covered by each IDE's respective license.


Much of the early documentation was written by a woman under hire and myself. Since this was a legal "work for hire" the material is owned by LC who holds all the permissions.Not only do those stacks have things from RR/Lc, but also from you, Jacque, and many others.
What you say is absolutely correct, but here is the (in my mind) much larger problem. The older documentation still works (probably better than 98% in new versions) because as you pointed out, Lc is pretty good at maintaining backwards compatibility.jacque wrote: Sun Jan 28, 2018 6:45 pm The problem will more likely be that the material is sometimes obsolete. One example that comes to mind is the handler for stripping out empty lines from a script. It was written before the filter command was altered to include "filter without empty", which accomplishes the same thing in a single line of code.
I don't see this as as being the end of someone learning, just as a good solid foundation for the beginning and a decent reference to look back at. Once someone has gotten familiar enough with Lc, they should be able to have some idea of what they are looking to do and can go through the more difficult documentation if they want.New users who rely on old documentation run the risk of not really learning the language as it currently exists. There have been a lot of additions as well that old documentation won't cover. We've come a long way since version 2.
