Thanks Terry, that's helpful. I get the feeling that we can do almost
anything internal to LC's engine, but things that require a call out to
the OS are harder.
I did a quick conversion of a simple stack way back when HTML5 was first
released and got pretty good results, but the load time was murderous
and I dropped it as unusable until it got faster. I haven't tried it
since that was improved, maybe it's okay now.
The deal is, my client and I have fast internet connections and we're
willing to wait a bit for the stack to load, but if this project goes
through it could be used by anyone including, as she told me, "by people
in Nairobi" who may be on slow connections or even cell data.
We're also considering writing mobile apps instead, but her customer is
hoping to integrate directly with their web site.
At any rate, thanks for the feedback.
On 2/20/18 9:05 PM, Terry Judd via use-livecode wrote:
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.
Terry...
On 21/02/2018 10:25 am, "use-livecode on behalf of J. Landman Gay via use-livecode"
<use-livecode-boun...@lists.runrev.com on behalf of use-livecode@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 | 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
