I am using 2.0 for development right now, with the intentions that by
the time I roll into production (3-6 months), 2.0 will be close to a
release version.  If 2.0 should get scrapped, it would take me probably
a week or less to port back to 1.3, so I'm not too concerned about
that.  What's important is that for us 2.0 users that we know sooner
than later if that is going to happen :)

My main reason for choosing 2.0 was jdk 1.5 support, and the long-term
picture that 2.0 would become the primarily used and supported branch by
the time I went into production (or at least getting very close).

The constructor change I like for the most part -- it seems to have
simplified my development a bit.  Not having to worry about calling
#add() is nice, and I haven't really run into any issues with code
explosion mentioned earlier in this thread.  I don't use markup to drive
components, so construction-time markup doesn't help me much.  A little
off-topic, but when I first started using wicket, I always thought it
would be more intuitive to do something like: 

panel.add( "myComponent", myComponent );  

Which leaves the constructors clean, and makes it very easy to
choose/pass around components, because the markup id doesn't need to be
known except by the parent thats actually attaching the component.  I
can't remember why things never ended up that way... I'll have to search
for that discussion thread. 

In any case, whether 2.0 is scrapped or not won't affect me all that
much... luckily most of my development thus far hasn't been on the web
tier so I'm only a few thousand lines of code with 2.0 and could revert
back to 1.3 relatively easy.

Aaron


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to