Josias Thöny wrote:
Hi devs,
Currently usecase views are being serialized as xhtml. There is an
option to override this by a request-parameter "asXML", in order to
serialize as xml.
For a special usecase I need to serialize as html-no-dtd, and I'm unsure
how to do that.
Should I also use a request parameter?
That doesn't sound very useful to me.
(The problem is that views with
multiple screens have to pass on this parameter, which is maybe not so
nice.)
Or should the usecase view have an attribute "serializer", which is
specified in the xconf?
That sounds nice, and conforms to the general Cocoon practise.
The problem is - how do you implement this in the sitemap? You
can't set pipeline component types dynamically, so you'd have
to add a selector and provide a set of default serializers.
Or is there a better way?
Another approach:
Maybe it should be allowed to declare an absolute view URL, so
that the view generation can be handled by a separate sitemap
(e.g. by a module sitemap)? The drawback is that duplication of
usecase.xmap code is required.
Anyway, we should try not to make the usecase framework too complex.
The flexibility is already far beyond my initial intention (with
CForms integration etc.), we should be careful that it remains
maintainable and easy to understand.
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
