The only problem I have with "wizard" is that it implies a serial forwards-backwards flow. I can see cases for dialogs :-) with branches in them. (It's the same reason I took standard "next" and "previous" methods back out of the API ... the concept doesn't always apply.
To me, the lifetime of the state information is the key distinguishing feature to this gadget -- so if we don't like "dialog" then maybe some name around that idea would be more appropriate. Craig On Tue, 18 Jan 2005 15:16:16 -0500, Sean Schofield <[EMAIL PROTECTED]> wrote: > > I almost suggested the same thing: "conversation". Its length, > > though, could be unfriendly. ConversationController. > > What about "dialogue" with the "ue" at the end? > > What about "wizard?" This is what we call our own custom solution > that we're using now. Wizard generally implies a guided series of > steps where you can go forwards and backwards (at least to me it > does.) > > sean > > --------------------------------------------------------------------- > 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]
