trunk - administration modules - buttons must be exclusive

Bug #599564 reported by Ferdinand
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo GTK Client (MOVED TO GITHUB)
Won't Fix
Wishlist
Unassigned
Odoo Server (MOVED TO GITHUB)
Confirmed
Wishlist
OpenERP's Framework R&D

Bug Description

IMHO the 3 buttons (installed,uninstalled,to be upgraded) must be "exclusive" - i.e. pressing on must unselect the 2 others.

pressing installed and uninstalled at the same time does not make sense.

now one could argue " administrators should know what they are doing" - but this is not the point - similar will happen in other forms

BTW on my KDE 4.4.4 based notebook active inactive and current buttons are almost not to distinguish - we need different styles (colors/shapes) for this

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hi,

I have little argue that similar case is there for states in many forms.

I vote for current scenario is ok.

Thanks.

Revision history for this message
Ferdinand (office-chricar) wrote :

@Jay
I am not sure to understand your argument correctly

Try Customer/Supplier Invoices
it should not be possible to press Buttons "Draft", "Proforma" and "Invoices" (whatever does this select? Should it read "Open" ?)
simultaneously or do I miss something?

Can a draft invoice be (un)paid ?

(I am on addons revision 4171)

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hi ,

I am saying the same thing that,it could happen in many forms where states have been appearing as buttons.

User will get choices to press buttons,but that does not mean he presses all them together,which really does not make sense.

Thanks.

Revision history for this message
Ferdinand (office-chricar) wrote :

Ok but what I am saying - is that users will press the exclusive buttons together and report errors because the system does not behave as expected

IMHO we should be able to create a group of buttons which are exclusive and the system guaranties the exclusiveness. similar to radio buttons used widely.
see http://en.wikipedia.org/wiki/Radio_button

I would consider only radio button functionality as user friendly and would assume that this can be found in the usability guidelines
It's missing here
http://doc.openerp.com/contribute/15_guidelines/

IIRC Aline Preillon "Responsible for the useability of OpenERP" posted a link to Apple HIC Guidline somewhere I can't find now which should be relevant for this question

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

My vote goes with you.

Revision history for this message
Carlos Liebana (carlos-liebana) wrote :

Mmm, I think I don't understand well.. Following your example for invoices, how can the user press simultaneously "Draft", "Pro-Forma" and "Invoices"?

Revision history for this message
Aline (OpenERP) (apr-tinyerp) wrote :

I consider your post, I think too that some buttons of some groups should be exclusive. But this is not planned for RC of V6. But we can consider for next version (v6.1 or 7)

@Ferdinand : I have not posted a link "Apple HIC Guidline". I have posted a preview of guide line manual on my blog http://useability-openerp.blogspot.com/ I tried send you a mail about this but I can't, when I send you a mail, i receive directly a undelivered message.message.

Changed in openobject-client:
importance: Undecided → Wishlist
status: New → Triaged
Revision history for this message
Ferdinand (office-chricar) wrote :

@Carlos
because it is possible ....

tfr (Openerp) (tfr)
Changed in openobject-addons:
importance: Undecided → Wishlist
qdp (OpenERP) (qdp)
Changed in openobject-addons:
assignee: nobody → OpenERP's Framework R&D (openerp-dev-framework)
Revision history for this message
tfr (Openerp) (tfr) wrote :

==> next release

Changed in openobject-client:
status: Triaged → Won't Fix
Changed in openobject-addons:
status: New → Confirmed
affects: openobject-addons → openobject-server
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.