I really don't feel comfortable with having client implementation details 
stored in the server as first-class actions. What have js controller names and 
parameters to do in the database? This is nothing that the server or other 
clients will understand. Are we now tying ourselves to javascript client 
scripting on top of python now??
Actions are supposed to be a major part of the protocol, if we do this, that 
major part of the protocol won't be fully supported anymore by all official 
clients.

If the goal is to have web data to pass to client-side, why not piggyback on 
ir.actions.act_url, which at least all clients know how to handle, and in a 
manner that degrades correctly?
If you ensure that the web client supports controller references in 
location.hash, a la http://url#!/MySuperController?param=value, this will even 
work on any client, as they could open a browser to that web client URL 
(assuming the web client is running somewhere, obviously)

But perhaps that doesn't cover all the use cases, I'm not sure.

- Starting POS? Well, this could be a menu bound to an act_url with target=new, 
as it does not behave at all like other menus ; btw that's minimal chrome, and 
would work perfectly on all clients.

- An action embedded in a dashboard? Hmm, why not make it an act_url with a 
controller reference in the URL, and make the web client recognize it so it 
knows to load that controller in the corresponding area. This could also work 
for non-OpenERP-related actions too, and again, degrades fine in other clients.

- Cross-model actions? Wait, why shouldn't they be implemented server-side? Why 
shouldn't that logic be stored with the rest of the business logic, available 
for other (re)uses too, through the standard OpenERP API (and then simply 
relying on web widgets for special rendering)

Thoughts?
-- 
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

Reply via email to