Yep, it is me again. Third email in two hours. I finished about 80% of code and about 40% of docs (tutorials + javadocs) for Struts Dialogs project. It is not finalized yet, but is taking shape. Thus, I want to test waters to include dialog functionality into Struts core, preferably into 1.3.
First, live demos. * the main demo page: http://www.superinterface.com/strutsdialog which contains some noteworthy samples, like: * Login web control, which has two states: "not logged in" and "logged in" and two corresponding pages: http://www.superinterface.com/strutsdialog/dialogloginactioncontrol.do * Master JSP page containing child web control: http://www.superinterface.com/strutsdialog/embeddedmasterpage-tomcat.do The login/userinfo cell in the top-left is the same web control as in prior example, it differs only in page design and in View location. Note, that you submit login info into a separate action, not into one which is displayed in the address bar. * Wizard: http://www.superinterface.com/strutsdialog/wizardaction.do You probably saw it before, but now it is nicely integrated into Struts Dialogs. I would like you guys to check out the live examples and to consider the feasibility of including this stuff (possibly, with changes and updates) into Struts core. The reason is that Struts is a controller framework. Check the packages: actions, taglibs, tiles and validator. The latter two pachages are not used by every Struts user. Taglibs? Aren't they obsolete, now when JSTL is available? So, average Struts developer is left with actions and config. All other frameworks, even Spring, which is not very strong in UI, have UI layer. Many of them have business/persistence integration layer and other good stuff. I think that adding some UI classes into Struts would be a good thing. Classes that I developed, pick up where DispatchAction left, and move on almost to JSF-like integration with business objects and with server-side viewstate, but without JSF tags. Currently the following actions are available: * SelectAction - improved DispatchAction, works with pushbuttons and image buttons. * DialogAction - implements two-phase input processing aka Post-redirect-Get. Manages error messages, allows to reload pages without implicit resubmit. * CRUDAction - all CRUD operations in one action and one interface. * WizardAction - allows to create robust web wizards Also, as you might see from master/child example, it is very easy to create a componentized page with child controls, and you don't even need Porlet API for it! Granted, this component application would not have extensive API, but is it really needed? In most cases all one needs is to drop control onto page and to have it rendered when page is rendered. Data exchange is possible through session object. Project homepage (not classes are described yet): http://struts.sourceforge.net/strutsdialogs/index.html I want to initiate some traction, while I am finishing with documentation and with final touches on the code. Hoping for positive replies ;-) Michael. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
