Forums | NoesisGUI

Hi, I am having some trouble getting a grip of the concepts of Xaml & noesis.

First of all :
Is it advisable to have all the Panels defined under a single xaml OR have a separate xaml for each panel? (Any overhead of this - even if those panels are offscreen/not visible?)

Secondly :
I wish to know what is the best way to make Panels that navigate from one to another? Say something similar to a powerpoint slide flying in from the side and sending the old one out?
I tried investigating and saw the Controls Gallery example and saw how you guys were loading a Xaml for every demo. But I couldn't understand how you guys did it - esp if there is any other way to choose what transition effect plays when you do load another xaml.

Some light on this should help.

BTW, I have seen that you all have an excellent product. I really think you guys should get some basic video tutorials out which explains how to make a simple game menu from scratch something like : Splashscreen > Main Menu > Options > Level Select > Loading Screen etc.
I saw a few other thread topics which asked about panels and transitions but I didn't get a simple and satisfactory enough answer that I could use.

Thank you!

Is it advisable to have all the Panels defined under a single xaml OR have a separate xaml for each panel? (Any overhead of this - even if those panels are offscreen/not visible?)

No, it is not necessary, you can have separate xamls for different sections of your UI. You just need a master xaml, a main window, where you connect the loaded xamls. If the design is not complicated you can have some panels at the same xaml and play with visibility/animations to show them when necessary. But for complex scenarios is better to factorize parts of the UI design in UserControls or separate panel xamls.

I wish to know what is the best way to make Panels that navigate from one to another? Say something similar to a powerpoint slide flying in from the side and sending the old one out?
I tried investigating and saw the Controls Gallery example and saw how you guys were loading a Xaml for every demo. But I couldn't understand how you guys did it - esp if there is any other way to choose what transition effect plays when you do load another xaml.

If you look at our ControlGallery sample, we designed a pair of storyboards that animates a fade out of a container with the current sample, and a fade in of another container with the next loaded sample. Then, when user indicates by selecting a new sample from the TreeView, we just load the specified sample, connect it to the corresponding container and begin the storyboard (this is done in the code-behind script: ControlGalleryLogic.cs, LoadSample() function).

You can have any number of animations that operate over a known container, then fire the one you want each time.

I really think you guys should get some basic video tutorials out which explains how to make a simple game menu from scratch something like : Splashscreen > Main Menu > Options > Level Select > Loading Screen etc.

Yes, we know that we need these video tutorials to help people new to XAML and NoesisGUI. We will try to dedicate more time to this point. About the sample you are describing we want it to be included in the 1.2 version. And a video building it up would be very useful and a great promotion for our asset too.