summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Watkins <daniel@daniel-watkins.co.uk>2011-04-14 22:36:11 +0100
committerDaniel Watkins <daniel@daniel-watkins.co.uk>2011-04-14 22:36:11 +0100
commitfcfa8feb192a0979bc515483f645fe04bef7102d (patch)
tree0fbb17ac1152ea5a2bddb585c017b352192421da
parent8ed08b8d6fed3beccc7e7ef77acefe5268f4de13 (diff)
Consistent reference to methods.
bzr revid: daniel@daniel-watkins.co.uk-20110414213611-e7duvzsd65ygxp9o
-rw-r--r--doc/source/development.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/source/development.rst b/doc/source/development.rst
index 719c6baa74a..07ee7dabf64 100644
--- a/doc/source/development.rst
+++ b/doc/source/development.rst
@@ -137,7 +137,7 @@ Life cycle
The search view has a pretty simple and linear life cycle, in three main steps:
-:js:class:`init <openerp.base.SearchView>`
+:js:class:`~openerp.base.SearchView.init`
Nothing interesting happens here
@@ -232,7 +232,8 @@ abstract types, used to implement input widgets:
<views-search-registration>`.
If inherited from, descendant classes should not call its
- implementations of ``get_context`` and ``get_domain``.
+ implementations of :js:func:`~openerp.base.search.Input.get_context`
+ and :js:func:`~openerp.base.search.Input.get_domain`.
* :js:class:`openerp.base.search.Field` is used to implement more
"field" widgets (which allow the user to input potentially complex