Joern Nettingsmeier wrote:
Andreas Hartmann wrote:
Joern Nettingsmeier wrote:
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.
nice!
this would provide a really intuitive, consistent interface for users. i
don't know how to implement transformers, but i would like to see
someone do it :-D i'll be your alpha tester :)
OK - if you're interested in this functionality, would you mind
filing a bug, maybe with a syntax proposal, so that the idea
doesn't get lost? Thanks a lot!
-- 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]
