On 10/25/05, David Bernard <[EMAIL PROTECTED]> wrote: > > My proposal is a tool that generate : > * controller > * html templates > * a checksum (md5) for all generated files > > The generated file could be used as is or could be modified. > > If the model change : > * if checksum matches, then file could be regenerated > * else (or if no checksum), file generated is prefixed with "new_" >
So you need to apply your changes over an over again to newly generated files? I know that is not what I want and I doubt if it'll work for others. I like the Plone/Archetypes way: Yoi can do verything through a schema definition and customize alot (i.e. by defining your own widget macros, standard css customization, header/footer customization) and eventually, you can always create your completely own template. I guess that template could be generated (as a starting base) but it should not be the mailn way of creating forms/views > Modication in the model could be apply manually into the controller and > html, like for the database. > > Runtime widget generation need +/- to understand the widget generation > framework and how-to customize it. If you look at zope3, it's some > study and configuration. In the case of a tool, users don't need to > understand/learn a new framework to customize its application. They > only need to learn it if they want to customize the generation (adding > widgets, create a new set of widget,...) > > My goal (with TurboEngine) is to be able to create something acceptable/usable (but not perfect) without touching *any* html. I'm not planning on building a complex framework with a steep learning curve, but it's unavoidable to introduce some new concepts/classes/rules. Just because everyone "knows" HTML doesn't make it the correct approach to do further customization :) Regards Ivo -- Drs. I.R. van der Wijk / m3r Consultancy B.V. Linux/Python/Zope/Plone and Open Source solutions PO-box 51091, 1007 EB Amsterdam, The Netherlands Email: ivo <at> m3r.nl
