Yes, you can implement your own button bar which adds
AjaxFormSubmitBehavior to the normal wizard buttons.
Sven
Corbin, James wrote:
Thanks for the info Sven.
I assume by Ajax-ify you mean to create a new implementation that
mirrors WizardButton but extends AjaxButton instead of just Button?
Also, our code base is currently on 1.4.1, I noticed 1.4.3 (stable?) is
released but the main Apache Wicket Page hasn't been updated?
What are your thoughts on upgrading directly to 1.4.3, or should we
stick with a 1.4.2 upgrade?
J.D.
-----Original Message-----
From: Sven Meier [mailto:[email protected]]
Sent: Saturday, October 24, 2009 11:35 AM
To: [email protected]
Subject: Re: Wicket Wizard Functionality (Extensions)
Hi James,
regretfully the standard Wicket dialog doesn't support non-AJAX request
- perhaps this restriction applies to the YUI version too?
You'll have to ajax-ify the wizard - see Wizard#newButtonBar(). I've
done it for our project but I don't have the code available at the
moment.
Regards
Sven
Corbin, James wrote:
Hi Sven,
I'm running the wizard in a modal popup (YUI).
One other thing that is happening is when I press the next button in
the
wizard that should take me to the next step, my dialog closes. I'm
not
sure what would cause the dialog to dismiss/close in this manner.
J.D.
-----Original Message-----
From: Sven Meier [mailto:[email protected]]
Sent: Saturday, October 24, 2009 8:32 AM
To: [email protected]
Subject: Re: Wicket Wizard Functionality (Extensions)
Hi James,
>but Wicket's implementation seems to only evaluate the condition at
step
>creation and not when I'm changing the state of my radios.
see NextButton#isEnabled() and FinishButton#isEnabled(). As far as I
can
see these method should support your usecase. Implementing ICondition
as
you did seems right to me.
I assume you're notifying changes of the current radio choice to the
server via AJAX? Are you adding the whole wizard to the request so the
button bar is re-rendered?
Sven
Corbin, James wrote:
I am writing a two step wizard using wicket's wizard implementation
and
having some issues.
I am using Wicket 1.4.1.
My first wizard step contains a RadioChoice with 3 options.
I would like the Finish Button to be enabled on Wizard Step 1 if
either
the first or second radio choice is selected. Also, if the first or
second radio is selected, then the next button should not be enabled.
If the 3rd Radio Choice is selected, then I want the Finish Button to
be
DISABLED, and the next button to be enabled so the user can go to the
final step.
My question....
I'm not sure how to set this up in wicket's wizard implementation. I
tried specifying an ICondition on step two, to only make that step
available if the selected type is Radio Choice Option 3 from step
one,
but Wicket's implementation seems to only evaluate the condition at
step
creation and not when I'm changing the state of my radios
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]