On 18 Mar 07, at 12:23 AM 18 Mar 07, Brett Porter wrote:
On 18/03/2007, at 11:29 AM, Jason van Zyl wrote:
Wouldn't documents like:
src/site/apt/guides/getting-started/index.apt
have the ${pom.name} expressions (which are meant to be
expressions) populated with the value?
Wouldn't break
On 18/03/2007, at 11:29 AM, Jason van Zyl wrote:
Wouldn't documents like:
src/site/apt/guides/getting-started/index.apt
have the ${pom.name} expressions (which are meant to be
expressions) populated with the value?
Wouldn't break them, they would render just interpolate the value.
So, ye
On 17 Mar 07, at 7:06 PM 17 Mar 07, Brett Porter wrote:
On 18/03/2007, at 9:56 AM, Jason van Zyl wrote:
On 17 Mar 07, at 6:37 PM 17 Mar 07, Brett Porter wrote:
What about anything with a .vm extension?
download.apt.vm gets processed as vm first, then apt. We can do
that in Doxia with z
On 18/03/2007, at 9:56 AM, Jason van Zyl wrote:
On 17 Mar 07, at 6:37 PM 17 Mar 07, Brett Porter wrote:
What about anything with a .vm extension?
download.apt.vm gets processed as vm first, then apt. We can do
that in Doxia with zero-configuration.
I really don't want it on by default,
On 17 Mar 07, at 6:37 PM 17 Mar 07, Brett Porter wrote:
What about anything with a .vm extension?
download.apt.vm gets processed as vm first, then apt. We can do
that in Doxia with zero-configuration.
I really don't want it on by default, because it'll break existing
documents
It won't
What about anything with a .vm extension?
download.apt.vm gets processed as vm first, then apt. We can do that
in Doxia with zero-configuration.
I really don't want it on by default, because it'll break existing
documents, and I can see situations where we might want to facilitate
differe
On 17 Mar 07, at 12:08 PM 17 Mar 07, Eric Redmond wrote:
Could this velocity pre-processor just be a plugin that gets run in
the
pre-site phase - unrelated to doxia?
It could and that's what the velocity people seem to be doing on
their site, but I would really like to not have to config
Could this velocity pre-processor just be a plugin that gets run in the
pre-site phase - unrelated to doxia?
Eric
On 3/17/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 17 Mar 07, at 2:23 AM 17 Mar 07, Brett Porter wrote:
> You've lost me, sorry. What type of page are you trying to create?
On 17 Mar 07, at 2:23 AM 17 Mar 07, Brett Porter wrote:
You've lost me, sorry. What type of page are you trying to create?
Any page, Velocity will be used to render any of the pages. It would
just work anywhere in the site.
I can see how this makes it possible to make lightweight reports
You've lost me, sorry. What type of page are you trying to create?
I can see how this makes it possible to make lightweight reports. I
don't see how it's useful in most documentation. I would think the
former would naturally be in a separate section somewhere, as opposed
to having to specif
On 16 Mar 07, at 8:00 PM 16 Mar 07, Wendy Smoak wrote:
On 3/16/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I'm leaning toward being on by default and letting people fully
utilize Velocity anywhere they like.
If Velocity is involved, please make sure the EscapeTool is available
so you can c
On 3/16/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I'm leaning toward being on by default and letting people fully
utilize Velocity anywhere they like.
If Velocity is involved, please make sure the EscapeTool is available
so you can convince it *not* to process certain expressions. This is
On 16 Mar 07, at 6:15 PM 16 Mar 07, Brett Porter wrote:
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 - th
On 16 Mar 07, at 6:09 PM 16 Mar 07, 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 bef
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 process
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
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
17 matches
Mail list logo
