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

Monday, January 30, 2006, 4:13:16 PM, Christian Stocker wrote:


CS> On 30.1.2006 10:54 Uhr, qMax wrote:
>> This looks very interesting, since it adds scalability,
>> and cleans up interfaces.
>> If i get right, this could generalize all of
>> collection::getPipelineNameByRequest()
>> collection::getPipelineNameById()
>> collection::getStylesheetNameByRequest()
>> collection::getFiltersByRequest()
>> plugin::getPipelineName()
>> plugin::getStylesheetNameById()
>> into just 2 methods of bx_plugin and bx_collection.

CS> Didn't think about that, but you're basically right

CS> it still needs 2 methods
CS> collection::getPipelineParametersById()
CS> and
CS> collection::getPipelineParametersByRequest()

CS> since the parameters are differernt.

There're
getPluginMapById()/getPluginMapByRequest()
+ bx_plugin::getIdByRequest()
Can't they help here ?


CS> chregu

>> 
>> Sunday, January 29, 2006, 6:38:07 PM, Christian Stocker wrote:
>> CS> Hi again
>> CS> I had some idea, about the getStylesheetNameByRequest method.
>> CS> Why not add another method like $collection->>getPipelineParametersByRequest($filename,$ext)
>> CS> and the plugins can return a whole array of pipeline parameters, the
>> CS> xmldoc would then
>> CS> return array("stylesheet" => "mystylesheet.xsl");
>> CS> and the bxcms action puts them into the pipeline.
>> CS> This would make it more flexible to add any parameter to the pipeline
>> CS> and not just one called "stylesheet".
>> CS> chregu





-- 
 qMax

-- 
bitflux-cms mailing list
[email protected]
http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms