The first page has one question:
QA
The user clicks on an answer and another question appears:
QA QB
Again:
QA QB QC
The user goes back and changes the answer to the first question:
QA QD
As you can see, it has a lot of potential for duplication. Do I model each of these views with a different JSP? It would make for a lot of simple JSPs, but the naming scheme and Struts config would quickly blow up. I could do one JSP, but after some time, this could easily evolve into one huge JSP for the entire flow (ick!).
There's also tracking the answers. i.e., it would be ideal to use the same form for each page, so the answer to QA always stays in sync.
Any tips?
Thanks, Bob
Adam L wrote:
For what it's worth, check out the workflow extension, http://www.livinglogic.de/Struts It takes a bit of tinkering with to fully understand and appreciate its power (check the archives for a very recent dialog between myself and its designer, Matthias Bauer). It's very simple in concept and design, but it's thus far been able to handle almost every need I have for workflow management.
To put it very simply, you end up coding each component of your process as a puzzle piece. You then end up stringing them together with appropriate actions and forwards to create your workflow process. Component re-use has finally been realized for me in my workflows!
-- adam
----- Original Message ----- From: "Bob Lee" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 07, 2003 6:31 AM Subject: Wizard with a Twist
All,
I have requirements do develop a wizard like application where you can have multiple questions (up to 3) on a single page.
When there are multiple questions, the first appears, you select an answer, and the next one appears. If you change the answer to a previous question, all of the succeeding answers are reset and you have re-answer the questions.
What the next question is bears on the answers to the previous questions (or some other factors). I've deemed it okay to go back to the server each time.
There's also a requirement to do a bread crumb trail, but it will need to go back pages of questions (not one question at a time). Also, going forward, if questions have been answered and you don't alter the answers, you should be able to go forward page by page as well.
I'm trying to figure out the best way to break this down (i.e. how many JSPs, actions, and forms to use, what scope to use for the forms, etc.). Key factors for maintainability will be the naming schemes (so you can easily follow and manipulate the flow) and the ability to move questions around without impacting other questions too much or making changes in too many places. Any tips or suggestions?
Note: I started down a more generic route where I was going to build a tool to manage the flow, but there's so many weird requirements (things specific to certain questions, etc.) that I decided it would be easier to just start out simple for this iteration.
Thanks, Bob
P.S. I also have an option to use Blue Martini. Anyone have experience with this? Would it help me solve this problem more easily than just coding it with Struts?
--------------------------------------------------------------------- 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]
