| Nice one! It is so fundamental and has always seemed odd to me.
That interface almost put me off using Wicket when I first checked it out. I know that is a very superficial attitude, but first impressions are important. I think I may have even hit the back button and then returned for another look only after thinking "well the rest of the framework sounds good".
That makes me happier than it probably should. On 16 Jun 2006, at 12:53, Igor Vaynberg wrote: well, mark stumbled on some major work-in-progress. johan and i are still trying out our new idea to see if it will work. looks like it will though :)
just to quickly summarize some stuff for anyone interested
IModel.setObject(Component, Object) -> IModel.setObject(Object)
IModel.getObject(Component) -> IModel.getObject()
i know this is what everyone has been crying for and we listened. it took so long because it took some very innovating thinking to make it work <== we are still confirming if the idea actually does work :)
now for models that /do/ want to know what component they are attached to there are a couple of options. either pass the component into the constructor or
there are a couple of points where models can wrap themselves:
a) models can wrap themselves any time they are assigned to a component by implements
IAssignmentAware { IWrapModel wrapOnAssignment(Component); }
b) models that are inherited implement IInheritableModel (used to be ICompoundModel) and now also have IWrapModel wrapOnInheritance(Component)
just a preview of things to come
-Igor
On 6/16/06, Eelco Hillenius <[EMAIL PROTECTED] > wrote:Maybe we - core devs - should email about the major changes we are
doing in svn/ Wicket 2.0. It's all still very alpha though at this
stage.
Also, we could /consider/ putting those methods back in with final
(so your code will break) and a deprecation message? Or should we
just settle for search (/replace) facilities being good enough for
the job and list what needs to be changed.
And of course, once Johan and Igor are done with the model changes,
they will add a section to http://wicket-wiki.org.uk/wiki/index.php/
Migrate-2.0
Eelco
On Jun 16, 2006, at 4:16 AM, Mark Derricutt wrote:
> Just a heads up for anyone playing with HEAD/Wicket 2.0, one sneaky
> little trap I just found is that the Model class has changed its
> method signature from:
>
> public Object getObject(Component component)
>
> to
>
> public Object getObject();
>
> Anywhere I was extending Model this tripped up silently by -adding-
> my (now) overloaded getObject() method. On the one or two
> instances where I was using AbstractReadOnlyModel (which doesn't
> provide a standard getObject() method) this signature change was
> trippedup and lead to finding this breakage.
>
> Just a heads up for anyone else dipping there toes....
>
> --
> i like my video games - mamma said they are gonna melt my brains
> i like my video games - i don't care what daddy said; they're my
> reality
> - henning pauly
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
_______________________________________________ Wicket-user mailing list |
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
