| chat.freenode.net #tryton log beginning Thu Jul 26 00:00:02 CEST 2012 | ||
| 2012-07-26 00:29 -!- sampac(~sampaccou@def92-7-82-231-203-127.fbx.proxad.net) has left #tryton | ||
| 2012-07-26 01:55 -!- rhubner(~rhubner@187.112.44.214) has left #tryton | ||
| 2012-07-26 07:39 -!- sharoonthomas(~sharoonth@122.177.212.241) has left #tryton | ||
| 2012-07-26 08:44 <sharoonthomas> can someone explain to me the idea behind the project_plan module and how the leveling is supposed to be used ? | ||
| 2012-07-26 09:33 <cedk> sharoonthomas: indeed with the current UI, it is quite complicated | ||
| 2012-07-26 09:34 <cedk> sharoonthomas: but leveling is about fixing overscheduling of employees | ||
| 2012-07-26 09:34 <sharoonthomas> cedk: ok, and can you explain the date time fields please ? | ||
| 2012-07-26 09:39 <cedk> sharoonthomas: it is the datetime for Gantt charts | ||
| 2012-07-26 09:40 <sharoonthomas> cedk: constraint_x_time is like the time within which the task *MUST* be started and stopped ? | ||
| 2012-07-26 09:45 <cedk> sharoonthomas: those are computed by the leveling | ||
| 2012-07-26 09:46 <sharoonthomas> cedk: the leveling distributes the task across the allocated employees ? | ||
| 2012-07-26 09:48 <cedk> sharoonthomas: in some way | ||
| 2012-07-26 13:16 -!- cristatus(~amit@1.22.97.195) has left #tryton | ||
| 2012-07-26 16:03 <rhubner> Hi nicoe | ||
| 2012-07-26 16:06 <nicoe> rhubner: hello | ||
| 2012-07-26 16:07 <rhubner> nicoe: I finished the operation of the widget... | ||
| 2012-07-26 16:07 <nicoe> rhubner: I saw the codereview | ||
| 2012-07-26 16:07 <nicoe> rhubner: I'll check them late today | ||
| 2012-07-26 16:08 <rhubner> nicoe: while the code is revised, I would like to talk now about the visual | ||
| 2012-07-26 16:08 <rhubner> nicoe: ok.. | ||
| 2012-07-26 16:08 <nicoe> rhubner: yes | ||
| 2012-07-26 16:09 <nicoe> rhubner: according to me there will be a lot of edit in a short time span and the record won't be changed before long | ||
| 2012-07-26 16:09 <nicoe> rhubner: so I think that evenly putting steps in the gtk.Scale is not right | ||
| 2012-07-26 16:10 <rhubner> nicoe: I gree | ||
| 2012-07-26 16:10 <nicoe> rhubner: I think that on top of it we should have a visual representation of the changes, and moving the scale would zoom in some period of time | ||
| 2012-07-26 16:10 <nicoe> rhubner: but this is difficult :D | ||
| 2012-07-26 16:11 <rhubner> nicoe: I studied something about goocanvas... But I found it difficult to start something from scratch | ||
| 2012-07-26 16:13 <nicoe> rhubner: we need a way to visualy make this obvious | ||
| 2012-07-26 16:13 <rhubner> nicoe: the closest examples I found, are the sound and video editing... those bars that has to make cuts, do you know? | ||
| 2012-07-26 16:17 <rhubner> nicoe: I also thought about using "graphviz", but I do not know if I can manipulate the graph with events | ||
| 2012-07-26 16:18 <nicoe> rhubner: I doubt you can | ||
| 2012-07-26 16:18 <cedk> for me, a good solution will be to have an infinite Scale | ||
| 2012-07-26 16:18 <nicoe> rhubner: bechamel proposed something like http://www.google.com/finance?cid=694653 | ||
| 2012-07-26 16:18 <nicoe> rhubner, cedk: I think we can have both | ||
| 2012-07-26 16:19 <rhubner> cedk: infinite scale? | ||
| 2012-07-26 16:20 <cedk> rhubner: yes a scale that put the cursor in the midle and double the size when you reach a border | ||
| 2012-07-26 16:21 <cedk> but I'm thinking about inifite scale that just move the value left-right and why not using the scroll-wheel for the scale | ||
| 2012-07-26 16:25 <rhubner> I could limit the amount of data on the scale and when the cursor arrived at the bound, the scale was rebuilt into new data | ||
| 2012-07-26 16:25 <rhubner> what do you think? | ||
| 2012-07-26 16:26 <cedk> rhubner: which data ? | ||
| 2012-07-26 16:28 <rhubner> cedk: rather than being infinite, I recreate the information on the scale every time it reached in the limit | ||
| 2012-07-26 16:29 <rhubner> data = timeline scale data | ||
| 2012-07-26 16:31 <rhubner> cedk nicoe: the problem of all is that to solve the problem... but it will not be "beautiful" | ||
| 2012-07-26 16:32 <cedk> rhubner: I don't understand which data? | ||
| 2012-07-26 16:32 <cedk> rhubner: a timeline doesn't have any data | ||
| 2012-07-26 16:33 <rhubner> cedk: I mean "dates" in scale | ||
| 2012-07-26 16:34 <cedk> rhubner: it is a continuous scale | ||
| 2012-07-26 16:39 <lukio> hello, i'm getting the error "<ProtocolError for localhost:8000/test: 500 Internal Server Error>" when i execute a report. | ||
| 2012-07-26 16:40 <rhubner> cedk: continuous but it could limit the number of dates and have buttons that show historic recent and recent | ||
| 2012-07-26 16:40 <rhubner> cedk: did you understand? | ||
| 2012-07-26 16:40 <lukio> When i execute tryton with -v it show this log -> INFO:rpc.request:report.sale.orden_de_terceros.execute(1, '02af0775bfe145a68cf5180410d03ccd', [29], {'model': 'sale.sale', 'id': 29, 'ids': [29]}, {'direct_print': True, 'language': 'es_AR', 'locale': {'date': '%d/%m/%Y', 'thousands_sep': '.', 'grouping': [3, 3, 0], 'decimal_point': ','}, 'language_direction': 'ltr', 'company.rec_name': 'ferrograf', 'email': {'subject': 'Orden de Terceros'}, | ||
| 2012-07-26 16:40 <lukio> 'email_print': False, 'groups': [5, 6, 1, 3, 4, 2, 13, 12, 10, 11, 8, 7, 9], 'employee': None, 'timezone': None, 'company': 1}) | ||
| 2012-07-26 16:40 <lukio> ERROR:common.message:None | ||
| 2012-07-26 16:40 <lukio> any idea? thanks | ||
| 2012-07-26 16:42 <rhubner> cedk: recent and past* | ||
| 2012-07-26 16:43 <rhubner> cedk nicoe: I will make a mockup to examplify, is it help or do you have more ideas? | ||
| 2012-07-26 16:52 <cedk> rhubner: no need to limit the number of dates | ||
| 2012-07-26 16:53 <cedk> lukio: it is possible that your wizard return a BrowseRecord | ||
| 2012-07-26 16:56 <lukio> cedk: my xml have this lines -> | ||
| 2012-07-26 16:56 <lukio> <record model="ir.action.report" id="report_sale_imprenta_terceros"> | ||
| 2012-07-26 16:56 <lukio> <field name="name">Orden de Terceros</field> | ||
| 2012-07-26 16:56 <lukio> <field name="report_name">sale.orden_terceros</field> | ||
| 2012-07-26 16:56 <lukio> <field name="model">sale.sale</field> | ||
| 2012-07-26 16:56 <lukio> <field name="report">sale_imprenta/orden_terceros.odt</field> | ||
| 2012-07-26 16:56 <lukio> <field name="style">sale_imprenta/header_A4.odt</field> | ||
| 2012-07-26 16:56 <lukio> <field name="template_extension">odt</field> | ||
| 2012-07-26 16:56 <lukio> <field name="extension">pdf</field> | ||
| 2012-07-26 16:57 <lukio> <field name="active" eval="True"/> | ||
| 2012-07-26 16:57 <lukio> </record> | ||
| 2012-07-26 16:57 <lukio> | ||
| 2012-07-26 16:57 <lukio> <record model="ir.action.keyword" id="report_sale_imprenta_terceros_keyword"> | ||
| 2012-07-26 16:57 <lukio> <field name="keyword">form_print</field> | ||
| 2012-07-26 16:57 <lukio> <field name="model">sale.sale,-1</field> | ||
| 2012-07-26 16:57 <lukio> <field name="action" ref="report_sale_imprenta_terceros"/> | ||
| 2012-07-26 16:57 <lukio> </record> | ||
| 2012-07-26 16:57 <cedk> lukio: *don't copy/past in chan !* | ||
| 2012-07-26 16:58 <lukio> cedk: sorry. :( | ||
| 2012-07-26 16:58 <cedk> lukio: ok it is a report, so probably an invalid template | ||
| 2012-07-26 16:59 <rhubner> cedk nicoe: http://pastebin.com/rUTJB1ZS | ||
| 2012-07-26 17:00 <nicoe> rhubner: go ahead with a mockup | ||
| 2012-07-26 17:00 <rhubner> nicoe: look at it | ||
| 2012-07-26 17:04 <rhubner> cedk nicoe: every time the button [<] is clicked are shown more (6.7,?) earlier dates. Both the forward and backward button could be active or not if there are more dates to show. | ||
| 2012-07-26 17:05 <nicoe> rhubner: why don't you do it automatically once you're at the start or the end of the scale ? | ||
| 2012-07-26 17:08 <rhubner> nicoe: it can too... the problem is how to represent the current time. Is checkbox is enough? | ||
| 2012-07-26 17:09 <nicoe> rhubner: you mean the selected time ? or the 'today' time ? | ||
| 2012-07-26 17:13 <rhubner> nicoe: today time... imagine if you go past a lot of history dates. the way it is now, the date of "today" is the far right. The user will take to get there again. | ||
| 2012-07-26 17:13 <rhubner> nicoe: A "link" would help it get the current date again. | ||
| 2012-07-26 17:16 <rhubner> nicoe: look at: http://pastebin.com/8Ec90gxS | ||
| 2012-07-26 17:16 <rhubner> nicoe: [Current Date] is a buttom | ||
| 2012-07-26 17:17 -!- lukio(~lukio@186.23.122.88) has left #tryton | ||
| 2012-07-26 17:20 <cedk> rhubner: I think the widget is far from being the primary subject | ||
| 2012-07-26 17:21 <cedk> rhubner: first get the history browsing works | ||
| 2012-07-26 17:21 <cedk> rhubner: you can put a simple datetime widget at first | ||
| 2012-07-26 17:21 <cedk> I'm pretty sure the Scale/Datetime will change a lot over time before having a nice one | ||
| 2012-07-26 17:21 <cedk> but we have first to see if it is working etc. | ||
| 2012-07-26 17:27 <lukio> cedk: i forget to declare the model of the report_name in my .py so it can have the companyreport | ||
| 2012-07-26 17:27 <lukio> cedk: that was the problem | ||
| 2012-07-26 17:30 <rhubner> cedk nicoe: i have lunch now... i'll back in some minutes... | ||
| 2012-07-26 17:32 <rhubner> cedk: the browsing of date history it already works | ||
| 2012-07-26 17:33 <rhubner> cedk: I managed to finish at the end of the day yesterday... only needs reviews | ||
| 2012-07-26 18:00 <rhubner> nicoe: what did you think the buttom "today" and automatically cursor on scale? | ||
| 2012-07-26 18:01 <nicoe> rhubner: I saw your example, it looks ok | ||
| 2012-07-26 18:02 <rhubner> nicoe: I can be working on these changes... | ||
| 2012-07-26 18:02 <nicoe> rhubner: But I would consider to idea of cedk that moving the cursor at the end/beginning of the scale changes the timeframe | ||
| 2012-07-26 18:05 <rhubner> nicoe: ok .. but this is what I proposed + button to display the current data, for ease of use | ||
| 2012-07-26 18:06 <nicoe> rhubner: OK then go for it | ||
| 2012-07-26 18:07 <rhubner> nicoe: but it would be interesting to have some information before or after the scale to alert the user that there are more dates to be seen beyond those shown. | ||
| 2012-07-26 18:09 <rhubner> nicoe: so I suggested the [<] and [>]. Its can be disabled if there are no more. It's just a suggestion | ||
| 2012-07-26 18:15 <nicoe> rhubner: maybe this is cosmetic | ||
| 2012-07-26 18:18 <cedk> rhubner: there will be always a date before a date | ||
| 2012-07-26 18:25 <rhubner> nicoe cedk: I understood :) The last date in scale becomes the first when reloaded? | ||
| 2012-07-26 18:34 <rhubner> cedk nicoe: thanks for ideas... later I'll continue the job | ||
| 2012-07-26 18:47 -!- rhubner(~rhubner@187.112.44.214) has left #tryton | ||
| 2012-07-26 23:26 -!- 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/!