IRC logs of #tryton for Sunday, 2012-04-22 #tryton log beginning Sun Apr 22 00:00:02 CEST 2012
2012-04-22 00:03 <cedk> bvillasanti: is it working?
2012-04-22 00:03 <bvillasanti> cedk: same error
2012-04-22 00:03 <bvillasanti> cedk: remote: abort: acl: user "bvillasanti" not allowed on "trytond/ir/lang.xml" (changeset "5b40bba5a2c3")
2012-04-22 00:04 <bvillasanti> ced: hg push ssh://
2012-04-22 00:05 <cedk> bvillasanti: ok I push also trytond that's just the bootstrap
2012-04-22 00:05 <bvillasanti> cedk: I'm using the same ssh key on other servers without problem.
2012-04-22 00:06 <cedk> bvillasanti: no, it is just that there are default rules for translators
2012-04-22 00:06 <cedk> bvillasanti: but the first commit in tryton and trytond needs to change files that normally translators doesn't have
2012-04-22 00:07 <bvillasanti> cedk: I understand
2012-04-22 00:07 <cedk> bvillasanti: it is done
2012-04-22 00:08 <cedk> bvillasanti: you can try modules
2012-04-22 00:09 <bvillasanti> cedk: good, now push account and tell you
2012-04-22 00:11 <cedk> bvillasanti: by the way, don't you known if you know but you can speed up hg+ssh communication by creating a master ssh connection
2012-04-22 00:12 <bvillasanti> cedk: I didn't knew that
2012-04-22 00:13 <cedk> bvillasanti: otherwise hg will do a connection for each repo/command
2012-04-22 00:13 <cedk> bvillasanti: I don't know how is the connection from Argentina?
2012-04-22 00:16 <bvillasanti> cedk: we have no speed problems
2012-04-22 00:17 <bvillasanti> cedk: I just push account module
2012-04-22 00:17 <cedk> bvillasanti: good
2012-04-22 00:17 <bvillasanti> cedk: I continue, thank you very much
2012-04-22 00:18 <cedk> bvillasanti: no need to put issue in each translation commit
2012-04-22 00:18 <bvillasanti> cedk: ok
2012-04-22 00:18 <cedk> bvillasanti: and perhaps add that it is for argentina spanish
2012-04-22 00:20 <cedk> bvillasanti: also you can compress the ssh connection
2012-04-22 00:21 <bvillasanti> cedk: so, Add Argentina spanish translation
2012-04-22 00:21 <bvillasanti> cedk: compress the ssh connection, how?
2012-04-22 00:22 <cedk> bvillasanti: -C
2012-04-22 00:22 <cedk> bvillasanti: or in ssh config: Compression yes
2012-04-22 00:23 <bvillasanti> cedk: ok
2012-04-22 04:16 -!- rhubner(~rhubner@ has left #tryton
2012-04-22 04:59 <__efx__> hi, I installed tryton.
2012-04-22 04:59 <__efx__> and I want to use part of it in a web app
2012-04-22 05:00 <__efx__> I don't know whether using proteus to communicate with the tryton server is better than for example using tryton as a module of django
2012-04-22 05:02 <__efx__> if somebody has some experience to share I would be really greatfull :)
2012-04-22 07:59 -!- Mayank(~mayank@ has left #tryton
2012-04-22 13:16 <__efx__> Hello
2012-04-22 13:16 <__efx__> Is smbdy there ?
2012-04-22 13:31 <bechamel> __efx__: yes
2012-04-22 13:37 <__efx__> oh great :)
2012-04-22 13:37 <__efx__> do you know maybe something about the development of proteus.js ?
2012-04-22 13:37 <__efx__> because I would like to develop an web interface to tryton for some of my customers
2012-04-22 13:38 <__efx__> and I don't know really what is the best way to handle that
2012-04-22 13:38 <__efx__> I have time and I m payed, so I can code something and share :)
2012-04-22 13:39 <bechamel> __efx__: I have updated the codereview, let me find the url
2012-04-22 13:39 <bechamel> __efx__:
2012-04-22 13:40 <__efx__> bechamel: thank you
2012-04-22 13:43 <__efx__> I downloaded the last patch set but I don't know why I cannot connect to my trytond server (the console.log('connected'); does not appear on the opera console ?
2012-04-22 13:44 <bechamel> __efx__: first you must change the tryton config file to tell him where to fetch the files
2012-04-22 13:45 <bechamel> __efx__: its the "jsondata_path" option
2012-04-22 13:46 <__efx__> but the js are only client side right ? so why could I not simple launch them outside of the jsondata_path ?
2012-04-22 13:46 <bechamel> __efx__: oh and of course: the login/password/db is still hard-coded in proteus-test.js so you must change it
2012-04-22 13:47 <bechamel> __efx__: this tells the server which directory is served when a browser connects
2012-04-22 13:49 <__efx__> but should it have the same effect as launching it outside of the jsondata_path ?
2012-04-22 13:52 <bechamel> __efx__: good question :)
2012-04-22 13:54 <bechamel> __efx__: currently, there are no way to configure which url to query in proteus.js, but it is not difficult to add it
2012-04-22 13:55 <bechamel> __efx__: the second issue is cors, but this is handled outside proteus.js itself
2012-04-22 13:57 <__efx__> is the work of Cedric Krier on a wsgi_app for a tryton_web app a good starting point for a CORS support
2012-04-22 13:57 <__efx__> ?
2012-04-22 14:02 <bechamel> __efx__: the support of the wsgi api, allows to use existing tools, so it may ease the developement/integration of some features, but I don't see any obvious solution for cors
2012-04-22 14:02 <bechamel> __efx__: is it a problem for you to serve the static files from the tryton server ?
2012-04-22 14:06 <__efx__> ok excellent I got something (I was launching the tryton server like that "trytond /path/to/config_file" without the -c :( )
2012-04-22 14:06 <__efx__> the test worked and I got beautiful green boxes
2012-04-22 14:07 <__efx__> some I think everything is ok
2012-04-22 14:07 <bechamel> __efx__: great
2012-04-22 14:08 <__efx__> know I think I can use proteus.js pretty much like the python proteus library to talk with the server ?
2012-04-22 14:08 <cedk> __efx__: but what will be the usage of your web interface?
2012-04-22 14:09 <bechamel> __efx__: the idea is the same but the api is not the same, it would have been too difficult to have the exact api with javascript
2012-04-22 14:10 <__efx__> ok so I can do the same thing than with proteus but not exactly in the same way
2012-04-22 14:10 <__efx__> during my use I think I will make a tutorial
2012-04-22 14:10 <bechamel> __efx__: if it works you can try it in your console: User = Proteus.Model.get('res.user'); all_users = User.find([]);
2012-04-22 14:11 <bechamel> then users.each(function(pos, user) {console.log(});
2012-04-22 14:13 <__efx__> do you mean on a javascript console of the webbrowser ?
2012-04-22 14:14 <__efx__> actually I work with some doctors and they want their patient to access their medical information from the net
2012-04-22 14:15 <cedk> __efx__: so you can use the client
2012-04-22 14:15 <cedk> __efx__: net != browser
2012-04-22 14:15 <bechamel> __efx__: yes
2012-04-22 14:15 <__efx__> yes I know but for the client it would be better to have a web page without need to install a desktop app or something, what do you think ?
2012-04-22 14:16 <__efx__> in this case the client is a patient
2012-04-22 14:16 <cedk> __efx__: so I don't think you must use proteus.js but generate static pages
2012-04-22 14:17 <cedk> __efx__: because patient are not users of the system, at least I guess
2012-04-22 14:19 <__efx__> ok so more something like a web server that makes call to a trytond server through proteus python lib ?
2012-04-22 14:19 <__efx__> for example a django-python web server that communicates with a trytond server through proteus ?
2012-04-22 14:19 <cedk> __efx__: something like
2012-04-22 14:20 <bechamel> __efx__: the doctors just need to read the data, or they must also edit them ?
2012-04-22 14:20 <__efx__> at the end doctors must also be able to edit
2012-04-22 14:21 <cedk> bechamel: it is not the doctors but the patients
2012-04-22 14:21 <__efx__> also the patients
2012-04-22 14:21 <__efx__> both actually
2012-04-22 14:21 <cedk> __efx__: what the patient will edit his one folder?
2012-04-22 14:21 <cedk> s/one/own/
2012-04-22 14:23 <__efx__> the patient is actually owner of the information that the doctors has from him so yes it should be able to edit the information but the changes should be loggued so that doctor will not loose crucial information
2012-04-22 14:25 <__efx__> I will look deeper at the integration with django but actually this example does not use proteus.js ? why is it ?
2012-04-22 14:26 <__efx__> It would be logical to use proteus, in the sense that we want to keep the server running separately maybe even on another server...
2012-04-22 14:27 <bechamel> __efx__: the django example render the templates server-side
2012-04-22 14:28 <bechamel> __efx__: the idea with proteus.js is to fetch only data from server and generate the dom in the browser
2012-04-22 14:28 <__efx__> sorry I made a mistake in the message at [14:26] I was talking about proteus python lib
2012-04-22 14:29 <__efx__> not proteus.js
2012-04-22 14:30 <bechamel> __efx__: actually the example was written before the creation of proteus
2012-04-22 14:33 <__efx__> ok I will try to make the same using proteus then
2012-04-22 14:35 <__efx__> If I understand well, proteus.js is better suited for example for a smart phone app
2012-04-22 14:35 <__efx__> ?
2012-04-22 14:38 <cedk> __efx__: it doesn't use proteus because it wants an other transaction management
2012-04-22 14:38 <bechamel> __efx__: it is better suited when data must be edited
2012-04-22 14:39 <cedk> __efx__: the fact that the patient owns his information doesn't mean he must have edit access on it
2012-04-22 14:40 <cedk> __efx__: more over how to you identify a patient?
2012-04-22 14:43 <__efx__> thats crucial question actually, but since I am using tryton the best is to give them a tryton account no ?
2012-04-22 14:44 <cedk> __efx__: how much patient do you expect to have?
2012-04-22 14:44 <__efx__> 10 doctors for now each of them having 200 patients or so.. so 2000
2012-04-22 14:45 <cedk> __efx__: only 200 patients per doctor in all the life of the application, I find it for few
2012-04-22 14:45 <__efx__> that's true, so lets say 20000
2012-04-22 14:45 <__efx__> :)
2012-04-22 14:46 <__efx__> do you think trytond will handle that ?
2012-04-22 14:46 <cedk> __efx__: I think you are going in the wrong direction, I guess you want to provide to patient the similar right as we got here in belgium which is the right to correct info data about us
2012-04-22 14:46 <__efx__> yes exactly that's what I want
2012-04-22 14:47 <cedk> __efx__: so for me, it looks more like: if the user ask for access, give him one readonly, if he wants to correct it, do it via a form and it will be apply after validation
2012-04-22 14:48 <cedk> __efx__:and the access to info could be managed with a website like the django example
2012-04-22 14:48 <cedk> __efx__: so in any case, the patient become a real user of trytond
2012-04-22 14:49 <__efx__> ok so I separate the problem in to distinct one
2012-04-22 14:49 <cedk> __efx__: different usages = different solution
2012-04-22 14:49 <cedk> ACTION bbl
2012-04-22 14:49 <__efx__> visualization through django and modification using a dom application that uses proteus.js for example ?
2012-04-22 14:50 <__efx__> Is "having hall patient becoming real user of trytond" a performance issue ?
2012-04-22 14:51 <bechamel> __efx__: proteus.js gives direct acces to the server, so you must be sure that all the acces rights are corrects, if not the server may leak important data.
2012-04-22 14:52 <bechamel> __efx__: otoh you can generate static pages, one per patient, and give each patient acces to his page
2012-04-22 14:52 <bechamel> __efx__: then if he want to correct data he may send an email
2012-04-22 14:53 <bechamel> __efx__: it's easier to secure
2012-04-22 14:53 <__efx__> yes that's true !
2012-04-22 14:54 <__efx__> but what do you think in using two authentifications layer for the patient one internal to trytond and one externally
2012-04-22 14:55 <__efx__> maybe only one "special" tryton user that can access only patient information
2012-04-22 14:55 <bechamel> __efx__: what is your idea ?
2012-04-22 14:56 <__efx__> and another authentification layer to restrain the access to only one specific patient
2012-04-22 14:57 <bechamel> __efx__: who will be the "special" user ? a doctor ?
2012-04-22 14:57 <__efx__> actually can I not fix the right I give to the patient in tryton so that I am sure that patient can do only what I allowed them to do ?
2012-04-22 14:59 <__efx__> it would be a user that have access only to patients information..
2012-04-22 15:00 <__efx__> ...but It makes no sense to have two authentification layers :-/
2012-04-22 15:00 <bechamel> __efx__: if you use proteus.js, you must write at least one access rule per model (to forbid them to read them), and then for each model containing data you want to show them write a rule to allow the user/patient to see only what is related to him
2012-04-22 15:01 <bechamel> __efx__: if you create one static page per patient, it's the other way around: you create a page with only the data you want to show, and as it is static no risk of forgeting an acces rule
2012-04-22 15:04 <__efx__> But If the patient decide to install the tryton client and connect to the trytond server the rule defined in proteus.js will not apply right ?
2012-04-22 15:05 <bechamel> __efx__: from a data point of view, proteus.js is the same has the tryton client
2012-04-22 15:06 <bechamel> __efx__: both of them acces data through json-rpc
2012-04-22 15:06 <bechamel> __efx__: and acces right are enforced by the server
2012-04-22 15:07 <bechamel> so if you give acces to a patient with proteus.js, he wil have acces to the same stuff as if you gave him the tryton client
2012-04-22 15:08 <__efx__> ok then why do we need no define access write, just for a verification purpose in the case the right are not setted as they should ?
2012-04-22 15:08 <__efx__> we need *to...
2012-04-22 15:10 <__efx__> are you from the french part of belgium because I am from Lausanne so we could also talk in french :) ?
2012-04-22 15:10 <bechamel> __efx__: yes, if you want to speak french just go to #tryton-fr
2012-04-22 18:22 <sharoonthomas> cedk: ping
2012-04-22 19:54 <yangoon1> cedk hi, should I run the backports releases together with 2.4 release?
2012-04-22 22:42 <cedk> yangoon1: I think it is better to do it one or 2 weeks after
2012-04-22 22:42 <cedk> sharoonthomas: pong

Generated by 2.17.3 by Marius Gedminas - find it at!