On Wed, May 21, 2008 at 6:48 AM, Christopher Schultz <[EMAIL PROTECTED]> wrote: > Nathan, > > Nathan Bubna wrote: >> >> On Tue, May 20, 2008 at 1:02 PM, Christopher Schultz >> <[EMAIL PROTECTED]> wrote: >>> >>> Nathan, >>> >>> Nathan Bubna wrote: >>>> >>>> not exactly easy to find if you're browsing around, sorry. >>> >>> Yeah, not so much. It would be good if there was a collection of >>> configuration properties, maybe in a table on a web page. >> >> That would rock. wanna help? if someone got it started, i'd be happy >> to jump in. > > Sure. What's the best way to do that? Wiki? Web page in the site? If the web > would be better, how do I change stuff there?
Since you can, it's probably best to put it in the distributed docs, since the wiki is harder to version and distribute. Just check out https://svn.apache.org/repos/asf/velocity/tools/trunk and make the changes in the xdocs there. You should probably put the table into the xdocs/view.xml page, since most settings are for all VelocityView uses (VVS, VLS, and veltag) then perhaps we can add separate tables (which have links back to the main one) on xdocs/view.servlet.xml for VVS-specific properties, on xdocs/view.layout.xml for VLS properties. Veltag is a bit different, as it's specific properties are set via tag attributes and not velocity.properties or web.xml. Still, i suppose we could document those too. Really, though, the bulk of configuration possibilities are at the VelocityView level. So, i'd just start there and not worry about the rest right away. > -chris > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
