diff options
| author | Antony Lesuisse <al@openerp.com> | 2012-10-06 19:10:53 +0200 |
|---|---|---|
| committer | Antony Lesuisse <al@openerp.com> | 2012-10-06 19:10:53 +0200 |
| commit | bc3cf0b74ff033d247a826ba55b608922454548a (patch) | |
| tree | 50ea97df74a07e3921ce13238abb5a9b1f107470 /doc/form-notes.rst | |
| parent | 55bcd978af814c90b1d486055940f242dfe0dbde (diff) | |
rm files, move postload hook
bzr revid: al@openerp.com-20121006171053-qggp1r5263h7v7vd
Diffstat (limited to 'doc/form-notes.rst')
| -rw-r--r-- | doc/form-notes.rst | 55 |
1 files changed, 0 insertions, 55 deletions
diff --git a/doc/form-notes.rst b/doc/form-notes.rst deleted file mode 100644 index 98d4a4de67e..00000000000 --- a/doc/form-notes.rst +++ /dev/null @@ -1,55 +0,0 @@ -Notes on the usage of the Form View as a sub-widget -=================================================== - -Undocumented stuff ------------------- - -* ``initial_mode`` *option* defines the starting mode of the form - view, one of ``view`` and ``edit`` (?). Default value is ``view`` - (non-editable form). - -* ``embedded_view`` *attribute* has to be set separately when - providing a view directly, no option available for that usage. - - * View arch **must** contain node with - ``@class="oe_form_container"``, otherwise everything will break - without any info - - * Root element of view arch not being ``form`` may or may not work - correctly, no idea. - - * Freeform views => ``@version="7.0"`` - -* Form is not entirely loaded (some widgets may not appear) unless - ``on_record_loaded`` is called (or ``do_show``, which itself calls - ``on_record_loaded``). - -* "Empty" form => ``on_button_new`` (...), or manually call - ``default_get`` + ``on_record_loaded`` - -* Form fields default to width: 100%, padding, !important margin, can - be reached via ``.oe_form_field`` - -* Form *will* render buttons and a pager, offers options to locate - both outside of form itself (``$buttons`` and ``$pager``), providing - empty jquery objects (``$()``) seems to stop displaying both but not - sure if there are deleterious side-effects. - - Other options: - - * Pass in ``$(document.createDocumentFragment)`` to ensure it's a - DOM-compatible tree completely outside of the actual DOM. - - * ??? - -* readonly fields probably don't have a background, beware if need of - overlay - - * What is the difference between ``readonly`` and - ``effective_readonly``? - -* No facilities for DOM events handling/delegations e.g. handling - keyup/keydown/keypress from a form fields into the form's user. - - * Also no way to reverse from a DOM node (e.g. DOMEvent#target) back to a - form view field easily |
