diff options
| author | J Bradshaw <jbradsha@users.noreply.github.com> | 2015-05-23 20:28:22 +0100 |
|---|---|---|
| committer | Xavier Morel <xmo@odoo.com> | 2015-07-07 12:09:21 +0200 |
| commit | 2f7ab001e209fa54260bbc1dd008b9fa0e17baad (patch) | |
| tree | d8ab5ffe63478450fdd9ee3af97ea4cc3b40b522 /doc/reference/views.rst | |
| parent | 95e56a109d5abc97ab7db1ee1c9b9efb66a7e362 (diff) | |
[IMP] doc: grammar and readability
Backport of most of #6827 by J Bradshaw with additional
modifications (and some reverts) during review.
closes #6827
Diffstat (limited to 'doc/reference/views.rst')
| -rw-r--r-- | doc/reference/views.rst | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/reference/views.rst b/doc/reference/views.rst index 6670ac05c33..b1cc0255520 100644 --- a/doc/reference/views.rst +++ b/doc/reference/views.rst @@ -13,7 +13,7 @@ Common Structure ================ View objects expose a number of fields, they are optional unless specified -otherwise) +otherwise. ``name`` (mandatory) only useful as a mnemonic/description of the view when looking for one in @@ -22,7 +22,7 @@ otherwise) the model linked to the view, if applicable (it doesn't for QWeb views) ``priority`` client programs can request views by ``id``, or by ``(model, type)``. For - the latter, all the views for the right type and model will be looked for, + the latter, all the views for the right type and model will be searched, and the one with the lowest ``priority`` number will be returned (it is the "default view"). @@ -147,7 +147,7 @@ root can have the following attributes: Defined as a mapping of colors to Python expressions. Values are of the form: :samp:`{color}:{expr}[;...]`. For each record, pairs are tested - in-order, the expression is evaluated for the record and if ``true`` the + in order, the expression is evaluated for the record and if ``true`` the corresponding color is applied to the row. If no color matches, uses the default text color (black). @@ -572,7 +572,7 @@ Button Box .......... Many relevant actions or links can be displayed in the form. For example, in -Opportunity form, the actions "Schedule a Call" and "Schedule a Meeting" take +Opportunity form, the actions "Schedule a Call" and "Schedule a Meeting" have an important place in the use of the CRM. Instead of placing them in the "More" menu, put them directly in the sheet as buttons (on the top right) to make them more visible and more easily accessible. |