An error occurred fetching the project authors.
  1. 24 Jan, 2014 1 commit
  2. 26 Jan, 2013 1 commit
    • Julien Muchembled's avatar
      Simulation: index 'delivery' categories in ZODB · 0a8fbb36
      Julien Muchembled authored
      Use of catalog to get related simulation movements from delivery lines/cells is
      unreliable.
      
      Until now, for any new code written for simulation, we often had to be careful
      not to call getDeliveryRelatedValueList too early, usually by deferring code
      to activities with complicated dependencies. Race conditions are difficult to
      avoid by developping this way, because for a given delivery, there are
      potentially so many events that happen at the same time, involving:
      - simulation, amongst causality, expand, building, solving (including split)
      - alarms, user actions, external interfaces, chains of activities
      - several related deliveries and simulation trees
      
      This commit enables ZODB-indexing of related documents for 'delivery' base
      category, making getDeliveryRelatedValueList safe and fixing unlink of
      deleted delivery lines/cells.
      
      Existing activity dependencies are left unchanged because builders only uses
      catalog and local building needs to find all simulation movements.
      0a8fbb36
  3. 09 Nov, 2010 1 commit
  4. 16 Sep, 2010 1 commit
  5. 05 Aug, 2010 1 commit
  6. 04 Aug, 2010 1 commit
  7. 20 Jun, 2010 1 commit
    • Jean-Paul Smets's avatar
      Business Path has beed splitted in 2 parts. A first part which is only used to... · 21f40032
      Jean-Paul Smets authored
      Business Path has beed splitted in 2 parts. A first part which is only used to control completation of trade phases and build process. A second part which is only used to define arrows, quantity shares and dates on amounts generated by amount generators. The first part is a predicate but no longer a Path (no arrow, no quantity, no delay, etc.). It is thus renamed to Business Link. The second part is a Path since it defines an Arrow, a quantity, a lead time, etc. It is thus renamed to Trade Model Path. 
      It is now time to review in detail all interfaces. In particular those interfaces on Business Link related to time management many no longer be needed since it is simpler to lookup simulation. However, time management must be handled at Business Process level as a helper method for rules which need to calculate dates based on Business Links and/or Trade Model Path.
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/sandbox/amount_generator@36465 20353a03-c40f-0410-a6d1-a30d3c3de9de
      21f40032
  8. 02 Mar, 2010 1 commit
  9. 22 Feb, 2010 1 commit
  10. 15 Dec, 2009 1 commit
  11. 19 Nov, 2009 1 commit
  12. 07 Nov, 2009 1 commit
  13. 18 Feb, 2009 1 commit
    • Jérome Perrin's avatar
      Simplify budget model variations, only 2 simple class are used: · 5fd031ec
      Jérome Perrin authored
       - NodeBudgetVariation that explicitly lists the possible values one by one,
         either by selecting them of specifying a script to return this list of
         values
       - CategoryBudgetVariation that uses a base category
      for each one, you specify what will be the "axis" used for getInventory (node,
      mirror_node, node_category etc)
      
      "SectionCategoryBudgetVariation" is therefore useless, it's a
      CategoryBudgetVariation where the axis is "section_category"
      
      Budget Cell, Budget Line and now Budget itself can be variated
       
      
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@25611 20353a03-c40f-0410-a6d1-a30d3c3de9de
      5fd031ec
  14. 08 Jan, 2009 1 commit
  15. 03 Jan, 2007 1 commit
  16. 08 Feb, 2004 1 commit
  17. 10 Dec, 2002 1 commit