On 12/20/05, Ian Bicking <[EMAIL PROTECTED]> wrote: > Again, it has something to do with work flow -- htmlfill is written with > designers in mind, while widgets are more programmer-centric. There > should be room for both techniques, without trying to encorporate both > cases into the same interface.
This is funny, in a way. Cheetah is a more programmer-centric template system than Kid. So, it's hard to say which is more designer friendly: widgets with individual templates, or Cheetah+htmlfill. Widgets *do* actually have a way to be completely designer friendly via the "source" view of a widget. Basically, the workflow is that the programmer creates the form object with the appropriate fields/validators (or automatically using a utility function) and the widgets spit out the Kid template for the whole form, ready to drop into a template. The idea is that the form would function the same as a generated form, but is fully customizable, even with WYSIWYG tools (that are XHTML capable). The basis for this is there, but it'll take more tools to make it slick and very usable. Kevin
