SelectAction is really old news and is what all the apps that use multiple select image buttons do only with a lot less bloating of the code See http://www.michaelmcgrady.com/button/
On 6/7/05, Michael Jouravlev <[EMAIL PROTECTED]> wrote: > Struts Dialogs is an extension of Struts actions that provides an > improved user experience along with event-based programming model. > > Struts Dialogs currently consists of two action classes: SelectAction > and DialogAction. > > ------------ > SelectAction > ------------ > > SelectAction is an abstract Action that dispatches an HTTP form > submission event to a handler method. > > The purpose of this class is processing submission of HTML forms. > Unlike DispatchAction and LookupDispatchAction, which correlate value > attribute of submit form element with handler method, SelectAction > uses name attribute. This allows to display a user-friendly caption on > a submit button. Also, it is possible to change button caption without > rebuilding the application. > > ------------ > DialogAction > ------------ > > DialogAction is an abstract Action that provides basic dialog > functions, like accepting input data, dispatching submit event to a > method, generating error messages and rendering a view. DialogAction > allows to create robust user inteface and provides simple event-based > programming model. > > DialogAction incorporates several innovative design decisions not > previously used in Struts. Some of them are already implemented in > other frameworks, like Ruby on Rails or JSF. Other features are unique > to DialogAction. > > The cornerstone concept of DialogAction is separation of input and > output processes. This solves several issues, related to HTML form > input, like double submit problem, annoying POSTDATA messages, bad > usability when Reload, Back and Forward buttons are used. > > DialogAction defines three different modes of operation: > > * action initialization prepares action for use with new set of data; > * user input process accepts input data, updates domain model, > generates error messages; > * view rendering process generates a result page. > > Separation of input and output improves usability and user experience: > > * Any page can be reloaded without resending input information to > the server. > * As a consequence, an application does not have to cope with > double submits. > * Another consequence is that a user does not see "Do you want to > resend POSTDATA?" message. > * Using Back and Forward buttons is safe, because only result > pages are browsed. > > ------------------------- > Documents, files, samples > ------------------------- > > Online samples: > http://www.superinterface.com/strutsdialog > > Documentataion: > http://wiki.java.net/bin/view/Projects/StrutsDialogs > If you cannot see pictures on SelectAction and DialogAction pages, > you might need to register and login to java.net. But it should > work without logging in. > > Source code for DialogAction and amples is located at: > Folder: > > https://easywizard.dev.java.net/servlets/ProjectDocumentList?folderID=3494&expandFolder=3494&folderID=3494 > File name: > strutsdialog.zip > > Michael Jouravlev. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "You can lead a horse to water but you cannot make it float on its back." ~Dakota Jack~ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
