Re: Re: [Bx-bugs] [Bug 899] doctypes

Hi again

I had some idea, about the getStylesheetNameByRequest method.

Why not add another method like

$collection->getPipelineParametersByRequest($filename,$ext)

and the plugins can return a whole array of pipeline parameters, the
xmldoc would then

return array("stylesheet" => "mystylesheet.xsl");

and the bxcms action puts them into the pipeline.

This would make it more flexible to add any parameter to the pipeline
and not just one called "stylesheet".

chregu

> 
> CS> Second: I'm a bit reluctant to add the
> "stylesheet" =>> $collection->getStylesheetNameByRequest($filename,$ext),
> 
> CS> by default to the bxcms action. It's another lookup added, which most
> CS> plugins don't need. OTOH, it doesn't look very expensive for most
> CS> plugins, so why not just adding it. There's just the other problem, that
> CS> it basically has the same meaning as the xslt parameter from .configxml.
> CS> Or do you use it for something else? Shouldn't it just be either xslt or
> CS> stylesheet?
> In .configxml there is a theme-related stylesheet.
> The pipeline parameter stylesheet is to transform xml document source
> into xhtml - it is different for each doctype,
> and there possible to have several doctypes in one collection.
> The stylesheet is configured in xmldocconfig, and could be retrieved
> by plugin_xmldoc, but it is not requested for pipeline properties.
> 
> CS> But looks good, do you have some examples somewhere to actually check it
> CS> out?
> Very soon i'll clean up my stylesheets for simplified docbook and
> glossary (a part of docbook also).
> 

-- 
christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich
phone +41 44 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71
http://www.bitflux.ch | [email protected] |  GPG 0x5CE1DECB
-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms