Actually there is a compile step. The beauty is that it happens in the dev environment as the app is running, and only to script objects that have been edited. Try to execute an uncompiled script and it will run like the previously compiled script.
However, we are talking about a conversion not just of code, but of all the GUI elements as well. So yeah, there would have to be an edit-conversion-test cycle, unless the conversion was so incredibly clean that you could be sure that if it ran in LiveCode it would run as HTML5. But I don't see how that could be, especially if you look at the code I write! I think everyone with any experience in LC development can attest to the really odd structure and syntax they at times are forced to use to solve certain problems. I don't think you will see this kind of translator any time soon, if ever. Bob On Jun 20, 2011, at 9:47 PM, Terry Vogelaar wrote: > Back to the subject: should LiveCode move towards being a web app development > environment? I truly don't know. I like the idea. But it also means there is > a major change in the way LiveCode works. It is proud to be compile-free, > breaking the development cycle of editing, compiling, running and debugging. > If however the code is being translated to something else like HTML5, there > HAS TO BE a compile step. _______________________________________________ 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
