HTML5 deployment: progress comes into sight
hh
hh at hyperhh.de
Thu Jun 1 15:56:30 EDT 2017
@Mark Waddingham:
I was partially wrong.
There is already more possible than I thought with HTML5 deployment when
using "do as javascript". One can work around missing javascriptHandlers
because there is "the result" available for evaluating in LC Script.
I tried again and found a bug in the HTML5 version of my "LCImageToolbox89"
from "Sample Stacks".
Bugs are hard to search/ find because we can't debug "do as javascript" in
LC Script (yes, of course we can do basic "testing" in a browser widget).
So first fly blind and then have eventually the real run-test with the
standalone. Very tedious.
At any rate the new features we will get for HTML5 will be a big step forward.
-------
The standalone is now running here. It is _very_ fast. I'll post it
tomorrow at http://hyperhh.org/html5/ and http://hh.on-rev.com/html5/ .
We can look at such standalones to have by LC a nice GUI to canvas2d-features.
*** And there is more available in canvas2d: Graphics, Video, Audio ...
*** So these are also available _via_ HTML5 standalones, we have to work
*** hard, do some (slightly advanced) javascript but it's possible.
*** I already know the "how to".
[These is on my 'vague' list for the next few demos:
basic graphics/text (also svg-features), more image processing, using
video/audio _via_ HTML5 deployment.]
> Mark W. wrote:
> > The problem is the "one-way"-only:
> > I can't see any way to go back, from the page to the standalone.
>
> That is a very good point.
>
> > = The browser widget has jsHandlers available.
> > = The standalone has to get the data from the page by guesses, in a
> > loop.
> >
> > If you can show or give us a solution for that, then we can have in
> > some scenarios even more by using the latest versions of the main
> > browsers than we get by using an embedded browser widget.
> >
> > In sum:
> > Can the HTML5 standalone become a property "javascriptHandlers" that
> > works as in the browser widget?
>
> Yes it can - I'll look into getting that (or something similar) done
> asap.
More information about the use-livecode
mailing list