On 8/15/06, Joern Nettingsmeier <[EMAIL PROTECTED]> wrote:
i'm trying to integrate the tinymce editor into lenya 1.4, based on a
skeleton module from wyona.

tinymce has this cool feature that allows you to turn arbitrary elements
into editor instances. that means you can tell it to take over
"div#body", and you don't need to do any ugly pre-processing. basically
you can take the page as is and add some javascript, and it becomes
editable.

now i want to circumvent the jxtemplate mechanism, because with it you
get all kinds of cruft by default, such as the lenya logo and a complete
set of html headers. not nice.
i found that you can specify a cocoon source as usecase view in the
xconf patchfile, which i did.

now i'm creating the usecase view in the module sitemap, but the problem
is that i need access to the continuation id and the name of the
usecase. in a jxtemplate, i could do this (taken from the fckeditor module):
<input type="hidden" name="lenya.continuation"
       value="${continuation.id}"/>
<input type="hidden" name="lenya.usecase"
       value="${usecase.getName()}"/>

is there any way to access this information via an input module in a
sitemap?

(The following is based on Lenya 1.2 and Cocoon 2.1.9, but it should
apply to 1.4.)

{flow-continuation:???}
The FlowContinuationModule will return any attribute from the
WebContinuation.  I could not find any code that sets attributes in a
WebContinuation.  There is even a JS function to set them, but I could
not find anthing that uses it.

{flow-attribute:???}
The FlowAttributeModule returns any attribute from the
"cocoon.flow.context" object.  I am not certain it exists.

{request-param:lenya.continuation}
{request-param:lenya.usecase}
These should return the POSTed fields.

<map:match type="usecase" pattern="*">
{1} should be the lenya.usecase.  Use nested matches if you also need the URL.

Hope that helps,
solprovider

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to