It seemed a bit odd to me to punish our users with multiple calls
because of something we didn't design well in the first place. Typical
case of where we should have provided an empty template method. It
would have my preference to fix that rather than doing the isEnabled
call twice.
Eelco
On
Can be of some use for wicket ?
http://www.theserverside.com/news/thread.tss?thread_id=44804
https://bean-properties.dev.java.net/
saki
Petr,
In what way do you think it might be useful?
Personally, I think that interoperability between bean-properties and
existing code would be more cumbersome then staying with getters/setters.
Regards,
Erik.
Petr Sakar wrote:
Can be of some use for wicket ?
Given that the US is sound asleep (at least I hope), I'll post now.
All continents had their share of time to review and no serious
concerns were raised.
Martijn
On 3/29/07, Martijn Dashorst [EMAIL PROTECTED] wrote:
Tried that but couldn't find the link. Thx... I'll update the link.
Martijn
On 3/30/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
well, however you fix it, imho the way it is now is broken.
No that's reversing it. It was truly broken, as it wasn't called at
all (in fact I committed the check on isEnabled just a couple of days
ago). Your concern is that it still not may
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 about this, it
just seems like harmless functionality to inherit
- make a public getRootModel() method that returns getRootModel(getModel())
- this one is
Can we also take the items outlined here into account?
https://issues.apache.org/jira/browse/WICKET-435
I'm pro those changes, but I'd like to look at the issues stated there
before putting my vote.
Eelco
On 3/30/07, Jonathan Locke [EMAIL PROTECTED] wrote:
Please vote +1/-1 all or per-item
i think you should propose a new merged vote then. ;-)
Eelco Hillenius wrote:
Can we also take the items outlined here into account?
https://issues.apache.org/jira/browse/WICKET-435
I'm pro those changes, but I'd like to look at the issues stated there
before putting my vote.
Eelco
Hello,
At the moment it is not possible to attach AjaxSubmitButton to button HTML
tag. Can somebody fix it?
Alex
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
+1
-igor
On 3/30/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
fixed in 1.x branch
-igor
On 3/30/07, Alexei Sokolov [EMAIL PROTECTED] wrote:
Hello,
At the moment it is not possible to attach AjaxSubmitButton to button
HTML
tag. Can somebody fix it?
Alex
12 matches
Mail list logo
