Now that I've read this a few times, I think I see where you're going with this.
On 11/1/05, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > Code Generation vs. API Good so far. Write-once code generation is a symptom, not a solution-- see http://c2.com/cgi/wiki?CodeGenerationIsaDesignSmell > Widgets >From what I can tell, TG's widgets sound like more ubiquitous versions of Spyce's Active Tags. Is that the case? What are some of the differences? Active Tags are the only thing I really miss from Spyce (other than errors in .py files not bringing down the server... but more on that another time). > A TableForm displays a label for each field in one column of a table, > with the field controls in another column of the table. A TableForm > gives you a submit button for free. ...but it doesn't force you to use its submit button, right? Right? > Also, since the form knows what the > submit button was called, it is automatically thrown out. (Someone's > probably going to say "hey! I need that submit button value!"... > widgets are customizable through standard Python means. Subclass and > override. Piece of cake.) Thanks. :-) > The form will be redisplayed with good values prepopulated and the > invalid ones thrown out. An error message would be displayed next to > the "age" field on the form. And we all heave a sigh of relief that we > didn't have to do that in validation_error :) Not bad so far... what is has_errors (other than something that doesn't evaluate to boolean false)? It would be convenient to have it be a dict of keys_with_errors:bad_value, and then your 'if' would still work. -- Tim Lesher <[EMAIL PROTECTED]>
