On 11/1/05, Jeff Grimmett <[EMAIL PROTECTED]> wrote: > On 11/1/05, Kevin Dangoor <[EMAIL PROTECTED]> wrote: > > > 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? ;-)
I googled for "life" and ended up buying one on eBay :) > > > 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. OK, that's a fine argument. turbogears.forms it is. I guess I don't want to get ri.diculo.us with the names anyhow. I like your example. I think I remember this line in the source for knotted.sandwich.pastrami: import pickle and I just couldn't convince the devs to hold the pickle. Kevin
