Odoo Server (MOVED TO GITHUB)

[trunk] rng view validation breaks web client shiny modularity

Bug #595783 reported by Raphaël Valyi - http://www.akretion.com
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Invalid
Undecided
Unassigned

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...

Revision history for this message
Olivier Dony (Odoo) (odo-openerp) wrote :

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
Revision history for this message
Raphaël Valyi - http://www.akretion.com (rvalyi) wrote : Re: [Bug 595783] Re: [trunk] rng view validation breaks web client shiny modularity

Yes, well I mean it looks like the RNG has been fixed for the "widget" tag
indeed. At some point the report was valid at the time it was made, glad you
fixed it though.

On Tue, Nov 9, 2010 at 10:45 PM, Olivier Dony (OpenERP) <
<email address hidden>> wrote:

> 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 direct subscriber
> of the bug.
>
> 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...
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/openobject-server/+bug/595783/+subscribe
>

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.