Wow, Nathan-- This is really quite an accomplishment to get to this point.
Quick thought on versioning. Practically speaking, it seems that the work on 1.x is stalled with the main innovation happening with 2.0. So why not release 1.3.1 with the current trunk, then encourage users to migrate to 2.0for new features? (presuming an actual release of 2.0 is coming soon). We're too small a community to focus on dual trunks, I think. WILL On 10/26/07, Nathan Bubna <[EMAIL PROTECTED]> wrote: > > On 10/26/07, Christopher Schultz <[EMAIL PROTECTED]> wrote: > > Nathan, > > > > Nathan Bubna wrote: > > > I have scratched my main personal itches for VelocityTools 2, but > > > there are still some things i was planning to have before we release > > > 2.0, specifically updated docs, updated showcase examples, Tiles2 > > > support and complete caching for VelocityViewTag. > > > > Has Struts 2 pretty much obviated the need for VelocityTools -- at least > > the Struts-oriented parts? I haven't used S2, yet, but I'm reviewing a > > book about it and it looks like it supports Velocity right out of the > > box -- i.e. no Veltools required. Any thoughts? > > Yeah, no Struts-specific VelocityTools are needed for Struts 2; they > make heavier use of custom directives then i would, but it seems to do > the trick for them. Of course, many of the non-Struts VelocityTools > we have would still come in handy. > > > > Finally, my third question, will you help? Christopher S.? > > > > Sure. Some of my previous patches have been accepted, so I will continue > > to post them when I can help. > > :( sorry. please feel free to nag myself and the other committers! i > can't speak for them, but i, at least, respond positively to nagging. > i've appreciated all your help. > > > I never did come up with a unit testing > > strategy, and was beaten to the punch :) > > no worries. > > > > Oh, and if you want to help out with documentation for 2.0, i have > > > actually written quite a bit, but it is all plain text. I mostly > > > need help either integrating it into the old DVSL doc system or (if > > > you're feeling ambitious) Henning's new Maven-based doc system that > > > Engine is using now. > > > > What about using a Wiki? Or, are those seen as too hard to maintain when > > it comes to conflicting versions, etc.? > > Hadn't thought about that. unfortunately, we're just not set up for > it. Versioning is definitely a problem, but so is pulling the docs > out to ship with the releases. Our current wiki, to my knowledge, has > no solutions for either. > > Still, i might as well start there. At least the content i've written > so far would be public and those helping out can easily jump in. > > > -chris > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Forio Business Simulations Will Glass-Husain [EMAIL PROTECTED] www.forio.com
