openerp-community team mailing list archive

[Raphael Valyi <rvalyi@xxxxxxxxx>]

Hello,

just to mention we negociated for Aflex OPW renewal that o2m would be
sortable on client side, it has been written as one of the regression to
fix in the renewal contract to bought to OpenERP. So I think this is
related to this: when you click on the header column of a o2m table (like
sale orders), it should re-order the table, that should include support on
the client side indeed for records not yet saved.

Olivier, I'll active the regular OPW bureaucracy artillery for that, but as
for now, I just took the opportunity to mention they need it too. You can
check with Fabrice Henrion about the deal.

Also, as I believe there nothing confidential here. Here is what Fabrice
answered me about that need for o2m ordering:

"
-          **Regarding the sort_by, I confirm that we will do it, merge in
trunk, and it will be available in v8. FYI, following is an excerpt of what
the web team says about it internally. In a nutshell, it’s not as easy as
in v6.1 namely because of the sequence handles.
*C'est en réalité un peu plus compliqué que pour les list views normales
car la lecture des lignes se fait lors de la lecture du record parent, pas
via un appel séparé permettant le tri -> donc lecture séparée à gérer dans
le widget en cas de tri. De plus il faut décider de ce qui se passe
lorsqu'on trie avec des lignes o2m qui ne sont pas encore sauvegardées, ce
qui n'arrive pas dans une list view normale (on pourrait simplement forcer
la sauvegarde ou afficher un message demandant de sauvegarder d'abord)"*
*
*

Hope this helps. Regards.

-- 
Raphaël Valyi
Founder and consultant
http://twitter.com/rvalyi <http://twitter.com/#!/rvalyi>
+55 21 2516 2954
www.akretion.com





On Wed, Oct 2, 2013 at 8:29 AM, Olivier Dony <odo@xxxxxxxxxxx> wrote:

> On 10/01/2013 07:10 PM, ferdinand wrote:
>
>> On 10/01/2013 03:16 PM, Olivier Dony wrote:
>>
>>> Is there any new version of one2many_sorted? The one I can see [1] does
>>> not
>>> perform any sorting or grouping on the client-side, so it does not seem
>>> to
>>> address the limitations I was referring to??
>>>
>>> [1]
>>> http://bazaar.launchpad.net/~**camptocamp/c2c-rd-addons/7.0/**
>>> view/head:/one2many_sorted/__**init__.py<http://bazaar.launchpad.net/~camptocamp/c2c-rd-addons/7.0/view/head:/one2many_sorted/__init__.py>
>>>
>> no this one does sorting on the server side.
>>
>> I attach the patches (for 6.0) which allowed to filter and sort not
>> database
>> fields on client side
>>
>
> Thanks for the patches. Unfortunately we do need sorting on the *client
> side*, which means sorting records that may not be in the database yet, or
> whose values for the "sorted column" may have changed since they were
> loaded.
> The user needs to be able to see in real time the effect of all the local
> changes to the lines, before pressing the Save button.
>
> The patches you sent seem to add an extra non-SQL-backed sorting system on
> the server-side for honoring sorts on non-SQL-backed fields (function
> fields), but the sorting does not actually happen on the client-side.
>
> We would need to do something similar but in the web layer, and that would
> presumably take care of sorting non-SQL fields too. But it really needs to
> operate on the local temporary lines stored on the client.
>
>
> ______________________________**_________________
> Mailing list: https://launchpad.net/~**openerp-community<https://launchpad.net/~openerp-community>
> Post to     : openerp-community@lists.**launchpad.net<openerp-community@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~**openerp-community<https://launchpad.net/~openerp-community>
> More help   : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>
>