I agree.
i have yet to use the HTML output but I would have a hard time meeting
my needs without the wait feature as I use it to keep the UI from ever
being blocked which is part of a major feature of the software I am
building.
While I don't anticipate having this need to output to HTM
Indeed - we can make all the things on the list I made have a callback /
without waiting form too.
In terms of wait itself - it is the HyperTalk way of doing 'async' - allowing
you to write such code without the 'headache' of nested callbacks / closures
and such - this is why it is important to
On 07/29/2017 09:23 PM, Mark Waddingham via use-livecode wrote:
P.S. One other possibility I've toyed with is doing LCS->BYTECODE, then
BYTECODE->ASYNCIFIED_JAVASCRIPT. The latter would be particularly easy
if targetting browsers which have already implemented the new async
JavaScript features
Hi Herman,
This is all very useful information I must confess.
I guess I'm wary of just extrapolating potential performance from piecing
together results from very different underlying architecture (e.g emterpreter
vs no emterpreter) over bastions different html5 engine iterations.
Of course y
> Mark wrote:
> I'm not sure relating this to RaspPi is useful. The reason is that if I
> am wanting to move my Desktop app (Mac, Windows, Linux) app to HTML5
> then I'd want the performance in the browser to be within a reasonable
> distance of that when on the Desktop...
> ...The only way to k
On 2017-07-30 11:13, hh via use-livecode wrote:
Wow. You say (using stars) it would make sense to implement wait
in HTML5 for some features that do _not_ (yet) work in HTML5.
Will be a great enhancement side-effect. I look forward to that.
I don't think that was the implication. The implication
Wow. You say (using stars) it would make sense to implement wait
in HTML5 for some features that do _not_ (yet) work in HTML5.
Will be a great enhancement side-effect. I look forward to that.
Peter-B already implemented wait in 2015, see bug #16076.
This caused an _additional_ slow down by a facto
So LiveCode has long has this feature called 'wait' - it is one of those
seemingly innocuous things which, from the surface seems simple (it
allows you to wait for something - it's great when syntax is aptly
named!) however it is perhaps one of the deepest language features we
have.
I think t
