i think wicket starting out on 1.4 will need to stabilize properly on 1.4 before leaping to tiger. even though tiger has many tasty features like annotations and generics but since servers are still quite 1.4 friendly than
1.5, its important to consider that.
although if it has to change to 1.5, it should quickly make that jump before the user base grows too big so dat users wont have issues then
also if wicket suddenly leverages features in Tiger which many developers may still be learning, it may suddenly affect the learning curve of wicket.
on the overall, i want to vote for wicket staying at 1.4 for a while more
On 2/14/06, John Patterson <[EMAIL PROTECTED]> wrote:
On Tuesday 14 Feb 2006 11:43, Eelco Hillenius wrote:
> move. I am always in favor of clarity and breaking early in these
> matters.
>
I would certainly rather see wicket become a better framework than be held
back by backwards compatibility. Those who are not willing to refactor their
ui code can simply keep using wicket 1.2. It is a good product now and
always will be!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
--
"The more life's risk you take, the more life's reward you get" - Me
Aladejebi Ayodeji A., Project Leads
PentaSoft Technologies Nigeria Limited
Floor 1, AP Plaza, Ademola Adetokunbo Crescent, Wuse II
Abuja, Nigeria |Tel: 234-09-5233478 | Fax: 234-09-5233470
Interested in Java Development?
Visit my blog: Ayodeji Aladejebi's JBlog | http://blog.dabarobjects.com/
Community: Visit Cowblock.net, Nigeria
