Hi, 4.0 final seems to be close, is there a roadmap for future releases? Currently the tapestry site seems to be off, so I cannot check the wiki...
For example: - I think the most important is some more advanced state management! Nowadays Tapestry is not a good choice for desktop application-like webapps because it lacks state management. At least a versioned persistent property implementation (or equivalent minimal BACK-button handling) should exist. Someone could say that "Tapestry is not for such applications" but this means that it will lose a fast growing number of potencial users! State management complexity just grows if AJAX is used... - Based on discussions on the mailing lists, a more community-friendly project management is the key of Tapestry's future. There should be a very detailed roadmap for each release. I feel that it would help in contributions of new features/bug fixes as well. Users must see where Tapestry goes... - Some kind of integration with AJAX capabilites of Tacos (as soon as it is final). I don't have any problem with it as a separate library but I just don't feel comfortable with two separate Form implementations for example... - As webapps get more complex, more and more users want dynamic component definition and rendering capabilities. It may be similar to DynamicBlock but it would be an official implementation. Tapestry should have such feature even if it is not always the best practice for solving the problem ;) - Howard had some good ideas about components being plain POJOs with every needed dependency injected into them, and completely rewriting the rewind functionality. But these seems to be more complex modifications which should be addressed in 5.0 instead of 4.1/4.2/etc. (Of course I'm not in the position to define the roadmap :), or I may be wrong, or as soon as I see the list of planned features I will be the first who votes on them :))) Any thoughts? Regards, Norbi
