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.
-- Jörn Nettingsmeier "One of my most productive days was throwing away 1000 lines of code." - Ken Thompson. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
