Documentation issues
Posted: 16 Nov 2018, 13:00
As I wrote in other recent posts, I'm currently evaluating Noesis for use in the UX company I work at.
The main issue I see so far is the total lack of any documentation in most parts.
There are a few samples and a few documentation pages, but those are almost all geared towards Unity developers trying to understand WPF style development.
There is no documentation for WPF developers, trying to port a project to Noesis, which is exactly our use case.
We know exactly how to develop for WPF, so we need clear documenation on what we need to change in workflow to work with Noesis compared to that.
There is almost nothing available in that regard.
The samples use InitializeComponent(); differently, but there's no line about the why.
There is no clear documentation talking about how the unity/Noesis workflow for a MVVM architecture may differ, how the setup can be different, what APIs need to be used differently, what types are missing etc.
Also I had to guess where to load a general themes.xaml since there is no App.xaml support. I'm GUESSING that needs to go to NoesisSettings->Application Resources. But I didn't find any documentation to confirm that.
Is there any way this situation can be improved? Otherwise I'll have a hard time recommending Noesis to our teams, considering I basically have to tell them "it somehow works if you know how you have to do things, but if you don't there's no place to read up on the why"
The main issue I see so far is the total lack of any documentation in most parts.
There are a few samples and a few documentation pages, but those are almost all geared towards Unity developers trying to understand WPF style development.
There is no documentation for WPF developers, trying to port a project to Noesis, which is exactly our use case.
We know exactly how to develop for WPF, so we need clear documenation on what we need to change in workflow to work with Noesis compared to that.
There is almost nothing available in that regard.
The samples use InitializeComponent(); differently, but there's no line about the why.
There is no clear documentation talking about how the unity/Noesis workflow for a MVVM architecture may differ, how the setup can be different, what APIs need to be used differently, what types are missing etc.
Also I had to guess where to load a general themes.xaml since there is no App.xaml support. I'm GUESSING that needs to go to NoesisSettings->Application Resources. But I didn't find any documentation to confirm that.
Is there any way this situation can be improved? Otherwise I'll have a hard time recommending Noesis to our teams, considering I basically have to tell them "it somehow works if you know how you have to do things, but if you don't there's no place to read up on the why"