IRC logs of #tryton for Friday, 2009-07-10

chat.freenode.net #tryton log beginning Fri Jul 10 00:00:01 CEST 2009
-!- _TiN_(n=TiN@190.189.9.80) has joined #tryton01:36
-!- digitalsatori(n=tony@116.233.248.233) has joined #tryton01:54
-!- gremly(n=gremly@190.156.162.109) has joined #tryton03:02
-!- yangoon(n=mathiasb@p549F7C74.dip.t-dialin.net) has joined #tryton05:19
-!- Timitos(n=timitos@88.217.184.172) has joined #tryton07:37
-!- johbo(n=joh@statdsl-085-016-072-173.ewe-ip-backbone.de) has joined #tryton08:04
-!- sharkcz(n=dan@plz1-v-4-17.static.adsl.vol.cz) has joined #tryton08:09
-!- bechamel(n=user@host-85-201-74-27.brutele.be) has joined #tryton08:10
-!- enlightx(n=enlightx@host-84-220-83-253.cust-adsl.tiscali.it) has joined #tryton08:54
-!- carlos(n=carlos@77.156.221.87.dynamic.jazztel.es) has joined #tryton09:12
-!- cedk(n=ced@gentoo/developer/cedk) has joined #tryton09:54
-!- paepke(n=paepke@mail.metaldyne-nue.de) has joined #tryton10:20
-!- gremly(n=gremly@190.156.162.109) has joined #tryton10:21
-!- gremly(n=gremly@190.156.162.109) has joined #tryton11:05
CIA-70ced roundup * #1103/Usage of widget="one2many" on many2many raise client exception:11:46
CIA-70[chatting] For me, it is not an issue as it can work because the internal model of o2m and m2m are very different.11:46
CIA-70It was working on OpenERP beca ...11:46
CIA-70http://bugs.tryton.org/roundup/issue110311:46
-!- enlightx(n=enlightx@ip-100-175.sn2.eutelia.it) has joined #tryton11:50
-!- tekknokrat(n=gthieleb@dslb-088-074-177-068.pools.arcor-ip.net) has joined #tryton12:55
-!- _TiN_(n=TiN@190.189.9.80) has joined #tryton14:32
pantherayangoon: i've uploaded 1.2.1 packages, and also created -modules-account-be.14:33
pantherayangoon: please have a look at the later and let me know if i should upload it.14:34
yangoonpanthera: will do14:38
-!- enlightx(n=enlightx@ip-100-175.sn2.eutelia.it) has joined #tryton14:55
-!- woakas(n=woakas@190.144.69.234) has joined #tryton15:17
-!- paepke(n=paepke@p5B32D754.dip.t-dialin.net) has joined #tryton16:17
-!- carlos(n=carlos@66.Red-83-38-118.dynamicIP.rima-tde.net) has joined #tryton17:20
-!- carlos(n=carlos@66.Red-83-38-118.dynamicIP.rima-tde.net) has joined #tryton17:50
-!- johbo(n=joh@statdsl-085-016-072-173.ewe-ip-backbone.de) has joined #tryton18:17
-!- vengfulsquirrel(n=ian@c-69-181-194-95.hsd1.ca.comcast.net) has joined #tryton18:35
-!- carlos(n=carlos@66.Red-83-38-118.dynamicIP.rima-tde.net) has joined #tryton18:41
-!- enlightx(n=enlightx@host-84-220-83-253.cust-adsl.tiscali.it) has joined #tryton18:47
-!- carlos(n=carlos@66.Red-83-38-118.dynamicIP.rima-tde.net) has joined #tryton19:31
-!- carlos(n=carlos@66.Red-83-38-118.dynamicIP.rima-tde.net) has joined #tryton19:51
vengfulsquirrelhey guys, if you were going to create a shipment from one warehouse to another warehouse would you expect that to be done with an internal shipment between input and output zones?  or does that matter, would it just be between the exact locations where those products were stored in each warehouse ?19:52
bechamelvengfulsquirrel: you can do both, if you already know where to take the product and where to put them you can create one internal shipment between the two locations20:10
bechamelvengfulsquirrel: if the goods must be delivered  across several locations on the "receiving" warehouse i think it simpler to create a first internal shipment to the input location and then after several internal shipment from the incoming location to other locations of the warehouse20:12
vengfulsquirrelso warehouse 1's storage --> warehouse 2's input --> warehouse 2's storage20:15
bechamelvengfulsquirrel: yes20:20
-!- carlos(n=carlos@66.Red-83-38-118.dynamicIP.rima-tde.net) has joined #tryton20:21

Generated by irclog2html.py 2.11.0 by Marius Gedminas - find it at mg.pov.lt!