Re: [U2] UI standards
Hi Dawn, At the moment I'm moving to .net /WPF front end using XAML (SB/XA at the back-end). But since I have not paid much attention to GUI (using defaults as necessary) I had not considered much. And I'm afraid the GUI version of some PRC screens were not as pretty as they could have and should have been. So I start digging in to make them prettier for the NEW interface and ... here I arrived at my dilemma. I have been perusing your response and a number of others... all good information, just have to consolidate it into one general standard. Susan Date: Tue, 13 Jul 2010 14:48:33 -0500 From: Dawn Wolthuis dw...@tincat-group.com To: U2 Users List u2-users@listserver.u2ug.org Subject: Re: [U2] UI standards Message-ID: aanlktilkewu6ignmq00lclkm7yytmxcy8susoqzx9...@mail.gmail.com Content-Type: text/plain; charset=ISO-8859-1 What is your target run-time environment? Is it Windows or browsers or a particular browser or Androids or iPhones or ...? --dawn On Tue, Jul 13, 2010 at 2:34 PM, Susan Joslyn sjos...@sjplus.com wrote: An immense amount of good information has come from this thread. Thank you to everyone for sharing your insights. But don't stop there if you have more! ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
An immense amount of good information has come from this thread. Thank you to everyone for sharing your insights. But don't stop there if you have more! ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
What is your target run-time environment? Is it Windows or browsers or a particular browser or Androids or iPhones or ...? --dawn On Tue, Jul 13, 2010 at 2:34 PM, Susan Joslyn sjos...@sjplus.com wrote: An immense amount of good information has come from this thread. Thank you to everyone for sharing your insights. But don't stop there if you have more! ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Dawn M. Wolthuis Take and give some delight today ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
[U2] UI standards
Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
I've seen the custom look feel developed as a way of gaining product differentiation - something 'shinier' for the demos. But for me, when it comes to developing a non-terminal UI on top of unidata for your typical business application, I would always recommend going with the UI guidelines for the target platform. There's nothing worse (imo) than non-standard interfaces - they as often as not look clunky when they're first developed and quickly fall behind as the operating system is updated, as we're seeing now with xp/vista/win7 and to a lesser extent Mac, Linux etc. Ed -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn Sent: 12 July 2010 13:33 To: u2-users@listserver.u2ug.org Subject: [U2] UI standards Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users --- This e-mail and any attachment(s), is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the addressee, dissemination, copying or use of this e-mail or any of its content is prohibited and may be unlawful. If you are not the intended recipient please inform the sender immediately and destroy the e-mail, any attachment(s) and any copies. All liability for viruses is excluded to the fullest extent permitted by law. It is your responsibility to scan or otherwise check this email and any attachment(s). Unless otherwise stated (i) views expressed in this message are those of the individual sender (ii) no contract may be construed by this e-mail. Emails may be monitored and you are taken to consent to this monitoring. Civica Services Limited, Company No. 02374268; Civica UK Limited, Company No. 01628868 Both companies are registered in England and Wales and each has its registered office at 2 Burston Road, Putney, London, SW15 6AR. --- ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
Keep in mind that fancier, is not always better. First you will need to determine what information you need, then look into UI that gather this type of information. If your using a gui interface, using drop down boxes/radio buttons to standardize selections is best and text when least possible. Keeping in mind that switching from keyboard to mouse and back really slows entry down. Funny, how we all hate the green screen entry, but at the same time, writing a UI, esp a GUI to do the same thing as easier/faster as the green screen is very difficult. Just because the UI may be outdated with current looks, doesn't make it obsolete or non-functional. to the OP, why not involve in the users on what they would like, or how they think the current interface could be improved to suit them better. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users- boun...@listserver.u2ug.org] On Behalf Of Edward Brown Sent: Monday, July 12, 2010 9:17 AM To: U2 Users List Subject: Re: [U2] UI standards I've seen the custom look feel developed as a way of gaining product differentiation - something 'shinier' for the demos. But for me, when it comes to developing a non-terminal UI on top of unidata for your typical business application, I would always recommend going with the UI guidelines for the target platform. There's nothing worse (imo) than non-standard interfaces - they as often as not look clunky when they're first developed and quickly fall behind as the operating system is updated, as we're seeing now with xp/vista/win7 and to a lesser extent Mac, Linux etc. Ed -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn Sent: 12 July 2010 13:33 To: u2-users@listserver.u2ug.org Subject: [U2] UI standards Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users --- This e-mail and any attachment(s), is confidential and may be legally privileged. It is intended solely for the addressee. If you are not the addressee, dissemination, copying or use of this e-mail or any of its content is prohibited and may be unlawful. If you are not the intended recipient please inform the sender immediately and destroy the e-mail, any attachment(s) and any copies. All liability for viruses is excluded to the fullest extent permitted by law. It is your responsibility to scan or otherwise check this email and any attachment(s). Unless otherwise stated (i) views expressed in this message are those of the individual sender (ii) no contract may be construed by this e-mail. Emails may be monitored and you are taken to consent to this monitoring. Civica Services Limited, Company No. 02374268; Civica UK Limited, Company No. 01628868 Both companies are registered in England and Wales and each has its registered office at 2 Burston Road, Putney, London, SW15 6AR. --- ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
You are right there are accessibility standard esp for internet resources, but no real de facto set of standards for data entry. I suppose this is partly why UX is such a big topic these days. Remember all user interfaces are designed, whether by the programmer as he goes along or by a designer. Of course much design is bad. We work with designers and ux people to produce wireframes, colour pallets, font rules, workflows etc, which can all form part of the specification for the programmers. I would recommend you look seriously at design and don't be afraid of using artistic designers and user experience professionals, I know in the MV world we have all done entry screens for many years, it does not mean we have been doing them right ! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn Sent: 12 July 2010 13:33 To: u2-users@listserver.u2ug.org Subject: [U2] UI standards Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
If you are writing MS Windows applications this should be on your bookshelf. A bit dated since it was originally written for Win2K but the design strategies are the same. 500+ pages of how to make a Microsoftian interface Shortened Amazon Link: *http://tinyurl.com/34xa395* Symeon Breen wrote: You are right there are accessibility standard esp for internet resources, but no real de facto set of standards for data entry. I suppose this is partly why UX is such a big topic these days. Remember all user interfaces are designed, whether by the programmer as he goes along or by a designer. Of course much design is bad. We work with designers and ux people to produce wireframes, colour pallets, font rules, workflows etc, which can all form part of the specification for the programmers. I would recommend you look seriously at design and don't be afraid of using artistic designers and user experience professionals, I know in the MV world we have all done entry screens for many years, it does not mean we have been doing them right ! -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Susan Joslyn Sent: 12 July 2010 13:33 To: u2-users@listserver.u2ug.org Subject: [U2] UI standards Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Jeff Schasny - Denver, Co, USA jschasny at gmail dot com ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
I have done a lot of reading in this area too, finding some of the best information by googling for HCI (human computer interface) and UX (user experience) sites and blogs. In addition to reading about UI theory, it makes sense to zero in on the particular run-time environment, such as a browser and both read up on best practices and check out what others are doing before doing your own thing any way, perhaps. After all, the good thing about standards is that everyone can have their own ;-) If you haven not read Don't Make Me Think then I highly recommend doing so. It illustrates by it's easy reader interface what it discusses. I've read it twice. We started with an existing vendor framework for MV AJAX, which comes pre-packaged with browser UI components. So, we have been evolving the UI by reaping the low-hanging fruit, then seeing what standards we want to add or change. That means that we have some things I would not have put in there from the start (such as some validation alerts, instead of perhaps happier approaches), that we have simply used out of the box and not yet tailored for our needs. I tend toward Keep it Simple, but the simple I want is that it be simple for the user and also, frankly, for maintainability over time. It is rarely simplest for us to do what is simplest for the user. It definitely takes work to make the user interface simple. For each decision there is now a ton of information, as you have found. While tackling some of it up front, many decisions arise during specific design tasks later in the development. It is counter-productive to do all such research and decision-making up front (the BDUF approach). EXAMPLE We started with field labels above the data entry field (to the left is the other common option, with inside the field being another new fangled approach), using short upper-cased words. I had researched enough to select the positioning of our labels when starting out, not the wording. When I got to the point of looking at how to write the labels, such as Last Name or Last name or What is your last name? or Your last name [not to mention choosing last name over family name or surname, another issue], I read that there was an ISO standard of sentence casing for field labels. Who knew? For what it's worth, we decided on sentence casing our labels, so in our alpha delivery of our software, the label is written as Last name instead of Last Name. --dawn On Mon, Jul 12, 2010 at 7:33 AM, Susan Joslyn sjos...@sjplus.com wrote: Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Dawn M. Wolthuis Take and give some delight today ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
Sorry for not proof-reading before sending. The possessive ' in its alone is torturous. smiles. --dawn On Mon, Jul 12, 2010 at 8:44 AM, Dawn Wolthuis dw...@tincat-group.comwrote: I have done a lot of reading in this area too, finding some of the best information by googling for HCI (human computer interface) and UX (user experience) sites and blogs. In addition to reading about UI theory, it makes sense to zero in on the particular run-time environment, such as a browser and both read up on best practices and check out what others are doing before doing your own thing any way, perhaps. After all, the good thing about standards is that everyone can have their own ;-) If you haven not read Don't Make Me Think then I highly recommend doing so. It illustrates by it's easy reader interface what it discusses. I've read it twice. We started with an existing vendor framework for MV AJAX, which comes pre-packaged with browser UI components. So, we have been evolving the UI by reaping the low-hanging fruit, then seeing what standards we want to add or change. That means that we have some things I would not have put in there from the start (such as some validation alerts, instead of perhaps happier approaches), that we have simply used out of the box and not yet tailored for our needs. I tend toward Keep it Simple, but the simple I want is that it be simple for the user and also, frankly, for maintainability over time. It is rarely simplest for us to do what is simplest for the user. It definitely takes work to make the user interface simple. For each decision there is now a ton of information, as you have found. While tackling some of it up front, many decisions arise during specific design tasks later in the development. It is counter-productive to do all such research and decision-making up front (the BDUF approach). EXAMPLE We started with field labels above the data entry field (to the left is the other common option, with inside the field being another new fangled approach), using short upper-cased words. I had researched enough to select the positioning of our labels when starting out, not the wording. When I got to the point of looking at how to write the labels, such as Last Name or Last name or What is your last name? or Your last name [not to mention choosing last name over family name or surname, another issue], I read that there was an ISO standard of sentence casing for field labels. Who knew? For what it's worth, we decided on sentence casing our labels, so in our alpha delivery of our software, the label is written as Last name instead of Last Name. --dawn On Mon, Jul 12, 2010 at 7:33 AM, Susan Joslyn sjos...@sjplus.com wrote: Good morning. In developing a new user interface - how have you folks established standards? When I google around I find an immense amount of information. Accessibility standards. Industry standards. And many games and applications have published their standards - how to make your software look like theirs so your users are already familiar. I don't see as many published standards regarding data entry screens. (But I am still plowing through thousands of search results!) Still many of these standards are personal choice. Or in some cases far to the opposite extreme - you can find psychological studies about what colors to use, for example. If you set standards on a previous interface and now move to another - how much do you want to stick to your standards for consistency and compatibility and how much do you want to break out and show-off that this is, after all, a new interface? Obviously there are technical limitations - with the new stuff, always. But what about design decisions you made based on previous limitations - and now those limitations are lifted!? How crazy do you go? What do users really want? (Now there is something to ponder!) Any thoughts, ideas, references and discussion on this topic from anyone? Susan ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users -- Dawn M. Wolthuis Take and give some delight today -- Dawn M. Wolthuis Take and give some delight today ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
As far as UI standards for data entry applications are concerned, I recommend Microsoft's User Experience Guidelines as a starting point. Google msdn windows 7 user experience guidelines, navigate to the MSDN page, find the PDF link and download the document. Most business people use Microsoft products daily. If your application follows the same basic layouts and uses the same keyboard shortcuts, your users will quickly learn your application; as a bonus, your application will teach them how to use their MS products. However, if your application works contrary to MS products, or requires them to memorize a different command set, then they'll despise you and your product. Have your developers read the book GUI Bloopers to avoid stupid GUI layouts. Also User Interface Design for Programmers is helpful. http://www.joelonsoftware.com/uibook/fog000249.html When is it okay to break out and show off a new interface? When it matches the user's imaginary model, not the developers! Finally, desktop and web applications are starting to blur into one another, so it's okay to borrow practices and standards from one and implement them in the other. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
On 12/07/10 14:26, George Gallen wrote: Keep in mind that fancier, is not always better. First you will need to determine what information you need, then look into UI that gather this type of information. Might not be easy having both, but can you keep both green screen and gui? Gui is great for people who only use the app occasionally, but if it's going to be used all day every day, green screen (despite being seen as old fashioned) is usually a lot easier. If your using a gui interface, using drop down boxes/radio buttons to standardize selections is best and text when least possible. Keeping in mind that switching from keyboard to mouse and back really slows entry down. But selecting an entry from a LOT of choices is very slow in a drop-down ... try and give the user the option of using the mouse or keyboard to select - oh and let them type in a string, don't assume that every character they type is the FIRST character :-( if you've got a thousand possible choices, letting the user type the first character still gives them 40 to choose from, which is too many for comfort. Funny, how we all hate the green screen entry, but at the same time, writing a UI, esp a GUI to do the same thing as easier/faster as the green screen is very difficult. Just because the UI may be outdated with current looks, doesn't make it obsolete or non-functional. to the OP, why not involve in the users on what they would like, or how they think the current interface could be improved to suit them better. Oh - and don't copy a database I've just been using ... I tried to enter a Brownie on the national database, and ended up having to enter them three times before it would let me proceed. Firstly it demanded information I didn't have (so I faked it :-) but I missed something so it rejected it with an error. So I went back to try again, fixed the error, and discovered that it had thrown away all the information that WASN'T in error. So third attempt, I finally managed to get it right and persuade the database to accept it. (Doesn't help that one of the senior people in charge of the database is my wife's Guiding boss, and as a professional I don't think very much of how well the database has been done :-( My wife doesn't like me moaning but I hear other guiders cursing the database too ...) Cheers, Wol ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
There are a ton of web pages on UX but it really pays to spend some time in different bookstores, where you'll find material that you don't see online. I've read a lot of books on creating good user interfaces, which may fly in the face of standards. And conversely to all of this, a lot of material on good design and standards is just pure rubbish. Take in a lot of info and come to your own conclusions. Consistency is always key as well, whether or not you're following someone else's standards, just follow your own. Put common functionality in consistent places. For example, do your best to put page/form-level buttons in the same place on every page, and then try to be consistent about where you put page-unique buttons. Save/Cancel/Delete should never be so close that the user can confuse them, or too far apart. ;) And use CSS (or similar mechanisms) as much as possible to control images, colors, and text styles. Change the image for Save buttons in one place and the entire application is morphed. Related: I optionally allow the admin or individual users to change the color scheme and lots of other visual aspects for the entire application with a single selection. The standard here is where screens are, not what they look like. That said, many of us are familiar with web parts (like at iGoogle.com) where users can move around sections of their screens. Part of your standard may be recognizing that you can't make everyone happy when you're designing your forms, so at least give people the tools they need to re-arrange page segments to suit their own style. This actually makes coding a lot easier because you can focus on functionality rather than fine-tuning the placement of components. Use the right controls for things like grids, dropdown lists, radio buttons, and checkboxes. Each has their place. For example: Yes/No should not be two separate checkboxes and should not be in a dropdown list. Also (for VARs), be prepared to change controls depending on where you deploy your software. This isn't easy and might be too much work for most VARs. When you create software for many companies you may not know how many records they have have in their tables. You might design a table to have a dropdown list for one client because they only have, say, 10 regions. But that's not appropriate when you sell to a company where every county (thousands) is a different region. That brings me to my last point: Try to create stand-alone controls which perform specific duties: The customer selector, the invoice display, the printer selector, etc. Not only does this create consistency (on-topic with Standards) but it allows you to maintain such code in one place for the entire application. The first time you realize that you need to change the same screen in two places, you will recognize the benefit of using controls. This falls into the category of object-oriented development, code-reuse, refactoring, etc. HTH Tony Gravagno Nebula Research and Development TG@ remove.pleaseNebula-RnD.com Nebula RD sells mv.NET and other Pick/MultiValue products worldwide, and provides related development services remove.pleaseNebula-RnD.com/blog (latest blogs on Web Services) Visit PickWiki.com! Contribute! http://Twitter.com/TonyGravagno ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
From:Rex Gozar Have your developers read the book GUI Bloopers to avoid stupid GUI layouts. That reminds me: http://webpagesthatsuck.com/ They constantly have new material over many years - you'd think people would learn. It's worth it to spend a lot of time there. Finally, desktop and web applications are starting to blur into one another, so it's okay to borrow practices and standards from one and implement them in the other. Agreed. For the last couple years I don't think I've been treating these much differently, to a point with some browser apps of adding a menubar with File, Edit, Tools, and Help, sometimes even toolbar buttons. Better tools are constantly evolving to make all of this easier. The concept of RIA can be summarized as reproducing the desktop experience in a browser, while being mindful of the limitations. T ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
Re: [U2] UI standards
Even though I tend not to agree with everything Mr Spolsky writes, I'll second his book User Interface Design for Programmers. The interesting thing about Microsoft's User Experience Guidelines is that MS doesn't follow them in their own office software, although, I wouldn't say following them is a bad idea. -Original Message- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Rex Gozar Sent: Tuesday, July 13, 2010 4:38 AM To: U2 Users List Subject: Re: [U2] UI standards As far as UI standards for data entry applications are concerned, I recommend Microsoft's User Experience Guidelines as a starting point. Google msdn windows 7 user experience guidelines, navigate to the MSDN page, find the PDF link and download the document. Most business people use Microsoft products daily. If your application follows the same basic layouts and uses the same keyboard shortcuts, your users will quickly learn your application; as a bonus, your application will teach them how to use their MS products. However, if your application works contrary to MS products, or requires them to memorize a different command set, then they'll despise you and your product. Have your developers read the book GUI Bloopers to avoid stupid GUI layouts. Also User Interface Design for Programmers is helpful. http://www.joelonsoftware.com/uibook/fog000249.html When is it okay to break out and show off a new interface? When it matches the user's imaginary model, not the developers! Finally, desktop and web applications are starting to blur into one another, so it's okay to borrow practices and standards from one and implement them in the other. ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ ### The information transmitted in this message and attachments (if any) is intended only for the person or entity to which it is addressed. The message may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. The intended recipient of this e-mail may only use, reproduce, disclose or distribute the information contained in this e-mail and any attached files with the permission of IMB. ### ___ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
