HTML5 and main Javacript Engine bridge

[Idle Ideas Inc.]

We are beginning the process of connecting our HTML5 feature to Mote's main Javascript engine. This might take a while so we'd like to ask for input as to what  (Mote) Javascript methods or functions you all think should be made available first.

Thanks!

[James Murrell]

The primary focus on this (as I see it) is for aesthetic and UI improvements. Being able to implement CSS3 rendering and HTML5 controls would be a huge deal. The clear focus, of course, is on the frames/dialogs.

[Idle Ideas Inc.]

Thanks for the input, James. What we're looking for in this thread is what functions of the Mote API would be actually usable or helpful, from within our HTML5 windows? Not everything will make it in, as we try to limit the scope of this effort.

[James Murrell]

The most important interactions would definitely be macro links. No question. And of course being able to get properties from all possible sources (Tokens, libraries, tables, SQL).

[Calvin McGowan]

I agree wholeheartedly. Being able to call properties would be huge. I'd also like the ability to make rolls, etc, directly from an HTML5 macro. But if I had to pick only one thing it would be macrolinks. It wouldn't be quite as sleek as being able to run it all directly from the HTML5 macro itself, but it would provide a relatively straightforward workaround in the interim.

[Idle Ideas Inc.]

We're still mulling incorporating macro links into this one. We'd rather not, and choose to use the standard tags, with mote-specific attributes e.g. lib="library reference", to refer to sources. Props would likely be the same, perhaps used in the value attribute, where the engine would then lookup the value and insert it where it needs to be.

[James Murrell]

That would be a fine solution. Frankly, the "macroLink" as inherited from MT is a fairly clunky system. All that really matters is that you can run code from the HTML window controls.