[04:01] <lfaraone> ls
[14:39] <manusheel> neeraj: Hi Neeraj.
[14:40] <neeraj> manusheel sir : Hi
[14:41] <manusheel> neeraj: Please have a word with Aleksey on the two patches and the GSM issue.
[14:42] <manusheel> alsroot: Around?
[14:55] <dipankar> dfarning, hello
[14:55] <dfarning> dipankar, good morning
[14:55] <dipankar> dfarning, good morning :)
[14:56] <dipankar> dfarning, you are still at Paraguay?
[14:57] <dfarning> dipankar, one more week then back to my own home.
[14:57] <dipankar> dfarning, :)
[14:59] <dipankar> dfarning, Did you get a chance to see the mail that I sent regarding the fullscreen bug?
[15:01] <dfarning> I scanned it.  but I try to stay out of technical discussions:)  those are better left to developers who know what they are doing.
[15:01] <dipankar> dfarning, :)
[15:01] <dipankar> alsroot, !ping!
[15:01] <dfarning> dipankar, ^^ I suggesting asking alsroot how to proceed.
[15:02] <dipankar> dfarning, I am on it.
[15:03] <dfarning> dipankar, thanks.
[15:09] <dipankar> alsroot, around?
[15:09] <dipankar> alsroot, I need your help on the fullscreen bug.
[15:10] <dipankar> neeraj, around?
[15:12] <dipankar> bernie, around?
[15:14] <manusheel> dipankar, neeraj is not around.
[15:14] <manusheel> He'll be back in 15 mins.
[15:14] <dipankar> manusheel, ohk sir
[15:14] <manusheel> Informed me.
[15:14] <dipankar> manusheel, I am at #suagr
[15:14] <dipankar> *#sugar
[15:14] <manusheel> Ok, great.
[15:15] <alsroot> dipankar: pong
[15:16] <dipankar> alsroot, I am at #sugar
[15:17] <alsroot> manusheel: pong as well
[15:17] <manusheel> alsroot: Hi Aleksey. Good morning.
[15:18] <alsroot> manusheel: morning
[15:18] <bernie> dipankar: yup
[15:19] <bernie> (not for long, I'm packing up)
[15:23] <dipankar> bernie, where are you heading to?
[15:24] <dipankar> manusheel, Sir, tomeu has again some other opinions
[15:24] <dipankar> manusheel, I need some help :(
[15:26] <dipankar> manusheel, Sir, what tomeu is asking is correct I guess. Why are we actually trying to remove all those errors in the shell.log first place?
[15:26] <dipankar> alsroot, did you get a chance to go through my mail regarding the 'fullscreen-new approach'
[15:27] <dipankar> alsroot, I found that at exactly 800x600, due to task panels and window title bar of xephyr, there is some cropping in emulator
[15:29] <alsroot> dipankar: the original issue that 800x600 is not work exactly is that issue w/ scaling, /me is looking into the code..
[15:33] <bernie> dipankar: Uruguay
[15:34] <bernie> dipankar: I'll work with the people of Plan Ceibal for one week, more or less
[15:44] <dipankar> alsroot, I set the condition for fullscreen to <= 800x600. from < 800x600
[15:45] <dipankar> on my system
[15:46] <dipankar> bernie, ohk. :)
[15:46] <alsroot> dipankar: heh, "<=" that's an obvious bug
[15:47] <dipankar> alsroot, why?
[15:47] <alsroot> dipankar: I mean its obviously a bug :)
[15:47] <alsroot> dipankar: could you create a ticket on bugs.sl.o?
[15:47] <dipankar> alsroot, I mean, to do away with the cropping part, I modified the code a bit
[15:48] <dipankar> alsroot, ok sure
[15:48] <dfarning> dipankar, are you looking at the gsm error bug?
[15:48] <dipankar> dfarning, just completed with the fullscreen bug.
[15:48] <dipankar> dfarning, I think we are slowly arriving at a conclusion.
[15:48] <alsroot> dipankar: but stop, there is already ticket for such issue, /me is looking
[15:49] <dipankar> alsroot, sure
[15:49] <dfarning> dipankar, the problem with the gsm bug is _not_ that something is being reported it is the fact that the message is called an 'error'.
[15:50] <dipankar> dfarning, ohk.
[15:50] <dipankar> dfarning, so, I think what tomeu is saying is correct.
[15:50] <dfarning> dipankar, to fix the issue all you have to do is downgrade the message from error something lower such as warning.
[15:50] <dipankar> * How is it relevant to user?
[15:51] <dipankar> dfarning, ok. But when I asked about gsm issue,^^ tomeu asked me the above question
[15:53] <dfarning> dipankar,  It is relevant to developers... because error means "holy shit some really bad just happened", warnings just provid information to the developer about what is happening.
[15:53] <dfarning> dipankar, where is the code?
[15:53] <dipankar> dfarning, got your point.
[15:53] <dipankar> dfarning, /usr/share/pyshared/jarabe/model/network.py, line 696
[15:53] <alsroot> dipankar: in fact there are two related bugs, http://bugs.sugarlabs.org/ticket/1396 and http://bugs.sugarlabs.org/ticket/1747
[15:54] <alsroot> dipankar: but they are not about the same.. so it could be new ticket then..
[15:54] <alsroot> *exactly the same
[15:55] <dipankar> alsroot, ohk. But I got some feeling that they are discussing about cropping only :P
[15:57] <dipankar> alsroot, I filing a new ticket.
[15:58] <neeraj> alsroot: for the control panel icon-cut off issues, I have reduced the column size to 3. At present there are nine items in control panel and all are visible with appropriate distance between various icons.
[15:59] <alsroot> neeraj: I think, it might be better to calculate optimal columns count according to current screen resolution i.e. screen sizes could be various from 800x600 to 1400+
[15:59] <neeraj> alsroot: do you any any other solution for this bug https://bugs.launchpad.net/ubuntu/+source/sugar-0.88/+bug/617582
[16:01] <neeraj> alsroot: Ok.
[16:03] <dipankar> alsroot, created the new ticket
[16:03] <neeraj> dipankar: Can u tell me how to check in which resolution sugar is running. Ok default is 800X600. But what if some one run it in higher resolution then this
[16:03] <dipankar> * its gone for moderation
[16:04] <dipankar> neeraj, for sys resolutions higher than 800x600, the emulator will run in window mode only. but the resolution of emulator will be 800x600
[16:04] <alsroot> neeraj: also, especially on large screens, it could be useful to not expand gtk.Table cells vertically (see yoptions argument on http://library.gnome.org/devel/pygtk/stable/class-gtktable.html#method-gtktable--attach)
[16:05] <dipankar> alsroot, I am off for dinner. will contact you after I get back. Thanks.
[16:05]  * dipankar is off for dineer
[16:05] <dipankar> *dinner
[16:05] <dfarning> dipankar, try grepping though the file for other occourances of the logging function
[16:06] <manusheel> dfarning: Thank you for the pointer.
[16:06] <manusheel> Will share it with Dipankar
[16:06] <manusheel> when he is back from dinner.
[16:06] <dfarning> manusheel,  I would suggest downgrading exception to debug.
[16:06] <manusheel> dfarning: Ok, sure.
[16:07] <dfarning> manusheel, thanks
[16:08] <neeraj> alsroot: Ok. When i ran sugar in 1068x800 then the control panel looks like this http://imgur.com/BsQIr.png
[16:10] <neeraj> alsroot: Can you suggest me how can I detect in which resolution a user is running sugar-emulator.(even when he is explicitly specifying the emulator resolution using sugar-emulator -i AxB)
[16:11] <kandarpk> alsroot: I was thinking of developing an application like visual basic in sugar.
[16:11] <kandarpk> which could provide application developers some idea of the tools sugar modules provide.
[16:12] <alsroot> neeraj: just something like "screen_width / <assumed-cell-width-eg-GRID_CELL_SIZE*3>
[16:12] <kandarpk> alsroot: but as sugar is targeted at children, will that be useful ?
[16:13] <kandarpk> dfarning: Hi.
[16:19] <alsroot> kandarpk: but why not, on big screens hardcoded 3x3 looks overkill
[16:19] <lucian> kandarpk: why visual basic? Sugar already uses python, a language superior by any measure
[16:20] <lucian> kandarpk: do you mean a GUI building tool?
[16:20] <kandarpk> lucian: yes, exactly
[16:20] <lucian> kandarpk: there are two activities geared towards writing code, Pippy and Develop
[16:20] <manusheel> kandarpk: Try develop.
[16:20] <lucian> and there's Glade for building GTK GUIs
[16:21] <alsroot> neeraj: but anyway, better to raise this question (about how many cells should be keeping in mind different screen sizes) should be risen on sugar-devel@, post an email w/ tag [DESIGN] in subject
[16:21] <kandarpk> lucian: Ok.
[16:21] <lucian> so you could integrate glade in Develop or sugarise glade
[16:21] <kandarpk> lucian: great idea.
[16:21] <lucian> alsroot: neeraj: android has the same problem with phone vs tablet
[16:22] <kandarpk> lucian: what I was looking for was instead of developers reading code, they should be able to see the GUI the sugar modules provide.
[16:22] <dfarning> kandarpk, and also check out turtle art, etoys, and scratch.  they are visual languages for helping kids learn to program visually.
[16:22] <kandarpk> lucian: will studying develop help ?
[16:22] <lucian> kandarpk: it might. also have a look at Pippy
[16:23] <neeraj> alsroot: Ok. I was also confused what will be better.
[16:23] <neeraj> *better option
[16:23] <kandarpk> dfarning, lucian: Ok.
[16:23] <lucian> dfarning: i think kandarpk is looking for something to transition developers to writing sugar activities. am i right?
[16:24] <lucian> or something to make writing activities easier?
[16:24] <kandarpk> lucian: I want to let them know what modules sugar already have
[16:25] <dfarning> neeraj, the issue for you is that the the screen resolution can vary depending on the hardware.  so you will need to detect the screen resolution on the fly and determine how many columns will fit in the available space.
[16:25] <kandarpk> lucian: yes, that will make writing activities easier
[16:26] <lucian> dfarning: i think the correct way to do it would be to figure out the screen size from DPI and resolution
[16:27] <dfarning> lucian, proper implementation is beyond me:(
[16:27] <neeraj> dfarning: Sure, That can be done. Modifying code and testing.
[16:36] <lfaraone> alsroot: how's your python
[16:37] <neeraj> dfarning: alsroot setting Max Column to gtk.gdk.screen_width()/200 is solving the problem.
[16:39] <dfarning> neeraj, that 'smells correct'.... but I don't know the implementation nuances.
[16:40] <neeraj> dfarning: same here. :)
[16:41] <lfaraone> lucian: perhaps you'd be a person to ask: I'm trying to have files that match "*.txt" and "aiml/self-test.aiml" installed in the same directory of a package as the python source itself. My naieve attempts wrangling setup.py have ended us with a subdirectory "aiml/aiml/self-test.aiml" in the resulting package.
[16:42] <lucian> lfaraone: i don't know setuptools
[16:42] <lucian> i don't think i know more than you here
[16:48] <alsroot> lucian: Re: how's your python -- not so bad :)
[16:48] <lucian> alsroot: that was lfaraone asking :)
[16:48] <lfaraone> alsroot: how's your setuptools-fu, I should ask :P
[16:49] <alsroot> lfaraone: didn't use such stuff
[16:50] <lfaraone> alsroot: so you couldn't help me figure out why http://git.debian.org/?p=collab-maint/python-aiml.git;a=blob;f=setup.py;h=9c7b5708ea9d53789e2d52ae3965c40be003725f;hb=HEAD is not installing package data ... in the package, right?
[16:50] <alsroot> neeraj: sugar uses scaling (to support different dpi), so better to avoid direct numbers and use style.zoom(), but in this particular case, in my mind better to count in style.GRID_CELL_SIZE
[16:51] <alsroot> lfaraone: sorry, can't help here
[16:58] <alsroot> neeraj: btw, while testing your code, use "-s 100" and "-s 72" as well for change scalling
[16:59] <alsroot> ..use w/ sugar-emulator command
[17:04] <neeraj> alsroot: I am not sure I should I co relate GRID_CELL_SIZE with screen resolution. By hit and trial I set up Column to style.GRID_CELL_SIZE/15. But when I ran sugar-emulator in different resolution, then the number of columns were not changing at all/
[17:08] <neeraj> alsroot: Ok. scaling is also an issue. I tried -s 100, then the effective size of control panel reduced a lot as comparison to 3X3 icon grid, when I ran in in 800X600.
[17:11] <neeraj> Also, I think you know it but still let me tell u again what we are trying to do. When we run sugar in default mode, then the  *all* control panel icons are not visible screen, but we do have a horizontal and vertical scroll bar .
[17:12] <alsroot> neeraj: GRID_CELL_SIZE is referencing to http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Sugar_Interface/Layout_Guidelines, so w/ "style.GRID_CELL_SIZE/15" you have too many columns :)
[17:13] <neeraj> alsroot: strange. I again set column to style.GRID_CELL_SIZE/15. The resultant column size is still 3.
[17:13] <alsroot> neeraj: my idea was just calculating columns count in advance(instead of hardcoded "5")
[17:15] <alsroot> ..something like <screen-width> / (style.GRID_CELL_SIZE * 3)
[17:16] <neeraj> alsroot: Ok.  Lemme try it again . :)
[17:21] <neeraj> alsroot: Ok. setting column to <screen-width> / (style.GRID_CELL_SIZE * 3) is solving the problem related to resolution.
[17:23] <neeraj> * dinner.
[18:10] <ankur> hi alsroot  :)
[18:12] <kandarpk> alsroot: around ?
[18:18] <dipankar> dfarning, I got your message. :) Thanks to Manu sir.
[18:18] <dfarning> dipankar, does it make sense?
[18:18] <dipankar> dfarning, yeah. We want that message to appear as warning and not as Error
[18:19] <dfarning> dipankar, +1
[18:19] <dipankar> because, developers kind of freak out on errors
[18:19] <dipankar> :P
[18:19] <dipankar> and as a convention they work more on removing errors
[18:21] <dipankar> dfarning, then I shall set it from exception to debug
[18:21] <dfarning> dipankar, +1
[18:24] <dipankar> dfarning, done
[18:24]  * dipankar is closing the 'No gsm connection was set in Gconf' bug
[18:25] <dipankar> dfarning, for making patch I should be targeting this package : python-jarabe-0.88?
[18:25] <dipankar> because the file, network.py falls under this package.
[18:25] <dfarning> dipankar, this should be turned into a patch and submitted to SL and accepted before closing
[18:26] <dfarning> dipankar,  is -jarabe- the source package in debian that contains the file?
[18:28] <dipankar> dfarning, this is as close as I could get: https://launchpad.net/ubuntu/maverick/+package/python-jarabe-0.88
[18:29] <dipankar> for debian : http://packages.debian.org/testing/python/python-jarabe-0.88
[18:30] <dfarning> dipankar, i think sugar-0.88 is the source package you want.
[18:31] <dipankar> dfarning, ok. right on
[18:33] <dipankar> dfarning, I have sugar-0.88 package. But I am unable to find the network.py file
[18:36] <alsroot> ankur: hi
[18:36] <alsroot> kandarpk: pong
[18:36] <dfarning> dipankar, sugar-0.88.1/src/jarabe/model/ in debian
[18:36] <dipankar> dfarning, just found it :)
[18:36] <kandarpk> alsroot: what other modules provide GUI tools like widgets does ?
[18:37] <alsroot> kandarpk: in fact, sugar-toolkit's directories: src/sugar/graphics src/sugar/activity
[18:38] <kandarpk> alsroot: Ok.
[18:39] <dipankar> dfarning, unfortunately thats not the file :(
[18:43] <dipankar> dfarning, I think I have the old package :(
[18:43] <dipankar> dfarning, how can I get the latest package? debcheckout?
[18:44] <dfarning> dipankar, yes the file in http://pastebin.com/8tfj202m it looks right to me
[18:44] <kandarpk> dfarning, alsroot: please see http://picturepush.com/host.php?image=4015695
[18:45] <dipankar> dfarning, yeah. I have the old files :(
[18:45] <kandarpk> dfarning, alsroot, manusheel sir: In the activity various modules along with the GUI provided can be described
[18:45] <dfarning> kandarpk, cool
[18:47] <ankur> hi alsroot , :)
[18:49] <ankur> i was working on to change the text in title bar of xephyr wondow if possible..... i was not able to process in that direction.Will need your help
[18:52] <dipankar> alsroot, hi. is it ok to continue with the fullscreen bug?
[18:53] <dipankar> dfarning, it will take sometime to download the package. slow speed :(
[18:55] <alsroot> ankur: dunno how it is important, I mean, sugar-emulator is just sugar emulator, you need to look to Xephyr documentation, sorry can't help here
[18:56] <alsroot> dipankar: what is the number of bug you created?
[18:56] <dipankar> alsroot, it has gone for moderation testing, I think no bug number has been assigned yet
[18:57] <ankur> right , i will try once again , i tried before but i was not able to see any break through
[18:58] <dipankar> dfarning, created my gsm.patch
[18:58] <ankur> also i wanted to work on the part that every little change in control panel should not require restart. so , i have zeroed on code segment which should be changes but i wa not able to figure out in which changes i should make the change
[18:59] <ankur> or more importantly , can i change the functionality of control panel so that it never requires restart where ever possible
[18:59] <ankur> ?
[19:01] <dfarning> dipankar, I have not heard of moderation for the bug tracker..... are you signed in?
[19:02] <dipankar> dfarning, I filed a bug ticket at bugs.sugarlabs.org as instructed by alsroot
[19:02] <alsroot> ankur: I guess nope, keeping control panel widgets all time in memory could be overkill
[19:03] <dfarning> hmmm maybe there is a spam filter inplace.
[19:04] <manusheel> dipankar: What is your username?
[19:04] <manusheel> at bugs.sl.org
[19:04] <dipankar> manusheel, dipankar
[19:05] <alsroot> dipankar: yup, looks like it is spam filter, it sansboxing every new submitter (afaik, but better to ask silbe)
[19:05]  * alsroot accepted it
[19:06] <alsroot> dipankar: you can upload your patch to http://bugs.sugarlabs.org/ticket/2180
[19:07] <dfarning> alsroot, are you an admin on trac?
[19:07] <dipankar> alsroot, ok. I found that silbe is the one who actually wrote the code for fullscreen emulator :)
[19:07] <dipankar> manusheel, dfarning, I have uploaded patch for gsm connection: https://bugs.launchpad.net/ubuntu/+source/sugar-0.88/+bug/614394 please check it
[19:10] <dfarning> dipankar, good.  Can you now open a bug in the debian bug tracker and attach you patch?
[19:10] <dipankar> dfarning, ohk
[19:10] <manusheel> dipankar: Yes, Dipankar. Please do that.
[19:16] <dfarning> dipankar, then test the patch against the debian package buy building it and then pinging the olpc-debian list for jonas or luke to commit it.
[19:16] <dipankar> dfarning, ohk
[19:24] <dipankar> manusheel, dfarning , I have sent the patch to DBTS
[19:25] <dfarning> dipankar, +1 what is the debian bug number
[19:25] <manusheel> dipankar: great
[19:25] <dipankar> dfarning, Bug#593380
[19:26] <dipankar> manusheel, dfarning : alsroot told me to upload a pacth for this too. I wanted to upload it before sleeping.
[19:26] <dipankar> how to do it
[19:26] <dipankar> ?
[19:27] <dfarning> dipankar, to where did alsroot suggest that you upload the patch
[19:28] <dipankar> dfarning,oops sorry. here: http://bugs.sugarlabs.org/ticket/2180
[19:31] <dfarning> dipankar, which issue are you fixing, the gsm logging error or the calculating the screen resolution in the CP?
[19:31] <dipankar> dfarning, the fullscreen issue. I have a patch ready for it.
[19:32] <alsroot> dipankar: there is "Attach file" button on http://bugs.sugarlabs.org/ticket/2180 page
[19:34] <dipankar> alsroot, I am not getting that option anywhere :(.
[19:34] <dipankar> is there something i am missing out
[19:34] <alsroot> dipankar: are you logged in?
[19:34] <dipankar> alsroot, yeah
[19:36] <dipankar> alsroot, I think it is owned by tomeu, thats why I can't upload anything i guess
[19:36] <dipankar> alsroot, how about I e-mail it to you?
[19:37] <alsroot> dipankar: ok, but it is something wrong w/ bugs.sl.o then, any logged on user can upload a patch
[19:37] <dipankar> alsroot, ohk :(
[19:40] <dipankar> alsroot, sent it to you
[19:41] <dipankar> alsroot, manusheel, dfarning, i would like to head to bed now. I will build the packages and test them on my system tomorrow
[19:41]  * dipankar says goodnight and great day!
[19:41] <dfarning> dipankar, sounds good see you tomorrow
[19:49] <kandarpk> alsroot: around ?
[19:49] <alsroot> kandarpk: yup
[19:50] <kandarpk> alsroot: how can I increase the font size of a gtk.Button ?
[19:53] <alsroot> kandarpk: there is modify_font() in gtk.Widget class
[19:53] <kandarpk> alsroot: Ok.
[19:53] <alsroot> i.e. button.modify_font(pango.FontDescription("Sans 10"))
[19:54] <alsroot> kandarpk: but in general, it is not good idea to change font size for regular widgets like buttons
[19:54] <kandarpk> alsroot: thanks a lot.
[19:55] <kandarpk> alsroot: why shouldn't they be changed ?
[19:57] <alsroot> kandarpk: it is common practice(and imho, good idea) to have all widgets of the same font, of course except special cases like games
[19:58] <kandarpk> alsroot: Ok. got it.
[20:02] <kandarpk> alsroot: it says global name 'pango' is not defined
[20:03] <alsroot> kandarpk: yup, you need to "import" pango module
[20:03] <kandarpk> alsroot: yeah, but the font size isn't changing
[20:06] <alsroot> kandarpk: not all for all properties like font, setting value can affect what you need (it is this particluar widget impl. details)
[20:07] <alsroot> kandarpk: looks like for buttons, font can be changed only on style level
[20:07] <kandarpk> alsroot: ok.
[20:10] <alsroot> kandarpk: e,g, you need to cnahge font not for button itself but for button.get_child() widget (which is standard gtk.Label)
[20:11] <kandarpk> alsroot: how can I do that ?
[20:12] <alsroot> kandarpk: just button.get_child().modify_font(...)
[20:13] <kandarpk> alsroot: wow, that worked.
[20:13] <kandarpk> alsroot: thanks.
[20:14] <alsroot> yw
[20:18] <kandarpk> alsroot, dfarning, manusheel sir: http://www.mediafire.com/imageview.php?quickkey=2mbavapx11vh92q&thumb=5
[20:18] <kandarpk> uploaded some screenshots
[20:19] <kandarpk> gn.
[20:20] <manusheel> kandarpk: Sure, Kandarp.
[20:20] <manusheel> We'll have a look.