Thanks, I needed to start to talk of some ideas I could have, so thanks for your answer.
* I went in openerp.web.Widget and saw .render() and the ".template" attribute is exactly what I was about to implement. Why wasn't it used ? This branch proposes to use Widget's philosophy. The next both points have been removed from this new branch. Nevertheless I'll answer the questions: * I setup a "ListViewClass" attribute because otherwise I should do as you hinted: replace "openerp.web_mobile.ListView". I cannot afford in the current situation to break the web_mobile which code I must watch regularly, test, tweak, and learn openerp. I must update daily the branch, and it's much more convenient (and cleaner) to build an add-on that does not break "web_mobile" add-on. * sub-templating: I won't be using the same menu, but want to be able to use the form template, or the list template in a different context (my Header and Footer bars are different...). I can propose a branch for each of these last 2 matters if you think it might be of interests. -- https://code.launchpad.net/~vaab/openerp-web/mobile-client-use-widget-render/+merge/76606 Your team OpenERP R&D Team is subscribed to branch lp:~openerp-dev/openerp-web/mobile-client. _______________________________________________ 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
