Ah, sorry for my misunderstanding. Have you experimented
with IWizardModelListener#onActiveStepChanged()? Maybe you can get the ART
with AjaxRequestTarget.get() and add your overview bar.
On Thu, Feb 23, 2012 at 5:09 PM, N. Metzger wrote:
> Dan,
>
> that's not what I meant. It never occurred to
Dan,
that's not what I meant. It never occurred to me to make my entire
Application AJAX. I meant I can make an AjaxWizard, no problem.
My question was about the basic wizard, if I can have an overview bar that
is changeable while using the "regular" Wizard class. But I guess not...
Thanks,
Na
Like an application setting that AJAX-ifies your entire app? No, Wicket
makes AJAX relatively easy but you still need to make decisions, for
example about what gets rendered in the response.
On Thu, Feb 23, 2012 at 11:05 AM, N. Metzger wrote:
> Thanks for the quick reply!
>
> I think I can go th
Thanks for the quick reply!
I think I can go the AJAX way, I was just wondering if there's something
quicker than that.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Wizard-overview-bar-tp4414812p4414873.html
Sent from the Users forum mailing list archive at Nabble.
Hi Natalie,
If I understand your description correctly, then updating your wizard to
use AJAX is a matter of (1) replacing links/buttons with AJAX ones, and (2)
adding the overview bar to the AjaxRequestTarget so that it gets updated.
An approach to #1 is to construct links/buttons with a factory
