c2c-oerpscenario team mailing list archive
-
c2c-oerpscenario team
-
Mailing list archive
-
Message #03468
[Bug 595783] Re: [trunk] rng view validation breaks web client shiny modularity
Raphael,
The RNG validator does not enforce the values of the "widget" attribute
of fields, hence you can implement web widgets that you turn on that way
on specific fields. Other types of extensions like controllers or
templates do not directly depend on the syntax of XML views, so should
not be a problem either.
If you want to include arbitrary elements in your view definition, you
may also choose to put it in a <html> element, where you can combine
HTML and regular OpenERP XML. See the html_view module in trunk for an
example.
Does that answer you question? Otherwise feel free to reopen with a more
detailed explanation of what you have in mind :-)
** Changed in: openobject-server
Status: New => Invalid
--
[trunk] rng view validation breaks web client shiny modularity
https://bugs.launchpad.net/bugs/595783
You received this bug notification because you are a member of C2C
OERPScenario, which is subscribed to the OpenERP Project Group.
Status in OpenObject Server: Invalid
Bug description:
Hello,
the new modularity of the v6 web client is all the rage, but this is currently limited by the way the server validates XML views using the bin/addons/base/rng/view.rng file where all the existing widgets have to be pre-hardcoded.
Something better, possibly allowing to skip the validation or eventually extend it under certain circumstances (like very special addons view) would be welcome...
Follow ups
