> 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.
Nice idea, but personally I think this has all the potential of becoming a big can of worms fast. Know where to stop/ what not to cover will probably be very important. Also, several people, including myself, have given this idea a go, and it seems hard to end up with something that everyone likes, that is flexible enough to use yet simple. I think the best thing we can do here is to leave it up to people to do this in wicket-stuff. > 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. Sure. I can't think of much else than just those models though. A general remark about this list is that I also think this actually should be 1.4.1. We agreed a long time ago that 1.4 would be only the last missing parts of 2.0 (Java 5 related things, most notably generics). Like I predicted back then, it is taking us a long time to reach 1.3, and we should have the discipline of sticking to what we promised way back: 1.4(.0) is about the last 2.0 ports, and after we have a good 1.4.0 final, we can start on new features again. Eelco
