*sigh* Things have been very disruptive for me outside of work for the
past few days. I have a feature to cleanup and two more devcasts to do
that will make some of these things clearer. I'll see what I can
clarify below and we'll see if the direction I was heading works for
you.
On 12/16/05,
On 12/16/05, Kevin Dangoor [EMAIL PROTECTED] wrote:
*sigh* Things have been very disruptive for me outside of work for the
past few days. I have a feature to cleanup and two more devcasts to do
that will make some of these things clearer. I'll see what I can
clarify below and we'll see if
On 16/12/05, Jared Kuolt [EMAIL PROTECTED] wrote:
This brings up an interesting point. Should we allow for form
generation based on SQLObject-like classes?
This would be my preference.
I like the object/declarative way that SQLObject and FormEncode
schemas work, because it seems more
Dan Jacob wrote:
1. An error_handler argument to @turbogears.expose. This would simplify
code like this:
...
@turbogears.expose(html=templates.form)
def add(self):
return dict(form=article_form())
@turbogears.expose(inputform=article_form(), error_handler=add)
# go straight
On 12/16/05, Wavy Davy [EMAIL PROTECTED] wrote:
On 16/12/05, Jared Kuolt [EMAIL PROTECTED] wrote:
This brings up an interesting point. Should we allow for form
generation based on SQLObject-like classes?
There's a ticket open on this, just waiting for the implementation.
BTW, though
5 matches
Mail list logo
