MVC Application Model a.k.a. MDV a.k.a. MVVM a.k.a. Presentation Models
Joachim Wester
have worked with SmallTalk Application Models and I've used
syncronized tree based models to drive the UI ever since. If anyone is
in doubt, I can assure you that this stuff will make you much more
productive. It is especially nice when you have glued the ViewModel to
the other end such that your controller and model is always in sync
(whenever a change in the domain model occurs, it is propagated to the
controller and then to the view model and viola, the view is updated
and vice versa).
Although I have not yet looked into your proposal in great depth, I
hope that you will not underestimate the need to hook in to the
declarative binding and declarative templating mechanism to allow the
creation advanced user interface components that can act as good
citizens. Lets say that instead of a DOM tree of <UL> elements, the
view model is suited to drive something using WebGL, SVG, Canvas, a
Joystick, a Barcode scanner etc, a web socket based output device etc.
p.s.
If you made sure your samples worked, this would soon become a
community hit. I know your proposal is aimed at other browser
implementors, but I think the mdv concept is so strong, it can gain
momentum in the community. I wish it was half as polished as the
alternative that Microsoft endorsed (http://www.knockoutjs.com).
Google mdv is conceptually very strong.
Thank you
Joachim Wester, Starcounter
Joachim Wester
bad ones as things remote to the DOM would not interfere and
registering observers to the model would suffice. The concern is
rather user interfaces needing advanced DOM trees with non simplistic
relationships between view model and the reflected state of the DOM
(data grids, charts, etc).
/ Joachim