The proposal to merge lp:~openerp-dev/openobject-server/trunk-client-actions-xmo into lp:openobject-server has been updated.
Description changed to: This proposal adds "client actions" to the server: a very simple description which will be almost entirely managed on the client side (with the client interpreting the action liberally, or ignoring it altogether). This is necessary to several features of the new web client, correct behavior of the POS (which should open as fullscreen as possible and with as little chrome — from the browser and the web client — as possible) for instance. An other use case are actions which are not attached to OpenERP models (either cross-models, or simply not directly relevant to openerp objects) or which would require quite disgusting hacks in/of openerp models and widgets (composing a web-6.0-style home page from a dashboard for instance). This merge proposal contains the following: * Addition of an `ir.actions.client` action type (along with the creation of a skeleton in the db, due to requirements of postgres table inheritance). This action has the following attributes (apart from the usual type, name and ?usage? inherited from `ir.actions.actions`): - tag, which is required, is the client-side of the action type. It is arbitrary and meaningless as far as the server is concerned, and the client can do whatever it wants with it - params, which is optional and a Python dictionary (a live object) it's exactly as its name describes: a keyword arguments dictionary provided to the client along with the action tag, e.g. in order to customize the behavior of a generic client action - params_store, which is the backing serialization store for the kwargs function field. currently, it serializes kwargs using repr & literal_eval, to ensure no data is retrieved which could not be sent over xmlrpc or converted into javascript). * Addition of that action type to the possibilities for `ir.ui.menu`'s action related field, so client actions can be invoked directly from menus. Support for client actions in the web client (as well as the implementation of a client action) has been added in the following branch: https://code.launchpad.net/~openerp-dev/openerp-web/trunk-client-actions-xmo The client action implemented in the web client has been added to the administration dashboard in this branch of the addons: https://code.launchpad.net/~openerp-dev/openobject-addons/trunk-client-actions-xmo Also simplifies ir.actions.todo a bit, removes a state and a type (only types left being "automatic" [formerly current] and "manual" with states "done" and "to do") For more details, see: https://code.launchpad.net/~openerp-dev/openobject-server/trunk-client-actions-xmo/+merge/66609 -- https://code.launchpad.net/~openerp-dev/openobject-server/trunk-client-actions-xmo/+merge/66609 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openobject-server/trunk-client-actions-xmo. _______________________________________________ Mailing list: https://launchpad.net/~openerp-dev-gtk Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-dev-gtk More help : https://help.launchpad.net/ListHelp
