Too see how it looks: http://trac.turbogears.org/turbogears/attachment/ticket/613/move-to-forms.patch
Ciao Michele Michele Cella wrote: > Hi, > > Ok, I've just said to Ronald that widgets are almost stable now, I've > forgot to mention the last thing that *may* happen but that should be > totally user invisible, it's just an internal reorganization to make > things more clear and move some other things where they belong. > > The problem is that since the initial re-design many form related > details have found their way inside base.py again, for example the path > managing (update_path, path, name_path), is_validate, the validate > method and so on... this is not a big problem but it's not a nice thing > from an OOP POV but does not reflect the intended usage in a clean way. > > The idea is to move all these things inside forms.py to make it clear > that Widget is not a form specific component (this will also help us to > remove the "in_path" attribute) and that TG uses it to manage forms but > you can use it to do other nifty things totally unrelated to forms. > > What I want to ask is: > > 1) Opinions? > 2) I would like to also remove (given the previous discussion about > layouts and widgets) CompoundWidget and RepeatingWidget (the latter is > very form related) from there, is someone using CompoundWidget to do > something other outside of form things? > > I think this is a needed cleanup that we are doing now at the end as we > have a clear vision of the place everything should take. > > Ciao > Michele --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
