Howdy, Depends on how much time you have on your hands ;) Right now the system seems simple enough that you can code one page to handle all three operations. However, to be more general and easier to maintain or expand in the future, I'd suggest separating page by action. One page for store, one for delete, one for change. Maybe with some sort of central controller to route requests to the appropriate page. Struts does this very nicely...
Yoav Shapira Millennium ChemInformatics >-----Original Message----- >From: Jose Euclides da Silva Junior - DATAPREVRJ >[mailto:[EMAIL PROTECTED]] >Sent: Tuesday, February 18, 2003 1:39 PM >To: Tomcat Users List >Subject: (off-topic) Best Practices - GUI > >Hi everybody, >i have a litle system, which just need to deal with technical hints >storage. >So, an user can store, delete or change a hint. The hint's STORE form has a >hint title field, a multipart form data and a key-word text field. Should i >use this same form to give the users the others options ( setting 2 >buttons) >- delete and change - , or not? >Regards, >Euclides. > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
