So you make your AjaxFallbackLink that does this:
class MyAjaxFallbackLink()
{
protected void onClick(AjaxTarget target) {
if (target == null) {
onFallbackClick();
}
else
{
onAjaxClick(target);
}
}
protected void onFallbackClick();
protected void
Although I'm not a committer, I'd like to open RFE for an API change, and
I'd like to get feedback from the devs.
Here's my complaint. When I'm using an AjaxFallbackLink, I'm making an
explicit decision that I want to handle ajax and non-ajax requests in
different ways. The problem is that
thats funny, i came to the opposite conclusion when designing it. most of my
usecases looked like this
onclick(AjaxRequestTarget) {
// dosomething
if (target!=null) {
// setup repaint
}
}
the // dosomething being the same between ajax and non ajax versions, so
having two methods
That's not a bad idea. it's a simple enough extension. I could even add
it to the wiki if anyone else has a similar use case.
On 1/8/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
thats funny, i came to the opposite conclusion when designing it. most of
my usecases looked like this
dont let me stop you :)
-igor
On 1/8/07, Ryan Sonnek [EMAIL PROTECTED] wrote:
That's not a bad idea. it's a simple enough extension. I could even
add it to the wiki if anyone else has a similar use case.
On 1/8/07, Igor Vaynberg [EMAIL PROTECTED] wrote:
thats funny, i came to the
