git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31493 20353a03-c40f-0410-a6d1-a30d3c3de9de

* call SolverTypeInformation.conflictsWithSolver() with solver type information instead of its id string.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31492 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31491 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31490 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31487 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31486 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31485 20353a03-c40f-0410-a6d1-a30d3c3de9de

if 'movement' that is passed to solver is a delivery (eg. in case of start_date divergence), we need to find related simulation movements by its movements.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31484 20353a03-c40f-0410-a6d1-a30d3c3de9de

* rename variables to make more sense.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31483 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31482 20353a03-c40f-0410-a6d1-a30d3c3de9de

Improve discussions, add scripts that are needed to ease the integration with websites for instance.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31481 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31479 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31478 20353a03-c40f-0410-a6d1-a30d3c3de9de

It is not necessary to build the entire list of transformation lines,
we can just examine and filter each line, as they are yielded


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31477 20353a03-c40f-0410-a6d1-a30d3c3de9de

During the review of simulation refactoring with Kaz, we found that it made more sense to implement movement aggregation at the applied rule level and implement and N to M matching process rather than a 1 to N. This requires AmountGenerator and MovementGenerator to provide a separate API with no aggregation. Moreover, aggregation process should if possible be implemented consistently accross ERP5. DivergenceTesters seem to be the appropriate core component for that. MovementGroup themselves could be based on embedded DivergenceTesters and getAggregated* method could use themselved MovementGroup, either temporary instances dynamically generated, or existing instances found in appropriate context. This gives an idea of future directions. However, initial implementation will focus first on stable expand.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31476 20353a03-c40f-0410-a6d1-a30d3c3de9de

Pile up a list of filters to apply, and filter the transformation_line_list
only once, instead of walking the list for each filter.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31475 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31474 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31473 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31472 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31471 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31470 20353a03-c40f-0410-a6d1-a30d3c3de9de

The Folder meta type should only be used for modules (for now). In the future, there will be a ModuleType portal type of portal type, and Folder meta type will no longer be used and will only act as a base class.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31469 20353a03-c40f-0410-a6d1-a30d3c3de9de

Reversed the order of expected lines in the test in order to make it pass. More work is required here so that the order of test results becomes predicatble. Current approach for test has no real consequence on real usability or on quality of the system. However, make order predictable would allow reducing the maintenance cost of tests.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31468 20353a03-c40f-0410-a6d1-a30d3c3de9de

Fix collateral damages. Take into account uids for filtered selection at the level of selection params. Sort results in a canonical way so that results are predicated, tests possible, and user feels better by havin results grouped by workflow and state always in the same order.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31467 20353a03-c40f-0410-a6d1-a30d3c3de9de

Initial implementatoin of mass workflow state change was playing arround the API of SelectionTool and Selection, getting parameters and reimplementing part of Selection.__call__ API in order to be able to override certain parameters. As a result, some parameters were not taken into account in some cases and the result was not the same as the one from the selection. In this change, we extend the API of Selection so that, just like for methods, it is possible to override in a non persistent way the parameters which are passed to the selection method. This is similar to the existing possibility of overriding the calling context or the selection method.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31466 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31465 20353a03-c40f-0410-a6d1-a30d3c3de9de

recording quantity property in simulation movements don't work well because we don't use quantity for matching.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31464 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31463 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31462 20353a03-c40f-0410-a6d1-a30d3c3de9de

Whenever there are no validation errors, the user input should be rendered by a float field as a float, not as the user input. (this behaviour is consistent with the form framework, although it should not be considered as a specification and could evolve)

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31461 20353a03-c40f-0410-a6d1-a30d3c3de9de

Make sure that the values entered by the user in the matrixbox are displayed in priority whenever the form has any error (even outside the matrixbox).

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31460 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31459 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31458 20353a03-c40f-0410-a6d1-a30d3c3de9de

use solver category in SimulationMovement, and remove non-working getSolverList() method in SimulationMovement and AppliedRule.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31457 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31456 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31455 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31454 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31453 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31452 20353a03-c40f-0410-a6d1-a30d3c3de9de

Zope 2.12 now correctly outputs response header linebreaks with \r\n
instead of just \n, including the double line-break in the header/body
separator.

Adjusted the regular expression and simplified the body parsing logic in
Products.ERP5Type.tests.ERP5TypeTestCase.ResponseWrapper.getBody()



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@31449 20353a03-c40f-0410-a6d1-a30d3c3de9de