I think I'd like the option to, but not every time. Maybe it belongs
closer to the reporting infrastructure (the download pages are more
like the SCM/mail list types of pages).
Maybe that's the real future of those types of pages - the ability to
write simple velocity pages that get processed to spit out apt that
gets added to the list of docs to generate. Rather than affecting the
APT itself, it is a step before
WDYT?
- Brett
On 17/03/2007, at 9:09 AM, Emmanuel Venisse wrote:
Jason van Zyl a écrit :
Hi,
Do you think people would like to use Velocity for the pages of
documentation regardless of format. I've hooked it in to try it
but there are a couple options.
1) Use Velocity to process the pages before going to the
respective doxia parser
2) Make 1) optional
3) Just interpolate the documents like we do the XML forms of model
We can't interpolate every time. Sometimes, we need to interpolate $
{project.*} and sometimes not in dox
Emmanuel
I like the Velocity option, not sure if being on by default or not
is good. When there is a parse error I'm currently just rendering
the original document as is where you can see a warning and the
full error in debug mode. This is for 2.0 so it is a new feature
but would allow some cool stuff with.
Jason.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
