Forums | NoesisGUI

Hi there!

I'm trying to integrate with an existing Unity project and am having a bit of trouble. Following the documentation here leads me to thing that I should be creating an entirely separate solution for the UI work and to link to samples and such.

This does nothing but toss up lots and lots of errors (I'm guessing because the new solution/project doesn't have any references to the Neosis namespace).

What's the correct way to get up and running with an existing Unity project?

Thanks!

---Edit
So just blindly trying things, I clicked to show all files in solution explorer, and then added the entire Samples folder to the project (the sln and csproj are sibling of the Asset folder).

The big thing that seems to be causing the errors is:
Undefined CLR namespace. The 'clr-namespace' URI refers to a namespace 'NoesisGUIExtensions' that could not be found. LostHaven1UI I:\Savatronix\SourceControl\Lost Haven 1\Assets\NoesisGUI\Samples\ControlGallery\Resources\Text.xaml 4

Which then goes on to generate more errors anywhere else that namespace is used (few places in the Text.xaml).

We are investigating now how to improve the xaml processing to avoid some dependency errors.

About the namespace error, in our github we provide some classes, defined under the NoesisGUIExtensions namespace, to help integrate Blend with NoesisGUI: https://github.com/Noesis/noesisgui-con ... ster/Blend

You need to add them to your Blend project outside the Assets folder.

Thanks.

It looks like there might be a missing tutorial as well.

http://www.noesisengine.com/docs/Gui.Co ... unity.html is linked to in the user control example ( http://www.noesisengine.com/docs/Gui.Co ... unity.html ) in between the xaml and c# code parts.

I'm guessing that tutorial is to show off how specifically to use noesis with Unity (since code behind is a little different, as I'm assuming the c# will end up being a monobehavior attached to a gameobject of some sort).

I've got a lot of questions on how how to begin from the code side of things, and I'm guessing that tutorial would hold most of the answers since I'm assuming "unity-land" is going to end up being quite a bit different than native.

+1 -- would really love to see this Unity tutorial fleshed out and updated for 2x

The native and the managed tutorial for extending Noesis was unified into a new tutorial available at (we will fix the typo, thanks!)

http://www.noesisengine.com/docs/Gui.Co ... orial.html

I'm guessing that tutorial is to show off how specifically to use noesis with Unity (since code behind is a little different, as I'm assuming the c# will end up being a monobehavior attached to a gameobject of some sort).

You can follow that approach (Monobehavior that gets access to the tree through the component) or better yet you can use code-behind using the x:Class keyword as we do in all the provided samples. This tutorial is also interesting for that (we need to improve it though):

http://www.noesisengine.com/docs/Gui.Co ... orial.html