Yep, you're reading too much into that last paragraph. What I meant was...
forms are currently declared like this:
myform = TableForm([TextField("foo1"), TextField("foo2")])
and SQLObjects are declared like this:
class MyTable(SQLObject):
foo1 = StringCol()
foo2 = StringCol()
Some folks have expressed that they'd like forms to be like this:
class MyForm(TableForm):
foo1 = TextField()
foo2 = TextField()
which is consistent with the SQLObject style, but is not consistent
with how other widgets (TextField, for example) work.
Well, I can see the point of "some folks" in this case since it certainly jibes with typical GUI idioms I've used, at their simplest.
Yep. While some day someone may write a data-aware widget, the core, basic widgets know nothing and care nothing about what happens to the information once it gets into your controller method.
To me, that just seems like the right way to do it, but I'm fairly naive with regards to web apps.
--
"Things fall apart. The Center cannot hold."
- Life as a QA geek, in a nutshell.
Best,
Jeff
