Re: my feedback after using 1.2.x in a real app

2006-11-16 Thread Erik van Oosten
Ah, you mean that the key names themselves are too generic. Ok, that is another thing. I'll leave that the to actual developers :) Erik. Alexei Sokolov schreef: I don't agree. At least rename them. Alexei On 11/16/06, Erik van Oosten <[EMAIL PROTECTED]> wrote: You can override keys in an

Re: my feedback after using 1.2.x in a real app

2006-11-16 Thread Alexei Sokolov
I don't agree. At least rename them. Alexei On 11/16/06, Erik van Oosten <[EMAIL PROTECTED]> wrote: You can override keys in any component. Please see here: http://cwiki.apache.org/WICKET/i18n-and-resource-boundles.html Alexei Sokolov wrote: > 1. Please remove 'null' and 'nullValid' propertie

Re: my feedback after using 1.2.x in a real app

2006-11-16 Thread Erik van Oosten
You can override keys in any component. Please see here: http://cwiki.apache.org/WICKET/i18n-and-resource-boundles.html Alexei Sokolov wrote: 1. Please remove 'null' and 'nullValid' properties from wicket/Application.properties The names are too generic and used by Dropdown controls. So tha

Re: my feedback after using 1.2.x in a real app

2006-11-16 Thread Igor Vaynberg
in 2.0 we recently introduced ComponentBorder and Component.setBorder (ComponentBorder) -igor On 11/16/06, Alexei Sokolov <[EMAIL PROTECTED]> wrote: Hey guys, [...] 3. Please fix borders. It's not natural to use as it is (in 1.2). Let me explain: [...] Alexei

my feedback after using 1.2.x in a real app

2006-11-16 Thread Alexei Sokolov
Hey guys, I hope it is not too late to make some minor suggestions for 2.0. I'm sorry, I noticed that you switched to apache mailing list too late... 1. Please remove 'null' and 'nullValid' properties from wicket/Application.properties The names are too generic and used by Dropdown controls. 2.