Hello, I would like to emphasis I absolutely supports David here: 1) editable grids in web client would be a lot more user friendly (even more if you could have buttons in list view) 2) having to make 2 clicks in the web clients for the one2many widgets is a HUGE limitation that has no great justification. The OpenERP server is perfectly able to create/update trees of objects passes as hashed, I think it's just too bad if the web client doesn't leverage it unlike the GTK client. Please notice that in my OOOR Ruby client, I have the same limitation currently, but I long ago acknowledged it as a bug instead: http://github.com/rvalyi/ooor/issues#issue/3 (will fix it soon). The problem are not only the boring two clicks! The problem is also mostly that if you you force the user to save the containing object object even if he his actually only exploring the one2many data, he has to save the containing object he he wants a on_change filling a one2many to fire. This happens even when you work with transient osv_memory wizard objects, like with the product configurator. Meaning you potentially force the user to create useless object in the database/memory and then you have to take care/make the user take care of their lifecycle. Currently, I would say this is almost only because of 2) that most of our customers rather use the GTK client as their primary client, using the web only occasionally, especially if they don't have the GTK on their PC (it was also because of the many web client bugs, but I admit it's much much better now). Fabien, fixing 2) seems more important to me than all of the things you specified for the real web client usage we all want. Here are only two reports of that same catch that confuse users/developers: https://bugs.launchpad.net/openobject-client-web/+bug/485304 https://bugs.launchpad.net/openobject-client-web/+bug/500593 Now, aside from that, I like all usability improvements from the last proposal. I like splitting the menu in 2 levels horizontally and vertically. I also like the home page with the first level menu large icon (like Google Chrome), if using appealing icons it will be very good for the branding (please make also sure it's easy to switch the CSS and the icons). But please really consider fixing 2), now at least I'm not along claiming it's a stupid limitation in the web client. -- Raphaƫl Valyi http://www.akretion.com On Wed, Jan 6, 2010 at 9:12 AM, David Janssens