Frank Mei�ner wrote:
> <table id="itemtable" visible="true"
InitType="test.model.ItemTableModel"/>
Actually, I did have a question about this. Does this call a JTable
constructor with what it gets from the InitType parameter? That does
make things a bit more useful.
> Defining (or rather: assigning) actions to GUI elements is a very fine
> thing to do. But to define the control flow of the application entirely
> in XML is IMHO a bit off the road... You will probably end with swixml
> becoming something like luxor (xul) or jelly. In fact, maybe this is
I agree, and I understand and agree with Wolf's focus on doing one
thing, and doing it well. That's why I'm curious if there is a place
for this stuff, either in add-ons to SwixML, or in slightly seperate
SwixModelML and SwixEventML projects. That is, projects that are made
to work with Swix, without changing what SwixML is.
I just kind of look at this like we have the View part of
Model-View-Controller (MVC) done really well in SwixML. I was looking
at the other parts. It would be nice if we could have as simple a
language for Model and Controller (Events, sorta).
I definitely don't want something complicated. Perhaps I should code up
something simple and post it out here as an example.
Pat.
