- AliciaCastillo
- Posts: 16
- Joined:
Is there a best structure to work with Noesis?
Hello! I'm using NoesisGui in Unity with VisualStudio 2022 and Blend.
I'm a bit new with NoesisGui, and I'm having some doubts about what would it be the best structure to follow for window navigation.
I'm used to work in WPF with a MVC structure and controlling navigation throught new Window instances but i've seen that Noesis uses the MVVM structure, and i've also cheked the examples and I see that, for example, in Ombra you use IsEnabled properties in <Components>.
All of this is making me wonder what whould it be the best approach for a new application:
Is it okay to have a XAML file for each window and navigate through them with a controller or a presenter as I'm used to or is not recommendable?
should I try to use this <Components> Example or maybe some layered composition in just one file?
Should I create different scenes in Unity with a XAML in each scene?
If you could give me some guidelines on what approach is better for which scenario it would be really helpful.
Thanks beforehand!
I'm a bit new with NoesisGui, and I'm having some doubts about what would it be the best structure to follow for window navigation.
I'm used to work in WPF with a MVC structure and controlling navigation throught new Window instances but i've seen that Noesis uses the MVVM structure, and i've also cheked the examples and I see that, for example, in Ombra you use IsEnabled properties in <Components>.
All of this is making me wonder what whould it be the best approach for a new application:
Is it okay to have a XAML file for each window and navigate through them with a controller or a presenter as I'm used to or is not recommendable?
should I try to use this <Components> Example or maybe some layered composition in just one file?
Should I create different scenes in Unity with a XAML in each scene?
If you could give me some guidelines on what approach is better for which scenario it would be really helpful.
Thanks beforehand!
-
sfernandez
Site Admin
- Posts: 3154
- Joined:
Re: Is there a best structure to work with Noesis?
Hi Alicia,
There are some tips in this post (viewtopic.php?t=3319) about application navigation.
As I explained there depending on the screen you would go for something more contained where visibility will show/hide parts of the UI, or directly load new xamls, probably via DataTemplates+UserControls or manually loading xamls and add them to the tree.
In MVVM is common to have a ContentControl that depending on the bound content type, it uses a different DataTemplate that loads different views (UserControls).
Please let me know if you need more detailed information about this.
There are some tips in this post (viewtopic.php?t=3319) about application navigation.
As I explained there depending on the screen you would go for something more contained where visibility will show/hide parts of the UI, or directly load new xamls, probably via DataTemplates+UserControls or manually loading xamls and add them to the tree.
In MVVM is common to have a ContentControl that depending on the bound content type, it uses a different DataTemplate that loads different views (UserControls).
Please let me know if you need more detailed information about this.
Who is online
Users browsing this forum: Google [Bot] and 7 guests