Forums | NoesisGUI

I have just discovered your technology and I was wondering whether you had plans for an integration of it with Web Assembly (WASM)?
Philippe

We experimented a bit with HTML5 + WebGL during the 1.3 development but finally decided to leave this platform out. This is something we want to retake for future versions, including WASM.

Thanks for your quick answer.
I plan to closely follow the evolution of your neat technology.

Thanks Philippe, just let us know if you want to evaluate NoesisGUI.

Thinking more about it, an XAML engine like yours for WASM would be _huge_ in that it would pave the way to a new Silverlight fullfilling the initial 'WPF/Everywhere' promise,
and even to a 'Flash rebirth' without its flaws: the need for a plugin, no presence in iOS ...; among other benefits: my 2 cents

Thinking more about it, an XAML engine like yours for WASM would be _huge_ in that it would pave the way to a new Silverlight fullfilling the initial 'WPF/Everywhere' promise,
and even to a 'Flash rebirth' without its flaws: the need for a plugin, no presence in iOS ...; among other benefits: my 2 cents

That's so true! Thought we need to wait for CoreCLR WASM support before that, otherwise without C# it doesn't have so much profit for us. And that still will be a lot of hard work for NoesisGUI team...

I was thinking that a UI based on Noesis/WASM could, and should, be 'scriptable' in any WASM capable language,
but also in JavaScript, in the form of JS ViewModel classes bound to XAML views for example...

Anyway, I wish the Noesis team all the best: the possibilities opened by WASM and your technology are very exciting!

The scary thing here is exposing all the API from C++ to JS. We already did it with C#, and it is being really painful using SWIG. We would like to find time to try a different approach using LLVM (it wasn't so popular when we started this part in Noesis)

You could try bridge.net or jsil.org (.NET to Javascript compiler) maybe for part or most of the code. Not sure how useful it would be.

Wouldn't one way to go ahead with this be to just use native C++ and emscripten plus webgl? And compile that to asm.js and wasm in the future? This is how Unreal 3 was ported in 4 days.

A nice tutorial that shows how easy this is:
http://www.learnopengles.com/calling-op ... d-and-ios/

Or maybe one could modify the plugin for unity to support webgl
https://blogs.unity3d.com/2017/01/19/lo ... ity-webgl/

I think unity compiles C# to C++ and then uses emscripten to create asm.js, so if I'm correct this would allow using C# code too.

Of course the devil is in the infinite number of details