yes.  also, i think it's much less shift than you are thinking, stefan. 
we've only really 
been talking about discontinuing the constructor change.  most if not all of
the other 
useful features in 2.0 would be moved into the 1.x branch, not discarded. 
and i think 
generics would probably be lightened, not dropped.  i imagine we will
present this
more formally once the constructor change discussion has completed, but i
suspect 
the basic idea will be that not all Components should be generified. 
instead, only 
subclasses that can really benefit like ListView, ListItem or DropDownList. 
it's almost 
definite that models would remain generified in whatever comes after 1.3. 
nobody is 
against generics on the team.  we love them.  but we don't want to overuse
them for
little or no benefit.  that currently seems to be the case in practical uses
of 2.0, so
that's why we're talking about stepping back and looking at it.


Martijn Dashorst wrote:
> 
> This is what we are discussing, and we ask our user community how much
> investment they have in 2.0, what they like about it, or don't, and
> how hard it would be to go back to the 1.x branch.
> 
> Before we have that picture clear we don't make a decision. Wicket is
> a community and we can't work without your input.
> 
> So voice your concerns, share your investment.
> 
> Martijn
> 
> On 3/7/07, Stefan Lindner <[EMAIL PROTECTED]> wrote:
>> We are a little bit confused about the future directions of the wicket
>> project. We startet switching from wicket 1.x to 2.0 in june 2006 and are
>> working with wicket 2 now for more then 10 months. One year ago it seemed
>> that wicket 2.0 (with generics and new constructor) will be the future
>> and was designed to overcome some problems that were within the design of
>> wicket 1.x. In other words, wicket 2.0 will become the new and better
>> wicket with the 1.x problems solved and 1.x will be put in a maintenace
>> only state when wicket 2.0 is ready.  Now it sees that the main
>> development is like "implementing new features in 2.0 and backport them
>> to 1.x" and if the process of backpüorting becomes too expensive, 2.0 has
>> to be modified to make it easier (go back to old constructor, degenerify
>> etc.).
>> Some postings on the developer list sound like "let's drop the whole 2.0
>> thing and concnetrat on 1.3, 1.4 and so on.
>> Can you help us to see a clear roadmap for wicket? What verson should we
>> concentrate on in further application development?
>>
>> Stefan Lindner
>>
>> -------------------------------------------------------------------------
>> 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
>>
>>
>>
> 
> 
> -- 
> Learn Wicket at ApacheCon Europe: http://apachecon.com
> Join the wicket community at irc.freenode.net: ##wicket
> Wicket 1.2.5 will keep your server alive. Download Wicket now!
> http://wicketframework.org
> 
> -------------------------------------------------------------------------
> 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
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Future-of-Wicket-2-tf3361195.html#a9352624
Sent from the Wicket - User mailing list archive at Nabble.com.


-------------------------------------------------------------------------
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