No problem, but thanks for replying. That is really interesting. I know that setting up such a structure in traditional HTML/JS would be a big pain, because I have looked into something similar before for other reasons.
It must have been quite a bit of work to duplicate that structure in the HTML5 deployment of LC. Sent from my iPhone > On Jul 25, 2017, at 4:21 PM, Kevin Miller via use-livecode > <use-livecode@lists.runrev.com> wrote: > > Yes you can. I'm at a conference just now but hopefully someone knowledgable > on our team can jump in with more info. > > Sent from my iPhone > >> On 25 Jul 2017, at 13:07, Jonathan Lynch via use-livecode >> <use-livecode@lists.runrev.com> wrote: >> >> Kevin, >> >> Can you have a structure similar to having multiple stacks controlled by an >> LC engine? >> >> I am really curious how you guys set that up? Using localstorage and cookies >> are the only methods I know of for doing that in regular html5 with multiple >> tabs/windows. >> >> >> >> Sent from my iPhone >> >>> On Jul 25, 2017, at 3:54 PM, Kevin Miller via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>> Go in window of stack works >>> >>> You can download stacks just fine >>> >>> Sent from my iPhone >>> >>>> On 25 Jul 2017, at 12:46, Jonathan Lynch via use-livecode >>>> <use-livecode@lists.runrev.com> wrote: >>>> >>>> In HTML the browser is the engine that runs both HTML and JavaScript. It >>>> is possible to have multiple tabs and there are some functions for >>>> communicating between tabs and windows, but it isn't pretty. You have to >>>> use localstorage and storage events. >>>> >>>> This could be made to work similar to an LC engine running multiple >>>> stacks, but it is like turning real fish into artificial crab. It is a lot >>>> of work to make something that will probably leave you with a bad taste in >>>> your mouth. >>>> >>>> Sent from my iPhone >>>> >>>>> On Jul 25, 2017, at 3:30 PM, J. Landman Gay via use-livecode >>>>> <use-livecode@lists.runrev.com> wrote: >>>>> >>>>> Thanks. I don't think the sandbox is an issue, the app doesn't read or >>>>> write to the user's drive at all. The various animations, and >>>>> splash-stack approach might be a concern, as well as the number of stacks >>>>> that are in RAM at any one time. Common images and icons are also stored >>>>> in the standalone, which are displayed in the downloaded stacks as they >>>>> are opened. >>>>> >>>>> The only HTML5 examples I've seen are all self-contained single stack >>>>> standalones. >>>>> >>>>>> On 7/25/17 2:00 PM, Jonathan Lynch via use-livecode wrote: >>>>>> Well, the sandbox is a huge issue. JavaScript is not allowed to access >>>>>> many things that LC can access in the user's system. >>>>>> The sandbox protects against malicious pages. >>>>>> It is very hard to simulate the mouseStillDown handler in HTML/JS. >>>>>> My app is a hybrid of LC and html5. The pace of development for LC is >>>>>> easily 10 times faster for me. >>>>>> LC text processing and array management is much much more flexible. >>>>>> "Get the keys of myArray" beats enumerating through a JS array any day. >>>>>> JS does not have true associative arrays, although you can work around >>>>>> that with datamaps. >>>>>> JS does not have programmatic access to the clipboard. >>>>>> Most of the limitations are related to security issues. If the sandbox >>>>>> is not an issue, then html5 will probably work, but they should expect >>>>>> to spend a fortune and live with a long development cycle with painfully >>>>>> slow bug fixes. >>>>>> Sent from my iPhone >>>>>>> On Jul 25, 2017, at 2:42 PM, J. Landman Gay via use-livecode >>>>>>> <use-livecode@lists.runrev.com> wrote: >>>>>>> >>>>>>> I have a client that wants to move our project to HTML5. I have some >>>>>>> doubts about the capabilities, could someone tell me what is currently >>>>>>> possible and what is not? >>>>>>> >>>>>>> This is a very large set of stacks, run by a standalone that loads >>>>>>> content on demand from a server. It is image-heavy and interacts with a >>>>>>> networked database. There is lots of navigation between stacks and many >>>>>>> hundreds of cards. At any given time, there can be up to a dozen stacks >>>>>>> held in RAM. There is also heavy use of visual effects and animation. >>>>>>> >>>>>>> Thoughts? >>>>>>> >>>>>>> -- >>>>>>> Jacqueline Landman Gay | jac...@hyperactivesw.com >>>>>>> HyperActive Software | http://www.hyperactivesw.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 >>>>> >>>>> >>>>> -- >>>>> Jacqueline Landman Gay | jac...@hyperactivesw.com >>>>> HyperActive Software | http://www.hyperactivesw.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 >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > 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
