I've just converted over a project to 1.4-m3 from m1. I skipped m2
because of the drastic changes between 1, 2 and 3.
I must say, I think generics at a component level - when I initially started
using it felt like unneeded overhead - but it became more and more useful.
now that I've
Thinking about this - generifying panel would probably fix it - or i can just
make my own base panel with generics.
Ned Collyer wrote:
I've just converted over a project to 1.4-m3 from m1. I skipped m2
because of the drastic changes between 1, 2 and 3.
I must say, I think generics
I used M2 and had no problem with it. When I heard talk about
decoupling the components and the models, for M3, I thought that
seemed a good idea.
Now I use M3. It works fine, but I think generics for components is
implemented upside down. I think M3 should have been M2 with generics
turned
On Fri, 18 Jul 2008, Stefan Lindner wrote:
Thank you all for your work on wicket! Maybe we can see Wicket 1.4.0
final in the near future?
Thanks for the feedback and the thanks!
There are still 30+ open issues for 1.4
