|
|
15.
|
|
|
In order to benefit from the feedback from any visitor on this web site, everyone can leave a comment on any page of this book. The usability team will review all comments every month and update the book accordingly if required.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:42
|
|
|
16.
|
|
|
The book is written only in English, then `translated by community members`_ into several languages.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:44
|
|
|
17.
|
|
|
In order to check that all OpenERP modules respect the usability guidelines, the check of these guidelines is part of the quality certification process of new modules by OpenERP SA. So, we check that all official modules respect the above guidelines in order to make them become official.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:46
|
|
|
18.
|
|
|
The usability team is also in charge of educating the developer teams. So, when the usability team detects developments which do not conform to these guidelines, they must contact the authors and ask the author of the module to improve his code according to specific guidelines. In this feedback email, the usability team links to each guideline that was infringed.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:48
|
|
|
19.
|
|
|
Having set this process, a full-time team of several developers and functional experts, we expect OpenERP's usability to improve very quickly over time. If you want to propose a new improvement, the easiest way is to `write to the usability mailing list`_ with your suggestion.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:50
|
|
|
20.
|
|
|
If your improvement is validated by the usability team, we will assign a developer and a member of the usability team will improve the guidelines.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/1. Introduction/index.rst:52
|
|
|
21.
|
|
|
Introduction to modules
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Introduction to modules.rst:3
|
|
|
22.
|
|
|
Menus Organization Rules
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:4
|
|
|
23.
|
|
|
All menus have to be suited to one business application. One user has to see all menus linked to his job. He has to be able to make his workflow in one menu only. This is the goal of all the applications. The user should be able to navigate through all his workflow from a single menu to make his work easier, faster and user friendly.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:6
|
|
|
24.
|
|
|
Menus are defined in a certain way to make the work of users easier . So, users can see all the menus he has need of and they have to be in a logical order, to facilitate navigation and use. A salesman doesn't need to see the invoices before he has even made the quotation.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/2. Business Applications/Menus Organization Rules.rst:8
|
