Hi guys,

thanks again for letting us use your test version of NoesisGUI for Unity. We startet using it and tried implementing what we want to achieve. But we encountered one major problem, where we couldn’t find any solution.

Just for your understanding: we use Unity as an 'extension' of our actual Software, meaning that our Unity Builds are plugged into our Software.

In our Software we have customer specific UI elements which are stored as XAML files and we want to send this XAML description to the Unity build at runtime, in order to show the correct customer UI. We need the UI to be completely customizable without the need to recompile the whole Unity project everytime (by editing the customer specific XAML file on our server).

We learned that a new XAML file can only be integrated into Unity BEFORE building the application, because the XAML parser isn’t available at runtime. Is this correct?

Can you see any possibility at all to achieve what we are trying to do with Noesis (e.g. enabeling the XAML parser at runtime)? If so, how?

Regards

Hi!

This is something we are finally addressing in v1.3, the runtime will understand XAML directly without preprocessing.

Meanwhile, in v1.2 the preprocessing code is there, you can use it to generate .xaml.nsb files from XAML files. Just have a look at NoesisBuildToolKernel.cs in the editor folder. This solution is far from perfect but several users are already using it and as said, take this as a temporary workaround,

Hi Jsantos

Is this API like NoesisBuildToolKernel.cs available in c++ version ?

thx aargh

Hi!

This is something we are finally addressing in v1.3, the runtime will understand XAML directly without preprocessing.

Meanwhile, in v1.2 the preprocessing code is there, you can use it to generate .xaml.nsb files from XAML files. Just have a look at NoesisBuildToolKernel.cs in the editor folder. This solution is far from perfect but several users are already using it and as said, take this as a temporary workaround,

Is this API like NoesisBuildToolKernel.cs available in c++ version ?

In C++ the recommended way is using the buildtool.exe

Hi jsantos,

thank you for the information. Awesome that you have already planned to implement the runtime import
Is there already a release date for 1.3 ? And is it possible to get access to another trail period to test the runtime XAML import for our purpose?

Is there already a release date for 1.3 ?

Beginning of 2016.

And is it possible to get access to another trail period to test the runtime XAML import for our purpose?

Sure, please email us about it.

thanks,