[Design of JBoss Portal] - Re: First pass UI improvements
by cdelashmutt
anonymous wrote : I am not trying to belittle your work. This is much appreciated in particular with respect to finding out all the different inconsistencies in the GUI.
Thank you. Without your personal dedication, and the dedication of the entire team, we wouldn't even have a Portal 2.6 UI to improve! :)
anonymous wrote : However, our usability problems are not going to go away with just that.
I agree completely. I think the issue is that there are things that need to be done for Portal 2.6 to release with a UI that is consistent and understandable.
I believe there is a much larger body of work that needs to be done to revamp the UI in a fundamental way, as you seem to agree with as well. This larger set of work is something that should probably happen in a post 2.6 release or we will be holding back some important features. This may mean re-work and possibly duplication of effort. But I would argue that refinement and alternate implementations are good things.
anonymous wrote : ...icons are not an end in themselves...
Absolutely true! The end is that a person should be able to implicitly understand what the UI is offering for them to do. This can be done with icons, text, or any number of UI tools. :) I think we agree on this point as well.
Which do we think would be better in terms of usabilty? The icons or a drop down list similar to the CMS actions?
I'm personally beginning to lean more towards the CMS-like drop downs for actions with a "Go" button...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047302#4047302
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047302
18 years, 7 months
[Design of JBoss Portal] - Re: First pass UI improvements
by chris.laprun@jboss.com
"cdelashmutt" wrote : Am I an authority in usability? By no means. Can I quote leading usability experts as to the validity of my suggestions? Nope.
|
| I'm simply approaching this from the perspective of a user trying to understand and use the portal, which is all that I really can do. ;)
I am not trying to belittle your work. This is much appreciated in particular with respect to finding out all the different inconsistencies in the GUI. However, our usability problems are not going to go away with just that. People have started to work on the issues you've identified and some of their fixes result in new inconsistency. I'm trying to make sure we get the proper help from someone who really knows about this stuff to provide solutions to the problems you identified so that we don't end up in an lengthy loop of modifications that could very well end up in not improving the GUI that much.
"cdelashmutt" wrote : In reference to the icons suggestion, I have a couple of reasons for suggesting them. First off, the text links seem to run together even with the pipe separators. One has to stop/think/interpret the text to understand which action they may want to take. People respond better to icons, or even text that looks more like an icon (buttons with adequate padding, etc). We could consider having icons with text next to them, similar to toolbar buttons, or for consistency's sake we could use a dropdown list and a "Go" button similar to the way CMS does it's functions if no one likes the icon idea.
People might respond better to icons, I don't know. What I know is that if they do, they will probably if the icons are well designed and meaningful and this is something that is extremely hard to do. Plus, icons are not an end in themselves. In particular, even if we do end up using icons/colors/whatever, we need to make sure that whatever information we convey degrades properly and that's another hard task that we, developers, are not fit for. Not that we're not interested about it (I know I am) or that we couldn't learn about it. We simply don't have time considering that we're also supposed to add features, improve performance and fix bugs...
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047296#4047296
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047296
18 years, 7 months
[Design of JBoss Portal] - Re: First pass UI improvements
by cdelashmutt
Am I an authority in usability? By no means. Can I quote leading usability experts as to the validity of my suggestions? Nope.
I'm simply approaching this from the perspective of a user trying to understand and use the portal, which is all that I really can do. ;)
In reference to the icons suggestion, I have a couple of reasons for suggesting them. First off, the text links seem to run together even with the pipe separators. One has to stop/think/interpret the text to understand which action they may want to take. People respond better to icons, or even text that looks more like an icon (buttons with adequate padding, etc). We could consider having icons with text next to them, similar to toolbar buttons, or for consistency's sake we could use a dropdown list and a "Go" button similar to the way CMS does it's functions if no one likes the icon idea.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047287#4047287
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047287
18 years, 7 months
[Design of JBoss Portal] - Re: First pass UI improvements
by chris.laprun@jboss.com
The so-called first pass is creating its own set of problems... Looking over the commits I already see different solutions implemented for the same problems. This first pass is not going to address the consistency issue that we have and it's not going to be addressed until we have some sort of template. James Cobb offered his team help, let's take him at his word and ask them (again) for a template.
This template will have to have minimally:
- A global page structure taking into account the fact that this is a portlet template.
- Sections and titles.
- A proper use of portlet CSS classes (as defined by JSR-168 and WSRP).
- An example of how to display a page-wide error (i.e. errors that don't affect a particular UI element).
- A table-less, CSS-based, semantically-correct complex form (i.e. form with embedded forms, see the WSRP display of registration properties for an example of why we would need that) with several buttons.
- Examples of how to display errors specific to a given UI element.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4047282#4047282
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4047282
18 years, 7 months