IRC logs of #tryton for Friday, 2009-04-17 #tryton log beginning Fri Apr 17 00:00:02 CEST 2009
bechamelvengfulsquirrel: maybe "clone" is better than "duplicate" ?00:00
vengfulsquirrelYeah maybe, so that is related to copy taking several ids on the server right ?00:02
bechamelvengfulsquirrel: yes00:03
vengfulsquirrelI kind of read up on the discussion for this release notification, but is this to get notify developers using the project or to attract new users/developers?00:03
vengfulsquirrel*"get notify"=notify00:03
bechamelvengfulsquirrel: the new tax rule system allow to define a way to substitute on an invoice tax from a product with a tax from a rule defined on the party (iirc, I'm not very good for accouting stuffs)00:03
bechamelvengfulsquirrel: this is the heart of the discussion imo00:05
bechamelvengfulsquirrel: the best would be a text which will be ok for both: devs and users00:05
bechamelvengfulsquirrel: hence my idea of adding a paragraph with key features on the top00:06
bechamelvengfulsquirrel: I think the peoples that will be intersted by the news are the ones that are not involved with the project but follow it and check the website from time to time00:10
bechamelvengfulsquirrel: update of account chart from templates: when you start to use the accounting module you have to choose an account chart for your company: this step consist of creating a complete chart from an existing template. so the new feature means that the chart can be resynced with the templates they come from00:16
vengfulsquirrelSo changes to the template can be propagated to an existing chart of an account ?00:18
bechamelvengfulsquirrel: yes00:18
vengfulsquirrelI think we should explain historical data handling.00:33
bechamelvengfulsquirrel: thanks00:38
vengfulsquirrelMake sure you look at "Contextual view inheritance" and the changes to the Account module I kind of changed those around a lot.00:39
bechamelvengfulsquirrel: yes especially as  "historical" is tryton-specific wording00:39
yangoon vengfulsquirrel sorry, but i think there are still errors left00:41
yangoonA more standard xml-rpc API that allow introspection.00:41
yangoon-> allows00:41
vengfulsquirreloh right00:42
vengfulsquirrelMissed that one00:42
vengfulsquirrelbechamel: When are you sending this out ?00:42
bechamelvengfulsquirrel: it's planned for monday00:42
yangoondate of the accounting moves to be differ00:46
yangoon-> different00:46
yangoonvengfulsquirrel: reads much better now, thx00:47
bechamelyangoon: you are faster than me to re-red the text :)00:47
vengfulsquirrelOh I changed it from different to differ but forgot to drop the "be"00:47
bechamelvengfulsquirrel: ok00:47
yangoonbechamel: invoice cancellation: you know, for us (german people around here) it is not a cancellation, but sort of automatic credit note00:49
vengfulsquirrelYeah that maybe could use a better explaination, it is talking about refunds/returns right ?00:49
yangoonbechamel: so perhaps better to change it to: Integrated management of refunds for invoices which can be handled directly from the sale/purchase order.00:51
bechamelyangoon, vengfulsquirrel: the sale/purchase generate automaticaly an invoice, which can be "cancelled" even if still draft00:51
bechamelif the invoice reach the "open" state, the purchase/sale doesn't care anymore00:52
yangoonbechamel: nevertheless we (i.e. the germans;) need a procedure which takes care of an opened invoice, but invalidating the same document, not creating a new one.00:53
bechamelno sorry, the workflow of the purchase take care of the invoice until the payment00:54
vengfulsquirrelbechamel: I gotta go out for a bit, I'll be back later today and tomorrow, so tell me if you want to me to read over more stuff.00:55
bechamelvengfulsquirrel: ok, thanks again00:56
bechamelyangoon: if i understand correctly you need an invoice specific features, the one on the text is only about purchase and sale orders00:57
yangoonbechamel: yes. that's it00:58
yangoonbechamel: the most experienced in this respect is timitos, he has already put a doc together on
bechamelyangoon: moreover, once opened the invoice cannot be cancelled00:58
yangoonthere one can see also the different handling in accounting00:58
yangoonbechamel: cancellation note means for me: transparent invalidation of an invoice01:00
bechamelyangoon: we should plan a meeting next week to talk about what we want for the next release, and prioritise01:00
yangoonbechamel: ack01:00
yangoonbechamel: I am going to slepp now, thx for your work!01:01
bechamelyangoon: ok, me too01:01
bechamelyangoon: good night :)01:02
yangoonbechamel: gn8!01:02
bechamelyangoon: :D01:02
-!- bechamel( has left #tryton01:03
-!- vengfulsquirrel( has left #tryton01:44
-!- juanfer(n=juanfer@ has joined #tryton01:53
juanferIts an evaluation of 40 Top ERPs01:56
-!- ikks(i=igor@ has joined #tryton02:20
-!- igor__(i=igor@ has joined #tryton03:07
-!- yangoon( has joined #tryton05:19 * r567 /wiki/ Edited wiki page through web user interface.06:05 * r568 /wiki/ Edited wiki page through web user interface.06:05
-!- igor__(i=igor@ has joined #tryton07:14
-!- FWiesing( has joined #tryton07:22
-!- sharkcz( has joined #tryton07:49
-!- paepke( has joined #tryton08:07
-!- Gedd(n=ged@ has joined #tryton08:17
-!- ikks(i=igor@ has joined #tryton08:25
-!- sharkcz( has joined #tryton08:36
-!- carlos(n=carlos@ has joined #tryton08:41
-!- Timitos(n=Timitos@ has joined #tryton09:24
-!- cedk(n=ced@gentoo/developer/cedk) has joined #tryton09:41
CIA-48Timitos roundup * #1003/error with newest changeset at login: [new] i updated my db because of changeset f2066eca208a the update succeeded but i get this error at login [Fri Apr 17 10:10:40 2009] INFO:module ...10:14
CIA-48ced roundup * #1003/error with newest changeset at login: [need-eg] Are you sure you updated the database?10:29
-!- Timitos(n=Timitos@ has joined #tryton10:44
-!- bechamel( has joined #tryton11:00
CIA-48Timitos roundup * #1003/error with newest changeset at login: [invalid] sorry. i messed up two different dbs11:00
CIA-48C?dric Krier <> default * 22:7d6c83516d27 account_be/account_be.xml: Add "Compte de r?sultats"11:08
CIA-48 * r569 /wiki/ Edited wiki page through web user interface.12:00
-!- nicoe( has joined #tryton12:56 * r570 /wiki/ Edited wiki page through web user interface.13:06
CIA-48dbrenck roundup * #1004/ ... issue with --database?: [new] Server running on Windows XP, Python 2.4 produces the attached output. I found this, when originally trying the following: python ...13:15
CIA-48dbrenck roundup * #1004/ ... issue with --database?: [chatting] trytond.conf file used13:16
CIA-48dbrenck roundup * #1004/ ... issue with --database?: Listing of the directory that I use to start trytond.13:21
CIA-48ced roundup * #1004/ ... issue with --database?: [testing] You should run the trytond script that must be in C:\Programme\Python\2.4\Lib\site-packages13:35
-!- enlightx( has joined #tryton13:36
CIA-48dbrenck roundup * #1004/ ... issue with --database?: Sorry - no such file in site-packages. See attached file. Install was done by calling: 1. python build 2. python install Re-i ...13:47
CIA-48dbrenck roundup * #1004/ ... issue with --database?: Found: C:\Programme\Python\2.4\Scripts Maybe you mean this?13:50
CIA-48ced roundup * #1004/ ... issue with --database?: Perhaps it is in C:\Programme\Python\2.4\bin13:52
-!- tekknokrat( has joined #tryton13:53
CIA-48ced roundup * #1004/ ... issue with --database?: > Found: C:\Programme\Python\2.4\Scripts > > Maybe you mean this? Yes14:02
-!- Gedd(n=ged@ has joined #tryton14:04
CIA-48Timitos roundup * #1005/changes of changeset 250:394d2eab7a02 on invoice.odt got lost: [new] with this changeset the presentation of taxes was changed. in the newest changeset there is the old behavior again.14:08
-!- paepke( has joined #tryton14:12
CIA-48dbrenck roundup * #1004/ ... issue with --database?: [resolved] Fine - it works now. Ty. Do you have a few words about the trick behind? I found this: which ...14:19
CIA-48C?dric Krier <> default * 341:909e89d4a917 account_invoice/ Fix key construct in get_invoice_taxes14:37
CIA-48C?dric Krier <> default * 342:76d33858d2c6 account_invoice/invoice.odt: Re-add sequence_number on invoice.odt which was lost for issue100514:37
CIA-48ced roundup * #1005/changes of changeset 250:394d2eab7a02 on invoice.odt got lost: [resolved] Fix with changeset 76d33858d2c614:37
CIA-48 * r571 /wiki/ Edited wiki page through web user interface.15:00
-!- woakas(n=woakas@ has joined #tryton15:04
-!- gremly(n=gremly@ has joined #tryton15:28
-!- juanfer(n=juanfer@ has joined #tryton15:54 * r572 /wiki/ Edited wiki page through web user interface.16:01
-!- essich( has joined #tryton16:23
-!- nicoe( has joined #tryton16:38
bechamelhello all, i've created an intro to the list of new features. This spot and explain the moste intersting one:
bechamelthe extensive list ( will follow it16:40
carlosbechamel: it's much better now. Good job!16:59
bechamelcarlos: thanks17:01
-!- juanfer(n=juanfer@ has joined #tryton17:55
bechamelhere is the complete text with intro and listing of features:
Timitosbechamel: i just did some fixes on the first text:
bechamelTimitos: thanks i will merge it18:04
Timitosbechamel: for historical data it would be better to write about for what it can be used or for what it is needed. i will try to do some research about this now18:04
bechamelTimitos: it's explained in the first point of the module section18:05
Timitosbechamel: as it is an eyecatcher i think we should write something about in the beginning.18:06
bechamelTimitos: or maybe a "see module section for an example usage"18:09
Timitosbechamel: i don´t think that everybody would understand this first abstract and the big advantage of this feature18:11
bechamelTimitos: as long as the feature is not more used, it will stay difficult to understand18:12
Timitosbechamel: maybe. but it we can find a good business case where it is needed everyone knowing the business case would understand that and this will push tryton i think18:14
bechamelTimitos: the first business case i see is precisely the invoice one18:15
-!- juanfer(n=juanfer@ has joined #tryton18:15
Timitosbechamel: yes. and now i am searching about some words why this is needed. some keywords having to do with this case18:16
Timitosbechamel: i found this link:
Timitosbechamel: i think the correct term is temporal database18:31
bechamelTimitos: i already talk a lot with ced, and even if temporal is more popular we used "history" in the code so we choose to keep it18:32
Timitosmaybe we can write it like this: Historical/Temporal data handling18:33
bechamelTimitos: and the current implementation is not exactly a temporal db at least not what is described on the wikipedia page18:34
Timitosbechamel: yes. you are right as it is not on database level.18:34
bechamelTimitos: imho the explanation is far more important thant the name we give to the feature18:35
Timitosbechamel: yes18:35
Timitosbechamel: maybe you find something useable in the last link. the mailinglist one:
bechamelTimitos: this link use "historical" the same way18:38
Timitosbechamel: my proposal for this abstract: (i hope it is correct english)19:06
-!- tekknokrat( has joined #tryton19:11
-!- mmarshall( has joined #tryton19:32
-!- vengfulsquirrel( has joined #tryton19:54
-!- kleinerdrache( has joined #tryton19:56
carloshow am I supposed to regiser an invoice payment?20:54
carlosoh, found, I need to create something before the account statement allows me to add data...20:56
Timitoscarlos: you should install a db without account_statement. there is a button on invoice to enter a payment on invoice form then. perhaps this is what you need21:18
carlosisn't account_statement to import bank statements ?21:19
carloswell, the base to implement such imports21:19
Timitosyes i think it could be the base of something like this. i didn´t recognize that you meant something like this21:20
carlosactually, what you told to me is exactly what I need21:22
carloshowever, I installed account_Statement to implement the automatic import for the Spanish banks21:22
-!- mmarshall_( has joined #tryton21:22
carlosso I was just confirming that I was correct on my assumption ;-)21:23
Timitoscarlos: this is a very interesting feature. we should try to create a generic base for such imports21:24
Timitosthe first problem is that the account is required on account_statement and you cannot know this when importing the bank statement lines.21:27
carloshmm, then, account_statement is only useful to introduce that information manually?21:29
Timitosthe next problem i see is that some payments could be an amount related to more than one invoice. but this is perhaps not really a problem as reconiliation can be made later21:29
Timitosfor the moment: yes21:29
Timitoscarlos: i think we also would need some different behavior in editable list because you need an easy way to browse through existing records and entering missing data to them21:31
carlosI see21:38
Timitosi have to go now. cu21:41
-!- tekknokrat( has left #tryton22:07
-!- FWiesing_away( has joined #tryton22:12
-!- essich( has joined #tryton22:23
bechamelvengfulsquirrel: hi22:44
bechamelvengfulsquirrel: I have added a more user-friendly text on top of the existing one :
-!- enlightx( has joined #tryton22:49
vengfulsquirrelbechamel: Okay I'm reading over it23:05
bechamelvengfulsquirrel: great thanks23:05
vengfulsquirrelbechamel: Do you mean translating custom reports? "Better support for translating reports which are overwritten by a custom report."23:42
bechamelvengfulsquirrel: yes there a problem when overloading a report, the strings of the new report weren't available in the list of strings to translate23:44
vengfulsquirrelSo custom reports can now be translated?23:46
vengfulsquirrel"- Better support for translating custom reports."23:47
-!- carlos(n=carlos@ has joined #tryton23:50
bechamelvengfulsquirrel: it was not a problem with all custom report, only with overloading of existing one23:53

Generated by 2.11.0 by Marius Gedminas - find it at!