On Wednesday 21 September 2011, you wrote: > Sorry, but I would like to ensure you don't miss the current API design > issues, or else you might just fail to plan its correction over the next > releases. >... > - on_change is expected to work even if the record isn't saved yet ... > - but mostly, the client API expect a "value" dictionary ...
I see your point, you are right about that. It is then true, that we keep an "open" Record in the client, while we want to dispatch partial computations to the server for it. One other issue that has bothered me is: What precedence should computed values have? For example, in an account.invoice.line, you could have on_change() compute (and send back) the default UoM, price. But, if the user has already typed them in, should they be replaced? Give me a little time to look at the OOOR API.. _______________________________________________ Mailing list: https://launchpad.net/~openerp-expert-framework Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-expert-framework More help : https://help.launchpad.net/ListHelp
