Ideas for Wicket 7.0Page edited by Dominik DrzewieckiChanges (1)
Full Content
This page lists ideas what can be improved for Wicket 7.0.These are only ideas. Some of them may not be implemented though. There will be a separate Roadmap page that will have only the ideas on which we agreed. Ajax back button supportIgor has already started something about this at his GitHub Perhaps this is a better library than simple history: https://github.com/rails/turbolinks Better stateless support
Implement JAX-RS on top of Wicket IResourceCrazy, but why not ... PageParameters improvements
Removal of auto-componentsAuto components caused some problems due to their special lifecycle - they appear only during the rendering process. This will simplify component queueing, resolvers+auto components, problems with enclosures, ... Java 7 as a minimumJava 7 has nice support for generics, better annotations, and Java 6 is reaching its end of life pretty soon. Servlet 3 as a minimumWhile we opted to not require servlet 3 for wicket 6, it has bitten us a couple of times solving issues in wicket 6. Servlet 3 has been out for ages, so we should move with the times. Improved tag manipulationUsing attribute modifiers it is difficult to modify tags in proper ways such that existing classes on a 'class' attribute remain, while adding/removing other tags. A DSL for manipulating the class value of a component would be really great.
|
- [CONF] Apache Wicket > Ideas for Wicket 7.0 confluence
- [CONF] Apache Wicket > Ideas for Wicket 7.0 confluence
- [CONF] Apache Wicket > Ideas for Wicket 7.0 confluence
- [CONF] Apache Wicket > Ideas for Wicket 7.0 confluence
- [CONF] Apache Wicket > Ideas for Wicket 7.0 confluence