Levels of abstraction?
Joeri Sebrechts
seem very true to life. They're too simple!
I'm used to dealing with screens that have hundreds of visual
elements, interacting in complex ways. Currently I'm using Ext JS as a
solution, abstracting away the DOM into components. Each component
encapsulates markup, behavior and style. By thinking in terms of
components the pages remain manageable (even with sometimes thousands
of DOM nodes).
Could model-driven views evolve into such a level of abstraction, or
are they more orthogonal, and would a different system be needed to
solve that problem space?
Rafael Weinstein
<joeri.s...@gmail.com> wrote:
> I think model-driven views are interesting, but the examples don't
> seem very true to life. They're too simple!
We'd love to get bigger examples. It's on our list. Only so many hours
in a day =-).
If there's an example you're keen on, patches are welcome!
>
> I'm used to dealing with screens that have hundreds of visual
> elements, interacting in complex ways. Currently I'm using Ext JS as a
> solution, abstracting away the DOM into components. Each component
> encapsulates markup, behavior and style. By thinking in terms of
> components the pages remain manageable (even with sometimes thousands
> of DOM nodes).
>
> Could model-driven views evolve into such a level of abstraction, or
> are they more orthogonal, and would a different system be needed to
> solve that problem space?
>
I think the two are very related problems. There's an existing
mechanism for creating components called XBL2 (it also does other
fancy stuff). The problem is that no one has implemented it yet. There
is work underway in Chromium, Mozilla, Safari & elsewhere to figure
out how to "whip XBL into shape" and I know that alot of that energy
is focused on the component problem. We're staying plugged into
developments there and our hope is that MDV and XBL/components can
work well together.