|
97.
|
|
|
(Product)
|
|
|
|
(产品)
|
|
Translated and reviewed by
Victor Yu
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/menus.rst:30
|
|
98.
|
|
|
Reporting
|
|
|
|
报表
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
94e1d268b66946cd948f5581e0c3d097
32388d75dd2c451493eb5a55e3dc161b
|
|
Located in
../../source/usability_book/5.Reporting/index.rst:4
../../source/usability_book/7.Guidelines/menus.rst:31
|
|
99.
|
|
|
Menu terminology
|
|
|
|
菜单用词
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
56501894b6bc4d22887d1b24fc31d543
|
|
Located in
../../source/usability_book/7.Guidelines/menus.rst:35
|
|
100.
|
|
|
The name must be short and explicit. Firstly, it must be short because in web client, main menus are organized on the top, in a horizontal bar. So it cannot take too much space. For instance we use “Purchases”, not “Purchases Management”, to minimise the space taken in the menu.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/usability_book/Guidelines/menus.rst:37
|
|
101.
|
|
|
Secondly, used terminology must be linked to the application and explicit to it. For example, res.partner object is named “Customer” in “sales” and “Supplier” in “Purchase”.
|
|
|
|
其次,使用的术语必须与应用模块相联系,且明确用于该应用。例如,“res.partner”对象在“销售”模块中叫做“客户”,而在“采购”模块中称为“供应商”。
|
|
Translated and reviewed by
Victor Yu
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/menus.rst:42
|
|
102.
|
|
|
Search Views
|
|
|
|
搜索视图 (注:OE7搜索视图巨变,此章暂且不译)
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
76040057d9e0458b9198dde94fbd231a
a6ff6447f8804eb5af9cb4fa735e4600
|
|
Located in
../../source/usability_book/3. OpenERP's Views/Search Views.rst:4
../../source/usability_book/7.Guidelines/searchviews.rst:3
|
|
103.
|
|
|
How organize a search view
|
|
|
|
如何设计一个搜索试图
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
6f9f53fa00464c4cab18ef4f0329aee4
|
|
Located in
../../source/usability_book/7.Guidelines/searchviews.rst:6
|
|
104.
|
|
|
Filtering buttons and main filter fields must be the first elements on top of the view, and on the same line. Below this main filter option, you must place extended filters and group by one above the other. Each field group must be placed in a new line. Finally, the search bar must be below the view as displayed in the picture above.
|
|
|
|
过滤按钮和主要的过滤字段应该在视图的顶部,并且在同一行内。在该主要过滤器的下方,必须放置扩展过滤器,每个分为一组依次排列。每个分组字段必须放在一个新行内。最后,搜索条必须要像上图中显示的视图中位置一样。
|
|
Translated and reviewed by
Victor Yu
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/searchviews.rst:12
|
|
105.
|
|
|
Use a business oriented terminology
|
|
|
|
使用业务相关的术语
|
|
Translated by
Xavier (Open ERP)
|
|
|
|
|
9447b2b10389424aa2467ffb460915cd
|
|
Located in
../../source/usability_book/7.Guidelines/searchviews.rst:16
|
|
106.
|
|
|
As previously mentioned, the used terminology must be adapted to the application. An example of this would be, in sale order the search field “partner_id” is named “Customer” and in purchase application, the same search field is named “Supplier”. In the same way, the “user_id” field in sales is named “Salesman” and in project management, it is named “Project Manager”.
|
|
|
|
像前面提到的一样,使用的术语必须和应用相匹配。举个例子,在销售订单的搜索字段"partner_id"命名为“客户”,而在采购应用里,同样的搜索字段被称为“供应商”。同样的,字段"user_id"在销售中叫“销售员”,而在项目管理中称为“项目经理”。
|
|
Translated and reviewed by
Victor Yu
|
|
|
|
Located in
../../source/usability_book/7.Guidelines/searchviews.rst:18
|