Derek Hohls wrote:
Sylvain
Thanks for the explanation - I certainly the lack the depth
of insight and knowledge you have... but I have always
thought that form definition/template were v. closely related
(albeit with different purposes), and given that there is
usually a 1:1 relation between them, it has always seemed
to make sense to keep them together. I guess I will need
to 'rewire' my thinking here...
Well, for sure definition and template are related. But there's no real
architectural difference between form.sendForm() and a raw
cocoon.sendPageAndWait() with some additional view data. These view data
and/or forms must be known on both sides (i.e. the flow and the
template). The flow prepares them and the template displays them.
Perhaps along with the "cleanup", the Cocoon gurus could outline
some "good practice" for directory structures for flow/forms/db
applications (along with the rationale, so we could learn as well)?
The rationale is "store similar things in the same location". Now it all
depends on the meaning of "similar". IMO a JXTemplate without forms is
more similar to a JXTemplate with forms than a form definition is
similar to a form template.
Imagine for example an existing form-less template that, because of
evolutions in the application, needs to also display a form. Woud that
require to move it from the "pages" to the "forms" directory? IMO no,
hence this organization.
'Rewiring' in progress? ;-)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
