[Zope-CMF] Re: [CMF-checkins] renamings

[Dieter Maurer]

yuppie wrote at 2004-7-12 22:42 +0200:
> ...
>> My main reason is that it is different from "CMFFormController"s
>> paradigma.
>> 
>> While our "CMFFormController" discussion had the result that we currently
>> do not want to include "CMFFormController" into CMF, this may change
>> in the future. Useful, to use already now it paradigma -- especially
>> when the previous CMF releases did it...
>
>Not sure I did get your point. CMFFormController uses the '.cpt' suffix, 
>so we would rename forms anyway. The 'old' style (template starts by 
>calling a script) existed only on HEAD and was never released.

>Why is it harder to switch to CMFFormController after the renamings?

Looking again at CMFDefault, I had to recognize that it is
extremely long that I used it (and I used it only for a very short time).
The way, I thought CMFDefault would work is not how it does.

Thus, lets step back a bit:

  "CMFFormController" follows the paradigme: the HTML action target
  of the form is the form itself -- always.

  "CMFFormController" takes care of logic (by means of modular
  validation scripts) and navigation (maybe supported by further
  scripts).

This behaviour is easily emulatated by the form submitting
to itself and calling an action script at its top which in
turn emulates what "CMFFormController" would do.

That's the way I (and when I understood it right, Florent) favour.

I thought, that this was already the way, CMFDefault works now.
But that apparently was wrong. The renamings you proposed
may not be a step away form "CMFFormController", just not
a way towards it.


-- 
Dieter