We want to separate View and ViewModel.
There are many MVVM solutions in the Web, but many think that observable objects are paying attention to transferring data to View. Although it is a useful function, it is not the essence of MVVM.
In a presentation layer where information such as business logic and view objects intersect, we want to separate responsibilities on a component basis.
The aim is on the principle of single responsibility. Creating code that fulfills a single responsibility principle is not painful, as it is not the purpose of reducing the amount of code.
In the world of XAML, it was able to respond flexibly. That's because the idea for describing code for View such as dependency properties and code-behind has been established
We are still under development. We will continue to strengthen the guide on more useful features and usage.
(The MIT License)
Copyright (c) 2016 uEN
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.