Maybe check when it got added to the JS side. There might be a reason.
Peter may remember when he starts up in a few hours.
On the SWF side, for things like Button, separate models and views are
part of the extensibility pattern. Going back to the expanded form, a
TextButton would be something like:
<js:UIBase>
<js:beads>
<js:TextButtonModel text="Click me" />
<js:TextButtonView />
</js:beads>
</js:UIBase>
To make an icon and text button, you would do:
<js:UIBase>
<js:beads>
<js:TextAndIconButtonModel text="Click me" icon="foo.png"/>
<js:TextAndIconButtonView />
</js:beads>
</js:UIBase>
But all of that is how the SWF side builds up to emulating the HTML button
element. On the HTML side, we just use the element.
If you can make the argument that Image is not extensible (won't ever need
new properties) then you can take out the model and view on the SWF side.
On the JS side, I think we can take it away since we can directly store
what is in the model in the element and the element does the view's work
of layout/presentation. But again, I might be missing something, so let's
see if Peter remembers.
-Alex
