i don't know if anyone else has taken the time to try out Tools 2.x or cares about it yet, but i thought i'd give an update anyway...
- The minor issues with the IteratorTool and RenderTool demos have been resolved. - The VelocityStruts tools are fully up to date with the new infrastructure. - All the tools have been massaged so they should work with either the deprecated XMLToolboxManager and ServletToolboxManager or the new ToolManager and VelocityView infrastructure. Almost everything listed on the wiki planning page has been accomplished. Overall, i think things are about as backwards compatible as they are going to get. The current examples run on the new tool management infrastructure without any modification or problems. The only people likely to be bitten in an upgrade (not counting the many, many deprecation notices) are those implementing their own ViewContext or otherwise extending/overriding much of the ToolboxManager cruft. If the user and dev lists are any indication, such people are few and far between. As this is a significant milestone, i thought i'd ask if anyone is interested in having an alpha release or milestone build. I'd love to get some feedback on the progress so far, as well as the backwards compatibility of things. Would that help lower the barrier for some of you to try it out? As far as further development goes, these are what's next on my mind: - the drudgery of adding the great amounts of missing javadoc and updating the old stuff - creating more parity (perhaps even inheritance) between ToolManager (for non-webapp use) and VelocityView (for webapps). this idea is the largest threat to the stability of the new tool management API. - the possibility of more package shifting, specifically of the actual tool classes - updating and integrating Veltag (soon to be known as VelocityViewTag). this is greatly hampered by the static repo issues in Engine 1.5's StringResourceLoader, but i still want to move ahead on it now, without waiting on Engine 1.6. I'm still debating whether to forget about caching (leading to lousy performance) or include a light StringResourceLoader impl specifically for Veltag's use. - updating the example applications to be examples of the new management API (rather than demonstrations of the new APIs backwards compatibility) - updating/adding website docs for the new stuff and the many changes if anyone is interested in joining these efforts, that'd be swell. :) otherwise, i'll continue to plug along and look forward to your bug reports and patches once we actually get a release out. On 4/27/07, Nathan Bubna <[EMAIL PROTECTED]> wrote:
hey folks, so, i thought i'd give a heads up that VelocityTools 2.x has come along quickly. at this point, the new code can be used to build apps with much less configuration and much greater flexibility and power than the previous version. it is also almost completely backwards compatible. if you checkout and build the 2.x branch, you can run the simple and showcase examples with no changes and only two minor problems (having an issue with the IteratorTool and RenderTool demos). The VelocityStruts tools are not updated to work with the new system yet, but i should get to those soon. please feel free to check it out and give feedback. once i get 100% (or maybe 99.5%) backwards compatibility with the examples as they are, i will convert them to get rid of the deprecated config and such, in order to demonstrate the new configuration method(s). then we (probably i) can move on to bringing Veltag in (as VelocityViewTag) and perhaps creating a VelocityViewFilter and other such new possibilities. cheers, nathan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
