Right, its not exactly going to be practical to take it apart. As we develop this we¹ll be looking at obfuscation to make it as hard as possible. Nor would you have any right to use the code or redistribute it. So there is a practical difference and a difference of intent. If its commercial, you¹re hacking which is hard and the original author can also look to appropriate law for protection.
GPL is quite different. The HTML5 output on the page is the compiled form¹ in GPL terms. The HTML5 compiled form is not the original source. It would not be considered to fulfill the terms of the GPL. The GPL binds you to releasing the original, modifiable source code. Everyone who receives the app - I.e. everyone who visits your web page - has to also be provided with the opportunity to receive the original source so that they can modify it and redistribute as they choose. Imagine you are contracted to produce a web app for a company to log sales from your network of sales people and affiliates on the road. If you give that to the client under GPL, they would need to include a link within that app to download the source code and anyone could take it and use the entire app freely. That is hardly going to be acceptable. There are lots of other such examples. Kind regards, Kevin Kevin Miller ~ ke...@livecode.com ~ http://www.livecode.com/ LiveCode: Everyone can code On 19/07/2014 15:16, "Richard Gaskin" <ambassa...@fourthworld.com> wrote: >Peter W A Wood wrote: > > > It is probably as easy to disassemble and modify a LiveCode generated > > binary as it will be to modify a LiveCode generated JavaScript file. > > Do you worry about people disassembling your binaries to modify the > > code it? It would take the same level of skill to do change the > > generated JavaScript code. > > > > Take a look at this example - >http://vps2.etotheipiplusone.com:30176/redmine/emscripten-qt-examples/kate >/kate.js.jo.js > > > > Sure some dishonest person could spend a vast amount of time to > > modify one of your applications but would they find it worthwhile? > > I don't think so. > >That example, onerous as it is, may be too generous, using readable >labels and such. > >The JS translation LC's looking at will use extensions to LLVM to >produce, so the output would likely look more like the source you see at >Google Maps - very, very difficult to convert into a human-editable >form, arguably more akin to the output you get running any object code >through modern disassemblers - useful only to experts who could probably >rewrite your app from scratch faster than they could decode compact >symbols. > >-- > Richard Gaskin > Fourth World Systems > Software Design and Development for the Desktop, Mobile, and the Web > ____________________________________________________________________ > ambassa...@fourthworld.com http://www.FourthWorld.com > >_______________________________________________ >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 _______________________________________________ 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
