i was just scanning the so-called "developer guide" on the website to see what logging control properties were documented there, and i had a tangential thought that never occured to me before.
the "user guide" and "developer guide" don't correlate to the velocity-user and velocity-dev lists. so i think perhaps some of those who post user questions to the dev list do so because they relate to the "developer guide" on the website. perhaps we should rename the guides on the website to prevent such confusion. essentially, the "User Guide" teaches people how to write templates in VTL. the "Developer Guide" teaches people how to develop applications that use Velocity. i haven't thought long about better names, but perhaps something along the lines of: User Guide -> How to Write Templates Developer Guide -> How to Use Velocity better name ideas are welcome... and as a bonus thought: you could probably break the Developer Guide into two guides, one more focused on using Velocity and another on the configuration minutia (which is not even fully documented). then we could have guides on: Writing Templates, Using Velocity, Configuration Options. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
