Features and shortcomings of html5

Terry Judd terry.judd at unimelb.edu.au
Tue Feb 20 22:05:10 EST 2018

I've converted a couple of interactive simulations to HTML5 and they worked and performed surprisingly well (once I'd removed and coded around a few wait statements). Multiple cards are fine but I haven't tried switching between stacks. Text display isn't that great out of the box but that shouldn't be too much of an issue unless you have pretty strict formatting requirements (you can load fonts but I'm not sure whether it's worth the trouble). The biggest drawback for me has been around networking but that seems to have been substantially improved in recent releases (I haven't had a chance to explore these yet).

It's certainly worth a quick try of exporting an existing stack with LC community and seeing what works and what doesn't to get a sense of whether a full on conversion is warranted.


On 21/02/2018 10:25 am, "use-livecode on behalf of J. Landman Gay via use-livecode" <use-livecode-bounces at lists.runrev.com on behalf of use-livecode at lists.runrev.com> wrote:

    I've been asked if I can convert a stack to HTML5, which I haven't 
    worked with yet. I'd like to know, in general, what can be done and what 
    can't. What are the limitations?
    The examples I've seen are mostly basic, usually just a one-card stack 
    with image or graphic manipulations. I'm also aware of the fairly long 
    initial load time, though I guess that's been cut back a bit. The stack 
    I will be working with will require many cards, navigation, and possibly 
    changing stacks (probably in the same window.)
    What else would I need to consider?
    Jacqueline Landman Gay         |     jacque at hyperactivesw.com
    HyperActive Software           |     http://www.hyperactivesw.com
    use-livecode mailing list
    use-livecode at lists.runrev.com
    Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list