> 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.
Actually, on second thought... I don't think this is important enough. Deprecation with a note that this model isn't really needed anymore should be good enough. Not important enough to break clients over imho. I think the models are they are now are fine. We've tweaked them a lot in the last few releases, and now is the time for stability. Eelco
