Kevin Dangoor wrote: > Hi Michele, > > It took me a bit longer to get back to this one.
No problem. ;-) > > The default templates need to be stored somewhere, of course. Since > these initial ones were pretty small, I decided to just stick them in > there with the code. They remain easily overrideable. > Yes, this makes sense. > > This makes updating painful. If the widgets are well-written, most > people won't be overriding many widgets for their projects. But, if > they had a copy of all of the templates then for each update of > TurboGears they'd have to regenerate templates that had been updated > with changes to the widgets. :-( Haven't thought about this, it will quickly become a nightmare to maintain. You are absolutely right that (hopefully) well written widgets will not be overridden that often. > > What I would be in favor of is making a widgets.py file with a couple > of override samples. > > Form will actually be a base class, and there will be a couple > different standard varieties (that will likely only vary in the > template they use). > Like TableForm, DivForm... > > Because widgets are standard Python modules with some additional > resources, they can be deployed easily as eggs. > Great, hope TG will provide a central repository also for third party widgets eggs. > I have a plan for providing easy access to the widget templates when > you want to update them. Yes, that's quite important. > > Yes, indeed... and I hope my thoughts on this become a bit clearer as > I get some of my ideas out there in code. Absolutely let's close this discussion here so that you can focus your work on your own ideas, I'm sure that what you are doing will be the right thing otherwise we can always talk about it. :-) > > Kevin Ciao Michele
