For anyone wondering why I've been somewhat quieter than normal... we had guests over the weekend, and...
You have a life outside of Python code? Where'd you download THAT? ;-)
Today, I checked in the first bit of code for TurboGears' form
generator. (Aside: if you have any thoughts on naming for the forms
package, that'd be good. turbogears.forms seems lame.)
Everything below this is well above my head - I'm really new to web apps - but I will comment on this.
Keep it simple. turbogears.forms is concise, to the point. It tells me everything I need to know about what the module will do.
Not to put too fine a point on it, but consider another fairly popular framework that I'll call, uh, "knotted" for illustrative purposes. Does the name " knotted.sandwich.pastrami" really tell you a lot about what the module does? It may be the heart and soul of tw -- er, "knotted"'s authentication system, but it's not too obvious from the name of the module.
I'm a nuts and bolts guy. Direct, unambiguous naming conventions rock my world, pythonically speaking.
Of course, that may be an unpopular opinion. Maybe a poll? :-)
At any rate, I'm very interested in your thoughts on the forms module, where it's going, etc. It almost looks like you're using a wxWidgets model, based in HTML instead of a windowing shell - which seems logical to me. wxWidgets builds almost every 'widget' off of a few basic core widgets, in various combinations, and it works quite well for making Python GUI apps [1]. I can't see any harm at all in emulating (whether it's deliberate or not) a model that works.
--
"Things fall apart. The Center cannot hold."
- Life as a QA geek, in a nutshell.
Best,
Jeff
