What is this 'conversation' all about? It doesn't seem to be a known concept in any GUI guideline I know (e.g. Apple's Human Interface Guidelines). Neither does wikipedia list it under http://en.wikipedia.org/wiki/GUI_widget.
This is what wikipedia is saying about Seam's conversation: 'The default Seam context is conversation which can span multiple pages and usually spans the whole business flow, from start to finish.' This seems to describe a http://en.wikipedia.org/wiki/Wizard_(software) . IMHO 'conversation' is a buzzword invented for those who still think a web UI consists of a sequence of HTML pages only. Back in 2000 the same guys invented 'mvc-2' and told us that a UI can be built on actions only. Just my rant (worth 2 cents or less). Back to Wicket and wizards: For a wizard I'd suggest to use a single Wicket page, replacing components as you step through it. Note that Wicket extensions provide a wizard component, but you can easily roll your own implementation. Sven > Hican this functionality added to the standard wicket? > actually much of seam popularity came from supporting conversation > scope..., > so i think that adding explicit wicket support will have momentum > i think that having just a store for conversation objects will be a good > begin > then we may add apis like beginConversation, endConversation > ,joinConversation,mergeConversation > ,suspendConversation,resumeConversation > and other concepts like workspace > what do u think? > Joe -- View this message in context: http://www.nabble.com/Conversation-scope-in-wicket-tp24078377p24088943.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
