IRC logs of #tryton for Tuesday, 2012-07-03

chat.freenode.net #tryton log beginning Tue Jul 3 00:00:01 CEST 2012
2012-07-03 00:30 -!- bechamel`(~user@host-85-201-156-238.brutele.be) has left #tryton
2012-07-03 03:33 -!- rhubner(~rhubner@189.114.250.224) has left #tryton
2012-07-03 11:19 <__efx__> Hello, I have a strange behavior in the client. I add a Company and a party and associate the party to the company as a new employee. When a try to create a user in the admin module I can not select the employee I just created. Have I missed something ?
2012-07-03 11:21 <__efx__> Ok I understand I can only add employee in the employees list but not in the employee field what is then this employee field of the User ?
2012-07-03 11:36 <bechamel> __efx__: there are employees that are not users
2012-07-03 11:36 <bechamel> __efx__: so creating an employee doesn't create a user
2012-07-03 11:37 <bechamel> __efx__: so you must create a user and link it to an employee
2012-07-03 11:56 <__efx__> bechamel: that's exectly what I did, however I can not find the employee in the employee field of the user, however they can be added in the employeeS of the user
2012-07-03 11:56 <__efx__> bechamel: that's why I don't understand the difference between the list of employees and the simple employee field of the user module
2012-07-03 11:57 <bechamel> __efx__: did you check if they are all in the same company than the admin ?
2012-07-03 11:58 <__efx__> bechamel: yes
2012-07-03 12:48 <navis> hi all, after quite a pause in my tryton research and experimentations, I have edited https://code.google.com/p/tryton/wiki/SaleB2c with a better segmentation of the problems and potential solutions to the issues for b2c adaptations in tryton
2012-07-03 12:48 <navis> can anyone with an interrest in this have a look and comment ?
2012-07-03 12:50 <navis> (here or on the wiki)
2012-07-03 12:52 <bechamel> navis: Hi, you will reach a bigger audience if you talk about it on the mailing list
2012-07-03 12:56 <navis> I read the mailing list through gmane, do you know if posting from gmane works ?
2012-07-03 12:57 <navis> bechamel: I just sent a message through gmane, will see if it works, otherwise I'll repost it through the web interface
2012-07-03 12:58 <bechamel> navis: never tried
2012-07-03 12:59 <bechamel> navis: about the blueprint: IMO it is a good summary of the issue
2012-07-03 13:00 <bechamel> but it may help to list the possible use cases, because this will help to balance pros and cons of the solutions
2012-07-03 13:01 <navis> bechamel: is the google group moderated ?
2012-07-03 13:01 <bechamel> navis: yes
2012-07-03 13:02 <navis> bechamel: have you received my gmane message ?
2012-07-03 13:02 <bechamel> navis: but I don't see any messages in the moderation queue
2012-07-03 13:02 <navis> bechamel: ok so I'll assume that it doesn't work and repost through the web
2012-07-03 13:03 <navis> bechamel: thanks for your comments. The use case is easy: all facilities facing end users *must* use this workflow
2012-07-03 13:03 <bechamel> navis: you can also send a mail with your mail client (it's the default way of using it)
2012-07-03 13:04 <bechamel> navis: i'm thinking about the sentence : "Implementing it as another object means that all extentions made to sale are not automatically availlable in that new object"
2012-07-03 13:05 <bechamel> navis: and I don't see where/how it can be a problem
2012-07-03 13:06 <bechamel> navis: if the use case is a point of sale: no need to create one shipment per sale and no need for invoice
2012-07-03 13:06 <bechamel> navis: and most probably no need for the sale_price_list module
2012-07-03 13:07 <navis> bechamel: a pos is one possible use case, but not the only one
2012-07-03 13:08 <navis> bechamel: think a retail web site, a phone order company,...
2012-07-03 13:08 <navis> bechamel: in the introduction: Note that while this is a probable requirement before a pos solution can be implemented, it is tackling a different problem than a pos workflow or interface. Any b2c facing facility (web sites, phone orders, deliveries, pos,...) is impacted.
2012-07-03 13:09 <navis> bechamel: this is definitely needed for a pos, but not only in this case
2012-07-03 13:10 <bechamel> navis: ok, I skipped the intro :)
2012-07-03 13:10 <navis> bechamel: besides, a pos also needs invoicing
2012-07-03 13:12 <navis> bechamel: rhaaa, I make a nice intro, with nice phrases and all, and it's like a manual, nobody reads it :-)
2012-07-03 13:13 <bechamel> navis: ;)
2012-07-03 13:53 <sharoonthomas> navis: its a good summary f the issue as becamel said
2012-07-03 13:54 <sharoonthomas> navis: about storing the tax included price, i am doubtful of its feasibility, because there could be several tax included prices depending on who you sell it to?
2012-07-03 14:08 <navis> sharoonthomas: yes the tax included price has to be linked to the most common scenario
2012-07-03 14:09 <navis> sharoonthomas: for example in Belgium, this is belgian vat and taxes
2012-07-03 14:10 <navis> sharoonthomas: all other clients (for example from France) could have different prices
2012-07-03 14:11 <sharoonthomas> navis: exactly the point, so even if we assume b2c there will be several tax situations for which the tax included price has to be stored ?
2012-07-03 14:15 <navis> sharoonthomas: I don't think it's necessary to store all of them, most shops have a most common scenario, which is the one that should be used
2012-07-03 14:16 <navis> sharoonthomas: for example, to calculate prices using rounding on tax included prices in pricelists, you can only do that for one scenario
2012-07-03 14:17 <navis> sharoonthomas: other scenarii cannot have rounded prices
2012-07-03 14:18 <navis> I have edited the wiki to add that precision
2012-07-03 14:36 <navis> and I just added all irc logs for reference
2012-07-03 18:53 -!- navis(~user@91.180.113.153) has left #tryton
2012-07-03 19:43 -!- lukio(~lukio@186.23.122.88) has left #tryton

Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!