Re: Short term road map for Wicket 1.3
undo the constructor change and generics :) Go ahead Matej! Removing all the MainContainer parent from all the constructors is easy Just fine a good find and replace script.. ;) Then you still have about 10 hours straight work to fix everything.. But the result is of course perfect! johan P.S. don't forget to rollback the changes that we have now because we have the constructor change then.. :)
Re: Short term road map for Wicket 1.3
* SecondLevelCacheSessionStore * deferred sessions * stateless components (forms, links, but basically what we have now in 2.0). those 3 are on my list and i think i will do them as soon as possible (this week if 1.x opens up..) johan
Re: Re: Re: Short term road map for Wicket 1.3
On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean the removal of the object param? That would be cool too. Not sure if that is possible, however. And further mostly flattening the hierarchy, so that it is equivalent with 2.0 Martijn -igor On 11/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: * IModel hierarchy improvements whats that? The simplifications in IModel hierarchy of 2.0 applied to 1.3 i.e. collapsing of models. You did it, don't you remember? :D Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
Re: Re: Re: Short term road map for Wicket 1.3
i need some concrete examples here martijn! :) you think i remember every refactor i do? removing object will really break everything out there, so i don tknow if we want to do that in 1.x branch -igor On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean the removal of the object param? That would be cool too. Not sure if that is possible, however. And further mostly flattening the hierarchy, so that it is equivalent with 2.0 Martijn -igor On 11/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: * IModel hierarchy improvements whats that? The simplifications in IModel hierarchy of 2.0 applied to 1.3 i.e. collapsing of models. You did it, don't you remember? :D Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
Re: Re: Re: Re: Short term road map for Wicket 1.3
you mean things like removing the abstract compound model, etc? all that was done as part of removing the object param so without that there is no point in backporting. -igor On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: i need some concrete examples here martijn! :) you think i remember every refactor i do? Press f4 on IModel in eclipse in your 2.x workspace, and do the same for the 1.x workspace. Notice the differences in hierarchy. removing object will really break everything out there, so i don tknow if we want to do that in 1.x branch We could make it a vote... But I share your concern. It is something that existing users need to vote on I guess. For them it will make moving to 2.0 a bit easier. Martijn On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean the removal of the object param? That would be cool too. Not sure if that is possible, however. And further mostly flattening the hierarchy, so that it is equivalent with 2.0 Martijn -igor On 11/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: * IModel hierarchy improvements whats that? The simplifications in IModel hierarchy of 2.0 applied to 1.3 i.e. collapsing of models. You did it, don't you remember? :D Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
Re: Re: Re: Re: Re: Short term road map for Wicket 1.3
There is... I profiled our app, and creating a flat model hierarchy can save quite some memory. Every layer of inheritance adds a reference to the super type, and takes 4 bytes (see the LDM thread for more information). Saving this on the models gives extra room in mem usage. Same would go for components, but there the difference in functionality is larger, and there are much more types. Even so, I'm not sure that the removal of the object parameter was the only idea behind the flattening, it makes the hierarchy much cleaner. Martijn On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean things like removing the abstract compound model, etc? all that was done as part of removing the object param so without that there is no point in backporting. -igor On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: i need some concrete examples here martijn! :) you think i remember every refactor i do? Press f4 on IModel in eclipse in your 2.x workspace, and do the same for the 1.x workspace. Notice the differences in hierarchy. removing object will really break everything out there, so i don tknow if we want to do that in 1.x branch We could make it a vote... But I share your concern. It is something that existing users need to vote on I guess. For them it will make moving to 2.0 a bit easier. Martijn On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean the removal of the object param? That would be cool too. Not sure if that is possible, however. And further mostly flattening the hierarchy, so that it is equivalent with 2.0 Martijn -igor On 11/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: * IModel hierarchy improvements whats that? The simplifications in IModel hierarchy of 2.0 applied to 1.3 i.e. collapsing of models. You did it, don't you remember? :D Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
Re: Re: Re: Re: Re: Short term road map for Wicket 1.3
all im saying is that it wont really be backporting more of a rewrite without the object param change -igor On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: There is... I profiled our app, and creating a flat model hierarchy can save quite some memory. Every layer of inheritance adds a reference to the super type, and takes 4 bytes (see the LDM thread for more information). Saving this on the models gives extra room in mem usage. Same would go for components, but there the difference in functionality is larger, and there are much more types. Even so, I'm not sure that the removal of the object parameter was the only idea behind the flattening, it makes the hierarchy much cleaner. Martijn On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean things like removing the abstract compound model, etc? all that was done as part of removing the object param so without that there is no point in backporting. -igor On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: i need some concrete examples here martijn! :) you think i remember every refactor i do? Press f4 on IModel in eclipse in your 2.x workspace, and do the same for the 1.x workspace. Notice the differences in hierarchy. removing object will really break everything out there, so i don tknow if we want to do that in 1.x branch We could make it a vote... But I share your concern. It is something that existing users need to vote on I guess. For them it will make moving to 2.0 a bit easier. Martijn On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean the removal of the object param? That would be cool too. Not sure if that is possible, however. And further mostly flattening the hierarchy, so that it is equivalent with 2.0 Martijn -igor On 11/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: * IModel hierarchy improvements whats that? The simplifications in IModel hierarchy of 2.0 applied to 1.3 i.e. collapsing of models. You did it, don't you remember? :D Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href= http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
Re: Re: Re: Re: Re: Re: Short term road map for Wicket 1.3
LDM thread is: http://www.nabble.com/LoadableDetachableModel%3A-remove-boolean-attached-tf2553764.html On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: There is... I profiled our app, and creating a flat model hierarchy can save quite some memory. Every layer of inheritance adds a reference to the super type, and takes 4 bytes (see the LDM thread for more information). Saving this on the models gives extra room in mem usage. Same would go for components, but there the difference in functionality is larger, and there are much more types. Even so, I'm not sure that the removal of the object parameter was the only idea behind the flattening, it makes the hierarchy much cleaner. Martijn On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean things like removing the abstract compound model, etc? all that was done as part of removing the object param so without that there is no point in backporting. -igor On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: i need some concrete examples here martijn! :) you think i remember every refactor i do? Press f4 on IModel in eclipse in your 2.x workspace, and do the same for the 1.x workspace. Notice the differences in hierarchy. removing object will really break everything out there, so i don tknow if we want to do that in 1.x branch We could make it a vote... But I share your concern. It is something that existing users need to vote on I guess. For them it will make moving to 2.0 a bit easier. Martijn On 11/7/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: you mean the removal of the object param? That would be cool too. Not sure if that is possible, however. And further mostly flattening the hierarchy, so that it is equivalent with 2.0 Martijn -igor On 11/6/06, Martijn Dashorst [EMAIL PROTECTED] wrote: On 11/7/06, Igor Vaynberg [EMAIL PROTECTED] wrote: * IModel hierarchy improvements whats that? The simplifications in IModel hierarchy of 2.0 applied to 1.3 i.e. collapsing of models. You did it, don't you remember? :D Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
Re: Short term road map for Wicket 1.3
That was my personal roadmap :) On 11/6/06, Frank Bille [EMAIL PROTECTED] wrote: - Fix license header stuff - Synchronize WicketTester with Juergens changes - Backport some fixes - (2.0 and 1.3) Take a look at WicketTester to get it consistent with AJAX generated content. Frank On 11/6/06, Eelco Hillenius [EMAIL PROTECTED] wrote: Hi, I know we've been here before, but that was a couple of months ago, and opinions might have changed by now. What are your ideas about the /immediate/ roadmap for Wicket 1.3? I'm interested to learn what the first things will be that people will be working on when we start 1.3, and/ or what everyone's most important wishes are for this version. I'm not totally sure myself, but as Teachscape is nearing production and a conversion to 2.0 seems unlikely, I'm very interested in anything that will help it scale better: * SecondLevelCacheSessionStore * deferred sessions * stateless components (forms, links, but basically what we have now in 2.0). Of course, you opinions make more sense if you are planning on helping with implementing them, and if you have no real pressing wishes, don't state them here :) Eelco
Re: Short term road map for Wicket 1.3
Yeah, the license header stuff is not so much a wish as a must-have if we want to incubate :). On 11/6/06, Frank Bille [EMAIL PROTECTED] wrote: - Fix license header stuff - Synchronize WicketTester with Juergens changes - Backport some fixes - (2.0 and 1.3) Take a look at WicketTester to get it consistent with AJAX generated content. Frank
Re: Short term road map for Wicket 1.3
On 11/6/06, Eelco Hillenius [EMAIL PROTECTED] wrote: * SecondLevelCacheSessionStore * deferred sessions * stateless components (forms, links, but basically what we have now in 2.0). +1 on all, and add: * nested forms * validator changes * IModel hierarchy improvements * API clean up ([re]move RequiredTextField?) * reference guide Martijn -- a href=http://www.thebeststuffintheworld.com/vote_for/wicket;Vote/a for a href=http://www.thebeststuffintheworld.com/stuff/wicket;Wicket/a at the a href=http://www.thebeststuffintheworld.com/;Best Stuff in the World!/a
