Thorsten Scherler schrieb:

[...]

> Actually if we assume that we have on document as main entrance and the
> news is just an addon to this page, which will be rendered in some
> formats (like html) and in others not (like pdf), we can make the
> revision only depended on the main document. Where the main document can
> be perfectly an aggregation of different documents.
> 
> Let us see the aggregation that we had the other day:
>   <map:aggregate element="cmsbody">
>     <map:part
> src="cocoon:/navigation-element/breadcrumb/{2}/{3}/{5}/{6}/{7}"/>
>     <map:part
> src="cocoon:/navigation-element/tabs/{2}/{3}/{5}/{6}/{7}"/>
>     <map:part
> src="cocoon:/navigation-element/menu/{2}/{3}/{5}/{6}/{7}"/>
>     <map:part
> src="cocoon:/navigation-element/search/{2}/{3}/{5}/{6}/{7}"/>
>     <map:part
> src="cocoon://modules/languageselector/text-none/flagsize-13"/>
>     <map:part src="{resource-type:format-xhtml}?rendertype={1}"/>
>   </map:aggregate>
> 
> IMO the only interested part for the revision is 
> <map:part src="{resource-type:format-xhtml}?rendertype={1}"/>
> 
> The rest is presentational and not part of the document.

This would work only if we do the aggregation in the sitemap, and it
wouldn't be generic but require hard-coding the revision handling in
all sitemaps. When you use templates, you'd have to add revision control
specific control statements in XSLTs ...


> Meaning another option is to limit the revision to the main document,
> which is as well producing the overview in
> http://localhost:8888/default/authoring/index.html?lenya.usecase=tab.revisions
> 
> The revision link would open only the document (no nav, no menu, no
> nothing else but the result of
> {resource-type:format-xhtml}?rendertype={1}.
> 
> wdyt?

That would certainly be an option, but it would require hard-coding
the revision handling in sitemaps. We'd have to introduce a generic
concept of "page" vs. "revision" rendering.

-- Andreas


-- 
Andreas Hartmann, CTO
BeCompany GmbH
http://www.becompany.ch


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

Reply via email to