Re[2]: doctypes

Thursday, November 24, 2005, 12:28:34 PM, Christian Stocker wrote:
CS> On 23.11.2005 11:30 Uhr, qMax wrote:
CS> Do I see that correctly, that you want to have different XML documents
CS> (doctypes) throughout the whole websites, which should be translated by
CS> different xslts?
CS> So for example
CS> /foo/addresses.xml <- adress.xslt
CS> /bar/agenda.xml <- calendar.xslt
CS> /gnarf/alsoaddresses.xml <- adress.xslt
Yes, exactly like this.
I guess that i need to tell one text/xml from another using some
resource property,
i just dont know how to access it from sitemap pipeline.

CS> What you basically need here is a special plugin and then it should be
CS> doable. But before I'm not really sure, what you want, I wait with more
CS> explanations :)

Tonight i figured out that i need at least three plugins
to integrate new resource type:
== for resource handling:
bx_resource_foo, extending bx_resource
with some additional methods out of interfaces.
== for actual resource management:
bx_plugin_foo, extending bx_plugin
again with some additional methods out of interfaces used in
collection operations (copy/move/delete)
== for specific content editor, with some forms, buttons and whistles:
bx_editors_fooedit, ext bx_editor

And then setup them alltogether in
BX_HOME/conf/properties/properties.xml for property editor,
BX_HOME/conf/editors/foo.xml for content editor.

I'm just not sure how to allow several resource types in the same
collection.
Is declaring them all in <plugins> in .configxml the right way ?

At the moment i don't know how to properly distinguish doctypes of the
same mimetype, but it's probably a matter of using a property
(and an addresource-usecase parameter at moment of creation).


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