[CONF] Apache Wicket: Wicket 1.4 Wish List (page edited)

[confluence]

Page Edited : WICKET : Wicket 1.4 Wish List Wicket 1.4 Wish List has been edited by Korbinian Bachl (Dec 15, 2007). Change summary: Added Clean up/ Have a look at Models idea (View changes) Content: Remove Change and possibly VersionManager no longer needed since we serialize the entire page. Downside - makes HttpSessionStore not as space efficient Remove PageMap PageMap is a misnomer and isnt really needed anymore - not with second level session store around. Transparent clustering support out of the box and enabled by default Window scope this will basically replace PageMap and allow users to store per browser tab/window attributes JDK-1.5 support Generify models Use varargs, for instance (a bad example) MarkupContainer#add(Component) -> MarkupContainer#add(Component...) Make WicketTester a first class citizen Currently WicketTester is one of the less mature parts of the core project. It really is useful and great, but the API is not thought through and there are lots of areas you still can't test. Migrating the API to a Junit 4.4 + Hamcrest style of programming would be a very nice addition. Establish Wicket Security strategies sub project Make Swarm part of wicket core - Giving users easier access to a security framework. Move auth-roles into sub project Improve Tree model the tree can use a more web-friendly model then swing's tree model Add Rapid Prototyping Forms The Idea of Alistair Maw and Jonathan Locke (ROR? No. Wicket on Wheels.) should be included in next Wicket. A set of nice looking Defaultformcomponents and a Beanresolver to automatically let create forms from just the plain bean but still allow to customize it later by overiding parts of it. Beside nice looking (to show/ even may go live with it in first place) and fast it should have enabled possibility to integrate security on a Form as well as Field-level. Clean up/ Have a look at Models With now having a CompoundPropertyModel that has the same abilities as BoundCompundPropertyModel it might be nice to have someone overwork all models and decide if we really need all. Stiping out/ Migrating ino one e.g.: BoundCompoundProperty and CompoundProperty model as well as others (if possible) would really ease wicket for beginners as well as save experienced users some thoughts about what model to use.

Powered by Atlassian Confluence (Version: 2.2.9 Build:#527 Sep 07, 2006) - Bug/feature request

Unsubscribe or edit your notifications preferences