I'd like to be able to set that as the data context (and get it back from the data context later) Working. I would expect binding expressions on arbitrary properties to work against the model As soon as you notify NoesisGUI system of property changes (just as you do when implementing INotifyPropert...

In another post chain there's a conversation about binding. The main bit about binding is the ability to bind to any property of a xaml element and have the ViewModel/code behind provide the notification when the underlying property/variable changes.. We will provide a function that will allow your...

The pricing document is not entirely clear on this issue, so we are going to update it.

The Unity license includes all supported platforms, which in version 1.0 will be: Windows, Mac OS X, iOS and Android. It will have to be purchased per Unity3D Pro seat as is the official asset store policy.

The TicTacToe example uses some Silverlight features like CompositeTransform and Projection, so you should create a Silverlight Application Project to be able to load it. Anyway, you can find a valid Expression Blend 4 project inside NoesisGUI SDK for the TicTacToe example: $(NoesisGUI_SDK)/Data/Pac...

So, I really did expect those styles to flow through since I had explicitly set them, but they didn't.

Do you mean you expect that styles defined in the resource file behave as the default (theme) styles?

Hi EisenbergEffect, sorry for my late answer. Data binding is not possible yet in Unity. We were working on this feature so it can be ready for the next update. The Unity API is a wrapper of NoesisGUI C++ API, where BaseComponent is our base class. In Unity you would have to inherit from this class ...

Hi jashan, Folder layout in Unity is one thing we would appreciate the collaboration of all of you, because we've seen many different layouts in already released plugins to make us think there is no standard or recommendation about :? We initially tried to put everything inside Plugins/Noesis folder...

Totally agree

That was something we fixed in current development and will be ready for the next release. All Noesis proxy classes will be under the Noesis namespace to avoid name collision.

Loading dynamically a XAML is a trivial task using C++ API. You just use the Resource System to load the XAML resource, and get the contents of the resource to assign them to the appropriate container: #include <NsCore/NsSystem.h> #include <NsResource/IResourceSystem.h> #include <NsGui/IUIResource.h...

The implementation of DropShadowEffect is empty right now
Effects is a feature that will be included in a future release, not for 1.0. I think we should remove everything related with effects to avoid confusion