[01:59] <tt33l3r> I'm having a problem with the "Keep Aligned" setting on gnome changing back to set on every reboot. Anyone know how to fix this?
[15:49] <manusheel> kandarpk: Hi Kandarp.
[15:49] <manusheel> Around?
[15:50] <kandarpk> manusheel sir: hello sir.
[15:50] <manusheel> kandarpk: How is the activity development coming along?
[15:51] <kandarpk> manusheel sir: finding including collaboration a bit difficult
[15:52] <manusheel> kandarpk: ok.
[16:08] <ishan> kandarpk, hi sir
[16:53] <ishan> kandarpk, sir have you read the file??
[16:59] <kandarpk> ishan: yeah, most of it.
[17:02] <ishan> kandarpk, sir is it fine
[17:02] <kandarpk> ishan: dont kno myself
[17:02] <ishan> can you also provide pointers to me on the part where i have added ???
[17:10] <kandarpk> alsroot: around ?
[17:19]  * ishan is away
[17:28]  * ishan is back
[17:34] <alsroot> kandarpk: yup
[17:36] <kandarpk> alsroot: can we synchronise the text in a textbox of a shared activity ?
[17:37] <alsroot> kandarpk: you mean concurrent editing?
[17:38] <kandarpk> alsroot: no, that might be tough
[17:38] <kandarpk> alsroot: one to type message, other one to display
[17:38] <alsroot> kandarpk: see how chatbox.py does it in Speak actiivty
[17:39] <kandarpk> alsroot: Ok.
[17:39] <alsroot> kandarpk: in anycase it is derivative workflow, you can do anything you want using basic sharing features
[17:40] <alsroot> kandarpk: btw hellomesh does similar(as I can remember) things but in more simple way
[17:41] <kandarpk> alsroot: hellomesh uses hippo.CanvasBox
[17:41] <kandarpk> which I was not able to add in the VBox
[17:41] <alsroot> kandarpk: hippo is used only for UI stuff, sharing features don't depend on it
[17:42] <alsroot> kandarpk: just do what hellomesh does(in case of sharing) but w/o hippo
[17:42] <kandarpk> alsroot: yeah, I was trying to place a textbox in its place
[17:43] <alsroot> kandarpk: btw chatbox.py is also hippo based
[17:43] <kandarpk> alsroot: ok.
[17:50] <kandarpk> alsroot: thanks, just removing hippo seems to work
[17:50] <alsroot> yw
[18:01] <neeraj> hi alsroot, around
[18:01] <neeraj> ?*
[18:01] <alsroot> neeraj: hi
[18:04] <neeraj> alsroot: for bug https://bugs.launchpad.net/ubuntu/+source/sugar-0.88/+bug/617582, I asked on sugar-devel as u suggested. And I got a different suggestion for this -> http://comments.gmane.org/gmane.linux.laptop.olpc.sugar/24679
[18:04] <ubot2> Launchpad bug 617582 in sugar-0.88 (Ubuntu) "When opening the control panel some icons are cut off . (affects: 2) (heat: 338)" [High,In progress]
[18:09] <alsroot> neeraj: I see, it is up to you what way to choose, you can follow the way what was suggested by email
[18:10] <alsroot> but /me is not sure what it was meant, since we have a grid of components, calculating width for cells/columns
[18:10] <neeraj> alsroot: 1. I don't think removing the text and only displaying the text will solve the purpose.
[18:13] <alsroot> neeraj: well, I guess email wasn't about removing text labels
[18:14] <neeraj> because the text are not that long as comparison to icon size. 6 is too big for of 800*600.
[18:14] <alsroot> neeraj: at the end, problem could be split into two parts, just fixing ugly issue with cut CP, and implement it in right way
[18:15] <neeraj> alsroot: Ok. He meant that icon and text should be of same width.
[18:17] <alsroot> neeraj: or you can apply your (fast)patch to ubuntu package, and start thinking about rigth implementation to push it to upstream
[18:18] <neeraj> alsroot: ok. Will keep track of this bug and send the patch (both text wrapping and column size)to sugar upstream later.
[18:19] <neeraj> for the time being first sending the column patch on ubuntu.
[18:26] <kandarpk> alsroot: can the timeout icon be removed from notifyAlert ?
[18:27] <alsroot> kandarpk: but you can use other alert classes or create new one
[18:27] <kandarpk> alsroot: hmmmm, ok.
[18:41] <kandarpk> alsroot: great :)
[18:42] <kandarpk> alsroot: how can I extract the name of person/computer on which sugar is running ?
[18:42] <kandarpk> alsroot: I want to use that while passing messages
[18:44] <alsroot> kandarpk: use sugar-toolkit/src/sugar/profile.py's methods
[18:44] <alsroot> e.g. get_nick_name
[18:59] <kandarpk> alsroot: wow. Just what I was looking for
[18:59] <kandarpk> alsroot: thanks again.
[18:59] <alsroot> np
[19:31] <thangam_arun> Hello All
[19:32] <thangam_arun> i would like to build a ubuntu with sugar interface..
[19:33] <thangam_arun> also with Tamil language
[19:33] <thangam_arun> Can you please some one guide on this
[20:10] <kandarpk> neeraj: around ?
[20:51] <manusheel> neeraj: Hi Neeraj.
[20:51] <manusheel> Around?
[20:52] <manusheel> kandarp: Hi kandarp.
[20:52] <kandarpk> manusheel sir: hello sir
[20:53] <manusheel> kandarpk: The activity seems to have covered up all the use-cases, right?
[20:53] <neeraj> kandarpk: hi..
[20:53] <kandarpk> manusheel sir: it isn't working properly yet
[20:54] <kandarpk> manusheel sir: while passing messages
[20:54] <manusheel> kandarpk: Right, That is the collaboration part, which has issues.
[20:55] <manusheel> kandarpk: Right? Can you elaborate on the problems?
[20:55] <neeraj> manusheel sir, Yes. We tested it, We are able to join the activity but the message is not showing to other person
[20:55] <kandarpk> manusheel sir: the code needs to be updated
[20:55] <manusheel> kandarpk: OK.
[20:55] <manusheel> neeraj: Sure.
[20:56] <manusheel> kandarpk , neeraj: The activity works well, in single user mode, right?
[20:56] <kandarpk> manusheel sir: are users of hello mesh able to communicate ?
[20:56] <kandarpk> manusheel sir: yes sir, for single user, it works ok
[20:57] <manusheel> kandarpk: I am not sure about the hello mesh activity. I would better recommend to have a look at Memorize or Turtle Art.
[20:57] <manusheel> kandarpk: Great. Glad to hear that for a single user the activity works well.
[20:57] <kandarpk> manusheel sir: ok sir.
[20:57] <kandarpk> I would like neeraj to try it out and see if he understands anything
[20:58] <manusheel> kandarpk: k.
[20:58] <neeraj> manusheel: yes,.. in single user mode its working fine.
[20:58] <kandarpk> neeraj: more than working, are you able to understand its purpose ?
[20:58] <manusheel> neeraj: Great.
[21:00] <kandarpk> alsroot: around ?
[21:01] <alsroot> kandarpk: yup
[21:01] <kandarpk> alsroot: can users of hello mesh send messages to each other ?
[21:02] <alsroot> kandarpk: didn't see into hellomesh code, but any sharing between users is sending messages between them
[21:02] <kandarpk> alsroot: definitely. thanks.
[21:03] <alsroot> kandarpk: you can search on wiki.laptop.org and wiki.sugarlabs.org, there are bunch of docs about sharing, e.g. http://wiki.laptop.org/go/Activity_sharing
[21:04] <kandarpk> alsroot: one general question
[21:05] <kandarpk> alsroot: is the presence service being removed from sugar-0.90 ?
[21:05] <alsroot> kandarpk: yup, shell and activities(via sugar-toolkit) use telepathy-mission-control
[21:05] <alsroot> ..except etoys
[21:06] <alsroot> but from activity devs nothing was changed, they just use sugar-toolkit API
[21:07] <kandarpk> alsroot: OK.
[23:12] <manusheel> alsroot: Hi Aleksey.
[23:12] <manusheel> Around?
[23:12] <alsroot> manusheel: hi
[23:13] <manusheel> alsroot: Aleksey, wish to ask you on how we can set the owner to a SEETA team member at bugs.sugarlabs.org.
[23:13] <manusheel> alsroot: Do we need certain privileges for the same?
[23:14] <manusheel> alsroot: Wish to assign certain upstream issues of Sugar to our team members. They have already been working on it.
[23:15] <alsroot> manusheel: in track, only one person can be an owner for component
[23:15] <alsroot> manusheel: do you want to create seeta component on bugs.sl.o?
[23:16] <manusheel> alsroot: Right.
[23:16] <alsroot> manusheel: why will be an owner?
[23:17] <manusheel> alsroot: You can set me as the owner for these issues - manusheel is my username.
[23:17] <manusheel> alsroot: I'll assign them to our team members by adding them in the CC.
[23:17] <alsroot> manusheel: manu on laptop.org?
[23:18] <manusheel> alsroot: I need to check on that. Ok. I can even create a common account of SEETA and get back to you in a minute.
[23:18] <manusheel> alsroot: The bugs that we are working on can be assigned to that account.
[23:22] <manusheel> alsroot: Just registered a common account. It is dev@seeta.in
[23:22] <manusheel> alsroot: The bugs assigned to our team will be owned by the e-mail "dev@seeta.in" and username "seeta".
[23:23] <alsroot> manusheel: done, create SEETA component
[23:23] <alsroot> *created
[23:24] <manusheel> alsroot: Now, can we change owners and assign bugs falling in the "New" category to ourselves.
[23:24] <alsroot> manusheel: there is "reassign" option in already created bug
[23:25] <alsroot> *"reassign  to"
[23:25] <manusheel> alsroot: Great. Thanks Aleksey.
[23:25] <alsroot> np
[23:30] <manusheel> alsroot: Is Sascha Silbe the moderator for bugs.sugarlabs.org? When I re-assigned the issue to Anurag, it said that the bug will have to flow through Sascha Silbe.
[23:31] <alsroot> manusheel: I have admin privileges as well but not confident about track workflows
[23:31]  * alsroot looks
[23:32] <alsroot> manusheel: what ticket number you meant?
[23:35] <manusheel> alsroot: I mean bug #2195
[23:36] <ubot2> Launchpad bug 2195 in gnome-panel (Ubuntu) (and 1 other project) "new menu item not listed if .desktop unpacked before the TryExec binary (dups: 1) (heat: 1)" [Low,Triaged] https://launchpad.net/bugs/2195
[23:36] <manusheel> meant*
[23:36] <manusheel> alsroot - http://bugs.sugarlabs.org/ticket/2195
[23:38] <alsroot> manusheel: try once more
[23:41] <alsroot> manusheel: there is no need, owner was already changed
[23:43] <manusheel> alsroot: Sure, Aleksey.Thank you.
[23:44] <alsroot> np
[23:44] <manusheel> alsroot: It seems there is a lead time associated with change of owner, which is fine.