Joern Nettingsmeier wrote:
Thorsten Scherler wrote:
I totally agree that we need private meta data and would like to remove
the lenya:internal data block from the generator since it is causing
many confusions and this private data should not be exposed to xml.
well, i'm using it in the main site aggregator.
the advantage of a generator that spits out all the available metadata
at once (as opposed to singe-value input module calls like andreas
suggests) is that a) you see what's available at a glance and b) you
avoid having to pass several parameters to your xsl transformer which is
always kludgy, since both the sitemap and the stylesheet have to know
about those parameters.
i see the architectural benefits of andreas' approach, but it's not as
easy to learn to use as the current all-in-one generator. and imho
ease-of-use on the sitemap level is currently under-valued in lenya. the
sitemaps are the primary api for most new users, and they need to be
lean and mean.
if we go with the input module approach only and ditch the generator, we
need very good documentation which must be updated frequently. the
generator just outputs all available fields, so it always represents the
current range of possibilities without requiring updates...
Another approach would be templating.
Use some specific elements / attributes:
<p>Published by <workflow:lastUser event="publish"/> ... </p>
and fill in values using a transformer:
<map:transform type="workflow-template"/>
This way, you don't have to pass the parameters explicitely to the XSL.
-- 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]
