HiWell, if you know of all the steps but there's only some small difference (like you said, Step 6 might be D or F), you might also consider a normal Wizard, but use the conditional step functionality. That way you would add ALL pages, but hide those that are not relevant. Hiding can also be done dynamically, for example if on the first step, option A is selected, step 6 is visible, else not. This is done in each step by overriding the evaluate() method. If it returns true, the step is displayed, if false, not.
Matt John Armstrong wrote:
I've done this in both DynamicWizards as well as regular wizards and can pass some code along if you need it. My rule of thumb is "If you can gather all of the content together for your wizard use a regular wizard (eg: non-dependent configuration directives), if future wizard steps can change based on a specific wizard step then use a DynamicWizard (eg: If you pick A on Step 5 then Step 6 shows D, otherwise Step 6 shows F" I have found that controlling backwards and forwards navigation in a dynamic wizard very difficult since you are responsible for all of the logic. John- On Tue, Sep 8, 2009 at 8:30 AM, Eyal Golan<[email protected]> wrote:I had some experience with what you need so i hope I could help you if you need something. I implemented the dynamic wizard and it was actually lots of fun :) Eyal Golan [email protected] Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Tue, Sep 8, 2009 at 5:51 PM, Muro Copenhagen <[email protected]>wrote:Thanks Pedro and Peter, I'll try the DynamicWizardModel, it seems as the right choice. But a quick google search didn't provide any example, so i must try making it work. Hopefully it will... Best Regards Muro On Tue, Sep 8, 2009 at 4:35 PM, Pedro Santos <[email protected]> wrote:I think the wizard is the correct approach... You can try use DynamicWizardModel on your wizard. javadoc: * Wizard model that is specialized on dynamic wizards. Unlike thedefault,static * {...@link WizardModel wizard model}, this model isn't very intelligent,butrather delegates much * of the work and knowledge to the {...@link IDynamicWizardStep dynamic wizard steps} it uses. on IDynamicWizardStep you can implement the ordering and navegation rules based on database and page params. On Tue, Sep 8, 2009 at 11:20 AM, Muro Copenhagen <[email protected]wrote:Hi,I could use some input on how to solve a problem i have. In my web-app i have some cases, and each cases have several questions. And i want the user to flow between the pages in a wizard manner liketheexample in: http://www.wicket-library.com/wicket-examples/wizard/ The only problem i have is that all the questions are database driven,andis not a fixed set of pages. But the wizard example is in the link is fixed. How would i make a dynamic database driven wizard, where the content ofthewizard pages are database driven? Or is the wizard approach not the right way of doing it...? What i want to achieve is a user browsing through several question incase,with the option of moving backwards between the question. Any input from anyone ...? Best Regards Muro--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
smime.p7s
Description: S/MIME Cryptographic Signature
