That's essentially what I did, but it's cumbersome and only allows for a linear flow - you can't for instance jump steps in the wizard depending on the choices chosen.
It would be much better to have a configurable flow - like sfEzcWorkflowPluign or something a bit more lightweight and easier to configure, like sfWorkFlowPlugin - which I started to rewrite, but then abandoned once I got involved with sfEzcWorkflowPlugin. On 8 Jan 2009, at 11:45, Gareth McCumskey wrote: > I also had to create a wizard setup. I ended up using a single view > with one form with javascript to simply enable/disable Next buttons > for validations and hide/show for showing the next step of the > wizard. While it sounds cumbersome it is actually one form and one > process so made it simpler so that the form could be re-used later > for editing purposes as well. > > On 1/8/09, Patrick Fong <patr...@ddns.com.au> wrote: > Hi, > > Yes that correct it's for a wizard! And the steps are fairly > similar, all > using the same objects so I think that one action is the way to go! > It keeps > everything centralised as you said. Thanks for the feedback, I'll > look into > the WorkFlowPlugin. > > A wizard plug-in would be great!! > > Thanks guys > > > > -----Original Message----- > From: symfony-users@googlegroups.com [mailto:symfony-users@googlegroups.com > ] > On Behalf Of Lee Bolding > Sent: Wednesday, 7 January 2009 11:27 PM > To: symfony-users@googlegroups.com > Subject: [symfony-users] Re: [symfony-users] > > > sounds like some form of wizard functionality... > > If it is, take a look at the sfEzcWorkflowPlugin > > I've made wizard-like behavior forms with Symfony before using a > mixture of custom validators and javascript, but I think there really > needs to be some kind of simple way to build wizards. > > Also, you may want to take a look at the sfWorkflowPlugin, but I never > managed to get that working. > > It would make sense to use 1 action with 3 different functions - eg > index (which would redirect to step1), step1, step2 and step3. > > Keeping everything in one action means that you haven't got scattered > validation and routing rules... keep it all in one place, makes it > easier to maintain. > > On 7 Jan 2009, at 11:52, Sid Bachtiar wrote: > > > > > Hard to say without knowing more about the problem. > > > > One thumb rule is if the 3 steps are radically different from one > > another, you should separate them into 3 actions. One big action > that > > does too much, too long, and too complex is simply not good. > > > > On Wed, Jan 7, 2009 at 5:51 PM, Patrick Fong <patr...@ddns.com.au> > > wrote: > >> hey all, > >> > >> > >> > >> I have a question that isn't really symfony specific but more about > >> applications design. My question is, if I have a process that has > >> say 3 > >> steps, should I separate those 3 steps into difference actions or > >> use one > >> action with different functions ? > >> > >> > >> > >> I'm not sure which would be the better approach, each has its > >> advantages/disadvantages > >> > >> > >> > >> Warm Regards, > >> > >> > >> > >> Patrick Fong > >> > >> > >> > >>> > >> > > > > > > > > -- > > Blue Horn Ltd - System Development > > http://bluehorn.co.nz > > > > > > > Lee Bolding > l...@leesbian.net > > "a successful framework finds users and sucks and diddles their > genitalia, it doesnt bend them over and make them squeel like stuck > pigs." Hani Suleiman, The Bile Blog > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
