xrg, something I don't really understand: You' often mention great changes you did in your branch. Well, of course this is cool, many people do great change in some branch, even Tryton did.
Now, why are those change buried in your pg84* branch and not merged in trunk? Is that: - a lack of will from OpenERP SA, from you?? - a lack of resource? If so, why don't you propose merge proposals so that the experts can comment and improve? I cannot understand how you can work for OpenERP SA and those change by buried in such a way that 99% of people potentially interested in them don't see them. Also let me recall you that just like many integrators around, Akretion is a small company and if we can afford maintaining some 5 patches or backport per customer deployment we cannot afford merging with a whole non official branch. It would be too much maintenance effort for us. Any explanation about that? This "struct" field is all about that: it allows a /structure/ of pythonic > fields to come as a payload. It could be a list, a dict, whatever. > Actually, > the "serializable" field had the same behavior, wrt. to the client API. I > just > thought it would be better to use json-encoded storage instead of > repr()/eval(). Especially in a period that nobody seems to use those fields > (or > know their existence). > Well, will double look. I should have missed something, buy my understanding is that is was complementary to what we did, not redundant. May be I should explain also better what we did. -- Raphaël Valyi Founder and consultant +55 21 3010 9965 www.akretion.com
_______________________________________________ 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
