This is really good stuff. Thanks for taking the initiative to get it going...
On Thu, May 24, 2012 at 10:51 AM, Nicolas LE BAS <[email protected]> wrote: > We have the 3 bindings votes to release it > and will probably have a consensus on Beta Quality. I'll try and complete > the release process this week or next. Mck, would you be willing to change your vote to Beta so we'd have full consensus? Or do you feel strongly that these should be GA? > 3.0 introduces tools to make tiles more maintainable across templating > technologies, including a stable (hopefully) API for rendering requests and > automatic tag generation. Otherwise, it's basically the same as 2.2. > One objective I have for 3.1 is to complete independence from servlets. On > a longer term, I'd like to try and introduce some cache management features > to support some extra use cases and optimizations. Indeed I'm starting to > think of tiles as an IoC framework for template-oriented programming. > What are your plans for Tiles? These are very good ideas. I like the direction I see of moving Tiles from yet another web application templating framework to essentially an offline or online templating system. As I've said before my long-term goal is to help mentor the regeneration of the team and move into a more backseat role. On that note I think our biggest hurdle at this point is to recruit some new developers. The ideas you point out below are good starting points because they draw from the user base we've had in the past. Greg > > * Promotion > It has been a long time without announce on the users ML; perhaps the beta > release will draw the attention of new users and/or developers. > We have an open issue with Spring for interfacing with tiles-3. Perhaps > it's time to update it, a good way to get the attention of the spring > community. Do we have a similar relationship with other projects? Struts > perhaps? > And finally I'm thinking of way to demonstrate and promote best practices > with Tiles. We had the showcase but it is difficult to keep it up to date; > perhaps a blog would make it easier for us, and at the same time more > accessible to inexperienced users. > > Nick. >
