Very well said. The point about making changes to the forms without having to disturb the underlying (and who cares what they look like) forms that hold the data is one of the biggest plusses in this design's favor.
I started doing all my custom work this way and will not go back. John's comment: I think most ARS apps are concerned with functionality -- not with usability -- I think that is the wrong approach... ...is 100% on target, in my book. Too many Remedy apps have that homegrown "well, it works..." look and feel to them. By using the display-only form design method, you can largely cut away from that and make apps look and behave much more like modern apps. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of John Sundberg Sent: Thursday, November 08, 2007 2:26 PM To: [email protected] Subject: Re: Using regular forms for data storage ONLY? ** I do not think your statement proves or disproves your craziness. However, I think display-only forms front-ending real forms is a great design pattern. You have more control over the end user experience -- you NEVER let the user do a 1=1 query -- you are closer to a MVC design pattern -- you could have 2 separate versions of workflow running simultaneously (if your datamodel does not change) (I think this is a significant benefit -- that way you can do controlled upgrades -- currently ARS App upgrades are all/nothing all at once) If you have massive systems - it is pretty hard to coord a big switchover. Also - by separating model from view more clearly -- I think you give more attention to the user-experience (which should not be ignored) (I think most ARS apps are concerned with functionality -- not with usability -- I think that is the wrong approach) I think the default options of being able to open a search or open a new -- are no longer relevant for the apps that are being built. When ARS was young -- users were nearly working directly with the data - it just happened to have filters and active links that might get in the way and do stuff in addition to what you typed. Now -- real applications are being built on ARS -- and that rawness is no longer in vogue. I think it makes it easier to upgrade (in terms of an application -- this is what Kinetic Survey does). (wow - twice I said this in one day) Basically - your raw data forms stay put. You drop all the display only forms -- reload all the 'new' display only forms -- and you are upgraded. (OK - that was way simplified - but you get the idea) Craziness - still up for debate! -John On 11/8/07, Durrant, Michael M. - ITSD <[EMAIL PROTECTED]> wrote: ** I'm toying with the idea of using regular forms for data storage only and using display forms for all user interactions. while I realize this entails more "coding", I think I would have a greater deal of control over behavior of the user interface. Has anyone tried this already? Am I crazy for even thinking about it? Thanks, Michael Durrant The information contained in this email may be privileged, confidential or otherwise protected from disclosure. All persons are advised that they may face penalties under state and federal law for sharing this information with unauthorized individuals. If you received this email in error, please reply to the sender that you have received this information in error. Also, please delete this email after replying to the sender. __20060125_______________________This posting was submitted with HTML in it___ -- John David Sundberg 235 East 6th Street, Suite 400B St. Paul, MN 55101 (651) 556-0930-work (651) 247-6766-cell (651) 695-8577-fax [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
