On 11/10/05, Rahul Akolkar <[EMAIL PROTECTED]> wrote: > > You can compare your > > testing examples with wizard, which works: > > http://www.superinterface.com/wizard/signupWizard.do > <snip/> > > Cool. Like the FrontController style setup, you've obviously spent > time thinking about these kind of usecases.
Yep, quite some :-) > > Try to use refresh, back, forward and other stuff. You can control the > > wizard using only designated buttons. The key point is redirecting to > > the same address. > > > <snip/> > > But, I'm not sure what to make of this (haven't looked at the code). > It is unclear to me how much effort is involved in making Shale > dialogs comply to the "redirect to same address" need. I cannot tell you about Shale since I use plain Struts + my own library. Anyway, the concept is simple: * keep the state on the server * after processing user input, redirect to the same address, this prevents browser session history from growing * serve pages as non-cachable, therefore... * whenever a user navigates to wizard location, he sees a page corresponding to current wizard state My wizard engine is very small, three small classes, no XML, no J2EE, can be tested in console app. Then I add UI to it, buttons that send commands, and panels/pages. > If you want to > showcase this with the Shale dialogs in the usecases war, I'd be > interested in knowing how much work was involved. ... > So, to re-iterate the requirements are: > 1) "Wizard style" dialog with bi-directional navigation > 2) Navigation using designated buttons, commandLinks etc. and browser > navigation buttons. > 3) Client - dialog alignment at all times, with minimum explicit authoring I don't think I will be using Shale anytime soon ;-) But I would like to showcase my approach in the comparison of wizards. After all, what matters is how browser sees it. > > On the other hand, this fiddling with navigation buttons is not much > > relevant for Ajax app. > <snap/> > > This is definitely a red herring. I am not sure what do you mean by red herring. Can you clarify, please? > I think it may be best to fork a new thread if we continue this > conversation, so we can follow the multiple approaches separately. Ok, please do start a new one with an appropriate subject. In User or in Dev? > As I said before, if you have the desire and the cycles, I'd be > interested in your rendition of the Shale usecases war (with your > preferred approach). Right, maybe I will try to implement my approach in Shale as well. > [1] http://people.apache.org/~rahul/shale/align-dialog/ The sample app initialized, but Tomcat does not see it running: "The requested resource (/struts-shale-usecases) is not available." Do I need something else besides the WAR file? Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
