Jürgen Ragaller wrote:
Am 18.09.2007 um 10:48 schrieb Jörn Nettingsmeier:
Jürgen Ragaller wrote:
I thought I'd use the usecasedocument module as it is done in the
contactform module. What I like about it is, that cocoon.xconf only
has to be patched once for the usecase (no need for samples etc.).
And such a usecasedocument can be moved in the site structure like
any other resource type.
you are right. on second thought, a usecasedocument is certainly more
appropriate for your usage scenario.
But the usecasedocument module sitemap unfortunately eats up the dojo
scripts...
hmm. i just looked into this, and i think the usecasedocument sitemap
knows way too much about cforms-specific stuff... if i understand its
purpose correctly, all it should to is wrap a usecase invocation and
subsequent view as a lenya document - no reason at all it should be
concerned with cforms intricacies... but then, i haven't used it yet
or tried to fix it, so talk is cheap.
I just read
http://wiki.apache.org/lenya/HowToCFormsInLenya2.0
by bob
It seems to be another approach how to get cforms working (my confusion
now grows again...)
Has anybody achieved to get cforms working in a lenya page-envelope?
Maybe even as usecasedocument?
this document is slightly outdated and describes a "from scratch"
approach. your best bet should be to look at the cforms module *and* to
look around on the cocoon lists *a lot*. jeremy quinn has made huge
improvements to cforms during the last year, and afaik nobody has
reviewed these from a lenya pov yet. so you might find that the lenya
cforms module does things in odd ways that contradict the way the cocoon
folks are now doing it...
--
jörn nettingsmeier
home://germany/45128 essen/lortzingstr. 11/
http://spunk.dnsalias.org
phone://+49/201/491621
Kurt is up in Heaven now.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
