Web vs Native (was Re: HTML5 limitations?)

hh hh at hyperhh.de
Fri Jul 28 16:22:08 EDT 2017


> Mark wrote:
> However, there is one VERY important point I do need to make. It is easy 
> to get hang up on saying 'oh the HTML5 engine doesn't do this, and oh it 
> doesn't do that' - and this might well be true. *However* the only important
> metric in this regard is - does it allow a suitable percentage  of LiveCode
> stacks which exist *right now* to run in the browser unchanged.
> 
> The problem here is that this is quite subjective - it largely depends on HOW
> you code and use LiveCode (remember my analogy of LiveCode and the elephant and
> the blind men). One thing you have pointed out is that  'the mouse' function does
> not work. It does not, this is true - however, for every person who ever uses
> 'the mouse' function I can be absolutely sure there are probably AT LEAST 2 who
> do not. This is true of all LiveCode features to a greater or lesser degree.

Probably the "one" (=checking if the mouse is "down") pledged and bought a HTML5
license, the "at least other 2" (=never using it) didn't pledge nor buy a license.

I reported to quality center in Dec 2015/Jan 2016, that the state of the mouse
and modifier keys aren't recognized and that all menu buttons crash the standalone.
To have at least two of these three working is for me a basic requirement for
interaction. If I repeat this 'feature request' 20 months later this is certainly
no "getting hang up".

And I really didn't take, for nearly three years, this 'negative' easy path as
you decribe, to the contrary:

Since the start of this *395 thousand dollars* project in July 2014 I made at
about 60 "successful tests" to show 'oh the HTML5 engine does this' and
'oh it does that'. This wasn't easy at all, needed a _lot_ of workarounds ...

So I'll better stop now and wait for the suitable percentage of 'unchanged'
LiveCode demos (although "wait" is not allowed in HTML5 deployment).

What the team made in HTML deployment until now is *very* good, especially the
"do as javascript" part is excellent. Just put more of the funds (and by that
'bandwidth') into it, so that also basic things (e.g. typing UTF-8 into a field)
do work. 

p.s. HTML5 standalones can talk to each other, several of them, in one browser
window. I just successfully tested that --- and trashed the demo.





More information about the use-livecode mailing list