← Back to team overview

openerp-expert-ergonomy team mailing list archive

Re: Guide lines



I think you are right, it is important to unify the layout of views. I think too it could be a big point of guide lines because it concerns fields in form view but also, buttons in search views, layout in reports, some terminology and some functionalities.

If you have more precise examples or other things which should be unified, feel free to add what you think about this point.
Thanks for your contribution.


Borja López Soilán (Pexego) a écrit :
The guide looks great, good job! :D

Now, I think you should take a look at the "unified layout of forms" discussions that took place on April on the Accounting Experts mailing list, and maybe add some of the ideas discussed there to the guide:

    * Similar documents should have similar interface:

      If document A has a field F, and document B has also an F field,
      that field should be on the same place on the form (being inside
      the a notebook page with the same title on both, being at the
      top/right/left/bottom on both, having the same colspan, using
      the same name/translation...) unless there is a good reason not
      to do so.

      This makes the interface easier to learn: Once you master the
      sales form, you should be like a fish in the water with the
      purchases form (on the 5.0 this is not true

    * Long names / address fields should have colspan 4, or be at
      least longer than normal fields, so the user can read the full
      address/name easily on small screens.

    * Functionality should be consistent between similar documents:

      For example sale orders have "payment terms" (so the user can
      preset the payment terms that should be used when invoicing);
      purchase orders do not/*/, why?: To me this is not only a
      functionality problem but also an usability problem: The user
      would expect to be able to preset the payment terms on the
      purchases just as he does on the sales, he will be disappointed
      when he notices that there is not such option.
      /(* we just added a "purchase_payment" module to the
      extra-addons that adds payment info to purchase orders; but I
      think that the sale&purchase modules should be consistent in
      basic functionality)./

Aline Preillon wrote:

I have published one guide line on my blog (http://useability-openerp.blogspot.com/2010/07/guide-lines.html). In next weeks, I will publish many guide lines.

The current goal of the usability team is simplify the use of the software. Therefore, we are interested in your ideas regarding this goal.


Aline Preillon

Borja López Soilán

Pexego Sistemas Informáticos S.L.
Avenida de Magoi 66 - 27002 Lugo (España)
Tel./Fax 982801517

Este mensaje se dirige exclusivamente a su destinatario y puede contener información privilegiada o confidencial. Si no es usted el destinatario indicado, queda informado de que la utilización, divulgación y/o copia sin autorización está prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.


Aline Preillon
Quality Officer

OpenERP s.a.
Chaussée de Namur, 40
B-1367 Grand-Rosière
Tel: +

Product-Web: http://www.openerp.com <http://www.openerp.com/>
On Demand-Web: http://ondemand.openerp.com <http://ondemand.openerp.com/>