On 12/23/05, Leandro Lucarella <[EMAIL PROTECTED]> wrote: > > This seems too painful, because you may end up repeating that > > information on multiple templates. > > About this, this is just an option, which makes much more clear the > separation between view, controller and model and can be used in a very > wide use cases. If you use the same form in 2 separated templates, you are > probably repeating information allready, so the ordering stuff is not you > bigger problem anyway.
Not really... you can drop a form object into multiple pages very easily, if it makes sense to do so. That said, adding this as an optional override seems reasonable. I've generally figured that the widgets/forms would need the ability to override at many points along the chain (in order of preference, lowest to highest: defaults, at the model, at the controller, at the view). Kevin
