erp5_pdm: show first newest movement in movement history dialog

User is usually interested by last movement in stock, not by several
months/years old movement. Thus display first fresh movement, and user
could then go to next pages to see oldest movements if needed.

bt5/erp5_pdm/SkinTemplateItem/portal_skins/erp5_pdm/Resource_getReversedMovementHistoryList.py

+history_list = context.getMovementHistoryList(**kw)
+reverse_list = []
+for x in history_list:
+  reverse_list.insert(0, x)
+return reverse_list

bt5/erp5_pdm/SkinTemplateItem/portal_skins/erp5_pdm/Resource_getReversedMovementHistoryList.xml

+<?xml version="1.0"?>
+<ZopeData>
+  <record id="1" aka="AAAAAAAAAAE=">
+    <pickle>
+      <global name="PythonScript" module="Products.PythonScripts.PythonScript"/>
+    </pickle>
+    <pickle>
+      <dictionary>
+        <item>
+            <key> <string>Script_magic</string> </key>
+            <value> <int>3</int> </value>
+        </item>
+        <item>
+            <key> <string>_bind_names</string> </key>
+            <value>
+              <object>
+                <klass>
+                  <global name="NameAssignments" module="Shared.DC.Scripts.Bindings"/>
+                </klass>
+                <tuple/>
+                <state>
+                  <dictionary>
+                    <item>
+                        <key> <string>_asgns</string> </key>
+                        <value>
+                          <dictionary>
+                            <item>
+                                <key> <string>name_container</string> </key>
+                                <value> <string>container</string> </value>
+                            </item>
+                            <item>
+                                <key> <string>name_context</string> </key>
+                                <value> <string>context</string> </value>
+                            </item>
+                            <item>
+                                <key> <string>name_m_self</string> </key>
+                                <value> <string>script</string> </value>
+                            </item>
+                            <item>
+                                <key> <string>name_subpath</string> </key>
+                                <value> <string>traverse_subpath</string> </value>
+                            </item>
+                          </dictionary>
+                        </value>
+                    </item>
+                  </dictionary>
+                </state>
+              </object>
+            </value>
+        </item>
+        <item>
+            <key> <string>_params</string> </key>
+            <value> <string>**kw</string> </value>
+        </item>
+        <item>
+            <key> <string>id</string> </key>
+            <value> <string>Resource_getReversedMovementHistoryList</string> </value>
+        </item>
+      </dictionary>
+    </pickle>
+  </record>
+</ZopeData>

bt5/erp5_pdm/SkinTemplateItem/portal_skins/erp5_pdm/Resource_viewMovementHistoryDialog/listbox.xml

@@ -561,7 +561,7 @@
       <dictionary>
         <item>
             <key> <string>method_name</string> </key>
-            <value> <string>getMovementHistoryList</string> </value>
+            <value> <string>Resource_getReversedMovementHistoryList</string> </value>
         </item>
       </dictionary>
     </pickle>

[Romain Courteaud]

@seb could you update this commit with an up to date erp5, in order to publish the expected xml output?

The issue was posted by this test

[Jérome Perrin]

I'm wondering why we don't use the "normal" sort functionality of listbox ? With this change, the date column is sortable, so if this implementation just reverse the order, and will behave differently than in other listboxs.

PS: similar change (but more global) was discussed in !1305

[Jérome Perrin]

I'm wondering what to do here, if we change the order, I feel it would be much better to just change in the listbox, because as said in the previous comment the buttons showing the sort order would work as expected and I think this would also look a bit better when there are more than 1000 movements (because getMovementHistoryList has a limit of 1000).

@romain do you think we should revert for now ?

[Romain Courteaud]

I also do not understand why the sort parameter of the listbox was not used.

If getMovementHistoryList has a limit of 1000, this commit is not usable anyway. I also agree to revert, and change the listbox's default sort.

[Jérome Perrin]

Thanks, I did e8d20966 and b5124bd9