Thanks again! I really appreciate your help.
I need this because not all the informations are shared between the
two views. Some are displayed by the first view and the same is true
for the second view. Plus, we are using a WYSIWYG editor and we don't
want the user to feel confused.
On 8/22/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> On 8/22/05, Alexandre Poitras <[EMAIL PROTECTED]> wrote:
> > Your solution seems to work but in the authoring area I don't get
> > the usual menus and navigation components. My page looks like it was
> > in the live area.
>
> No, you did it correctly. The issue is the Usecase hooks into the
> normal XMAP below the level the "authoring" GUI is added. This is
> necessary because the higher Pipeline sets the DocType. So the
> Usecase must reproduce code from the higher Pipeline. The only line I
> felt was necessary was the "strip_namespaces". I excluded the
> "resource-exists" and "language-exists" checks, the authoring GUI, and
> caching.
>
> I just added the following to the webpage:
>
> This is meant for multiple versions for display of data, so it only
> applies to the Live Area. If you want this to work with Authoring, add
> these lines:
> <map:match pattern="authoring/**.html">
> <map:transform
> src="cocoon://lenya-page/{page-envelope:publication-id}/authoring/{1}.xml?doctype={page-envelope:document-type}"/>
> </map:match>
> Just before each of the two lines:
> <map:transform src="../../xslt/util/strip_namespaces.xsl"/> I have not
> tested this yet, since I do not understand why anyone would want
> multiple display formats for editing.
>
> solprovider
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
