Re[2]: doctypes

Thursday, November 24, 2005, 3:14:27 PM, Christian Stocker wrote:
CS> For the desicion of which stylesheet should be used, you can implement the
CS> public function getStylesheetNameById($path = NULL, $id = NULL) {}
CS> method in the new plugin and return an stylesheet according to the
CS> doctype. I don't know, how lenya does it, but I would suggest you just
CS> return  $doctype.'2html.xsl' for each different doctype. otherwise we
CS> need a central place for defining which xslt should be used for which
CS> doctype. We still can extend that later to make it more advanced.
Is this metod used automagically, or i should configure some pipeline
explicitely ?
Then i probably need also getPipelineName to return this specific
pipeline, handling various doctypes.
I still miss how to use resource properties or plugin methods inside pipelines.

>> == for specific content editor, with some forms, buttons and whistles:
>> bx_editors_fooedit, ext bx_editor

CS> Editors are "doctype" independent, so you could basically just use the
CS> BXE or oneform editor for your files. or write your own, of course.
For some strictly structured doctypes (calendar event, task shedule, user profile,
etc) it is probably better to have spelicized form-editor.
For text-style doctypes (like docbook), i will need to do tribal dance
to set up BXE to handle new schema.
Still dunno how.

-- 
 qMax

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