Re: Component.getString(String key)

2007-03-31 Thread Eelco Hillenius
https://issues.apache.org/jira/browse/WICKET-440 so anyone mind if i change getmodel() to null? i dont know if people depend on this, but imho this is definetely a bug I'm not familiar with how/ why that code is there, but I agree that it looks like a bug and can be removed. Eelco

Component.getString(String key)

2007-03-31 Thread Igor Vaynberg
the code for getstring(string) is currently: public final String Component.getString(final String key) { return getString(key, getModel()); } why is it involving the component's model in localization by default?? when used in conjunction with a compound model it causes this bug:

Re: remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Igor Vaynberg
then it would be more of a set() :) -igor On 3/31/07, Johan Compagner <[EMAIL PROTECTED]> wrote: if it was me just add() and should just replace if there is already one with that id if not then add. (and don't throw an error) thats how 2.0 really worked. (and for example Swing also) johan

Re: remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Johan Compagner
if it was me just add() and should just replace if there is already one with that id if not then add. (and don't throw an error) thats how 2.0 really worked. (and for example Swing also) johan On 4/1/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: should actually be called addOrReplace() :) -

Re: remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Igor Vaynberg
should actually be called addOrReplace() :) -igor On 3/31/07, Matej Knopp <[EMAIL PROTECTED]> wrote: I'm fine with either too. -Matej On 3/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > That's an idea too. It's an extra method (not so nice) but more pricise (nice). > > I'm fine with ei

Re: remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Matej Knopp
I'm fine with either too. -Matej On 3/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: That's an idea too. It's an extra method (not so nice) but more pricise (nice). I'm fine with either. What do others think? Eelco On 3/31/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > or add a replaceOr

Re: remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Eelco Hillenius
That's an idea too. It's an extra method (not so nice) but more pricise (nice). I'm fine with either. What do others think? Eelco On 3/31/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: or add a replaceOrAdd() method -igor On 3/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > I'm backpor

Re: remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Igor Vaynberg
or add a replaceOrAdd() method -igor On 3/31/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: I'm backporting Wicket In Action's code currently, and stumbled upon something I really liked to be able to do in 2.0 which I can't do in the same way in 1.3. Consider this: void setContentPanel()

Re: Vote: A few small changes

2007-03-31 Thread Jonathan Locke
well, trunk convertees aren't using these interfaces too much. sorry that this affects your chapter though. is there anyone actually -1? if not, i'll go ahead and make these changes. jon Martijn Dashorst wrote: > > +0 > > The biggest problem I have in renaming is that we mess again wi

remove check on previous child in MarkupContainer#replace

2007-03-31 Thread Eelco Hillenius
I'm backporting Wicket In Action's code currently, and stumbled upon something I really liked to be able to do in 2.0 which I can't do in the same way in 1.3. Consider this: void setContentPanel() { if (inEditMode) { new DiscountsEditList(this, "content"); } else { new Discounts

Re: Vote: A few small changes

2007-03-31 Thread Martijn Dashorst
+0 The biggest problem I have in renaming is that we mess again with trunk convertees, *and* that I have to revise a chapter I regarded finished. This may not be as big a change, but adds to the total. However, the names have changed for the better. Martijn On 3/30/07, Jonathan Locke <[EMAIL P

Re: Vote: A few small changes

2007-03-31 Thread Jonathan Locke
I didn't want this vote killed. I take it that nobody is -1 on us making these or similar changes (ala Eelco's note)? Jonathan Locke wrote: > > > Please vote +1/-1 all or per-item if you disagree with some but not > others: > > - make getRootModel(IModel) protected - i don't care much abou

Re: VOTE accept fix to WICKET-432 into 1.2.x

2007-03-31 Thread Gwyn Evans
+1 /Gwyn On 31/03/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: the subject says it all. i kinda jumped the gun on this one and committed already by mistake :( my appologies. if the vote doesnt pass i will revert it. -igor -- Download Wicket 1.2.5 now! - http://wicketframework.org