If ComposableModel's semantics is similar to VW ApplicationModel then calling it the sameis ��probably an advantage, but but I can't help thinking that ApplicationModel is more related to the application domain than the UI as we need.�� The suggestion in another thread for ViewModel sounds better - but I haven't dug into Spec enough to get a feel for which is more appropriate.

cheers -ben

On Sat, Feb 14, 2015 at 5:39 PM, stepharo <stepharo@free.fr> wrote:

Le 13/2/15 14:58, Ben Coman a ��crit��:

On Fri, Feb 13, 2015 at 4:18 PM, Sven Van Caekenberghe <sven@stfx.eu> wrote:

Spec is not perfect, its main 'issue' is that the UI elements are called models, which confuses the hell out of people (me too in the beginning). But it does make sense, you model the UI (haha).

I find the same.�� So should we really rename ComposableModel to ComposableUIModel ? ��(And before Spec becomes more widely used?)

Yes we could in VW it is call ApplicationModel

��

cheers -ben