=== bernie_afk is now known as bernie === bernie is now known as bernie_afk === bernie_afk is now known as bernie [15:13] morning! [16:25] alsroot, hello. good morning [16:25] dipankar: hi [16:25] dfarning, hello, good morning :) [16:27] alsroot, I didn't receive any mail from sugarlabs. Is it usual? [16:28] dipankar: [16:28] YOur subscription to sugar-devel was rejected. [16:28] manusheel, oh. [16:28] dipankar: You used dipankar@seeta.in as your username. [16:28] manusheel, ohk sir [16:30] dipankar: to speed up process, you can discuss your patch with module maintainer (http://wiki.sugarlabs.org/go/Development_Team/Release/Modules) on #sugar [16:31] manusheel, sir, now its accepted my request [16:36] alsroot, there it is mentioned that you are a maintainer of 'sugar' (journal) :P. I guess I should contact tomeu to review my package? [16:36] dipankar: you can ping Co-maintainers as well [16:37] alsroot, sure [16:37] alsroot, is there anyway (except pastebin) where I can refer others to my patch? [16:38] on #sugar [16:39] dipankar: better to follow http://wiki.sugarlabs.org/go/Development_Team/Code_Review, did you get approve from silbe? [16:39] dipankar: Let me make your FTp account. [16:39] ..on bugs.sl.o [16:41] alsroot, no :( [16:42] dipankar: well, use pastebin for a while [17:01] alsroot, I am not able to start different module of some activity using the same activity bundle_id [17:02] alsroot: what I am trying to d is to have different buttons, and clicking on the buttons should launch the same activity but some different module [17:03] * dipankar is away: Be Right Back [17:03] * dipankar is off for dinenr [17:07] kandarpk: I think you have to follow complicated way, the thing is that sugar-launch uses sugar db of installed activities, thus when you calling it with the same bundle_id, the code will be invoked -- try to pass additoinal info(e.g. module to start) via envars (unfortunately sugar-launch doesn't support custom args) [17:07] s/the code will be invoked/the same code will be invoked/ [17:08] alsroot, will os.system('export option=1') [17:08] os.system('sugar-launch org.laptop.HelloWorld') [17:08] work ?? [17:10] kandarpk: use suprocess module instead http://docs.python.org/library/subprocess.html#convenience-functions, e.g. call() method has env argument http://docs.python.org/library/subprocess.html#using-the-subprocess-module [17:10] alsroot: I dont have much knowledge on how to check the envar in python [17:10] alsroot: ok. [17:18] * dipankar is back (gone 00:15:51) [17:18] * dipankar is away: Be Right Back [17:19] * dipankar is back (gone 00:00:02) [18:07] alsroot, what will happen if I launch the running activity itself using sugar-launch ? [18:08] kandarpk: it will launch new activity instance [18:09] sugar-launch does it in any case [18:13] alsroot: ok, thanks. [18:14] alsroot, tomeu assigned me some work. [18:15] alsroot, can you help me a bit in understanding the code? [18:15] dipankar: yup [18:15] alsroot, I am to understand the scaling and gtkrc.em [18:18] alsroot, how I find a file whose partial content I know using grep [18:18] ? [18:18] dipankar: the thing is simple, there are two gtk.rc files /usr/share/themes/sugar-72 and -100, the only difference is that them have different scale, one for huge dpi(200 on XO) and one for more regular desktops w.g. 1024.768 [18:18] I tried searching a lot [18:18] dipankar: see artwork project [18:23] alsroot, artwork project == http://www.google.com/search?hl=en&q=artwork+project&aq=f&aqi=g2&aql=&oq=&gs_rfai= [18:23] ? [18:24] dipankar: just search on git.sl.o, http://git.sugarlabs.org/projects/sugar-artwork [18:25] alsroot, ohk! I already have that with me [18:26] alsroot, tomeu referred to a file : gtkrc.em [18:26] I found that in data/ in sugar-toolkit [18:27] dipankar: hmm, it should be in artwork/gtk/theme/ [18:29] ..in artwork git repo I mean [18:36] alsroot, ohk, that git repo is somewhat different from ubuntu package [18:39] alsroot, so in which file shall I target for patch [18:39] ? [18:40] dipankar: what your idea is [18:40] s/idea/plan/ [18:41] alsroot, my plan is to increase the scaling a bit so that cropping in nullified [18:42] alsroot, this is what tomeu said: yeah, we want less pixels per cell [18:42] dipankar: are your planing to compose several gtk.rc files for different resulutions/dpi? [18:43] alsroot, I have no idea about gtkrc at all. :( [18:43] alsroot, I need sometime to understand the code [18:44] dipankar: I mean if you decrease/increase scaling you just will target it from one resolution/dpi to other nothing more (i.e. you solve probelem in one case but create new one) [18:45] alsroot, ohk. that I didn't think of [18:46] dipankar: there was idea to create several gtk.rc files fot different resolutins/dpi, but in my mind it sounds pretty undoable for distros like ubuntu (but ok for derivates like XOOS) [18:47] alsroot, then its a bit risky to try them [18:47] alsroot, I mean there is a chance that it might affect other resolution [18:47] dipankar: yeah, that's the core issue of this problem :) [18:47] alsroot, why do you think tomeu rejected my patch? [18:48] tomeu told about 'what user want' [18:48] alsroot: what should I do to set text wrapping in HBox ? [18:49] alsroot: its text goes under the button if too long instead of splitting to two lines [18:49] I mean the text of the label I added to HBox [18:50] dipankar: dunno, at then end, there are different usecases, and there is no need in having some of presets in code code -- e.g. in jhconvert ditros I use this patch http://bugs.sugarlabs.org/ticket/1747 [18:51] kandarpk: you need to wrap text on label widget not on HBox, http://library.gnome.org/devel/gtk/stable/GtkLabel.html#GtkLabel--wrap [18:53] alsroot: Ok. [18:57] alsroot, looks like Its not the first time with me :). [18:58] dipankar: well, there 11 months old ticket http://bugs.sugarlabs.org/ticket/1396 :) [18:58] *there is [19:00] alsroot, I have seen that a lot of times [19:01] :) [19:01] *while searching [19:01] alsroot, I hate to say this, but I think I should catch some sleep now [19:01] :( [19:01] alsroot, see you again tomorrow [19:01] dipankar: see you [19:02] * I will try my best to understand some part of code [19:02] alsroot, bye [19:02] * dipankar is off for the night [19:10] kandarpk: Hi Kandarp. [19:10] Around? [19:11] manusheel sir: yes sir. [19:15] kandarpk: How is the development of the activity coming along? [19:16] manusheel sir: the basic framework is ready [19:16] manusheel sir: let me upload some screenshots [19:16] kandarpk: Neat. [19:16] kandarpk: Do you have an FTP account? [19:16] That is, SEETA FTP account. [19:17] Let me know. I'll get it created it right away. [19:17] You should get your screenshots uploaded over there. [19:17] manusheel sir: you sent me the details of the account of vijaykansal [19:18] Ok, you can use that FTP account. [19:18] Great. [19:19] lfaraone, hi [19:21] kandarpk: Please upload screenshots where we used to upload files. You can create a new activity folder too. [19:21] manusheel sir: sure sir. [19:24] kandarpk: Great. [19:24] kandarpk: Also, please do let me know the results of the browse activity too. [19:25] manusheel sir: that needs to be tested on debian ? [19:39] manusheel sir: screenshots uploaded at http://seeta.in/sugar/api/documentation/activity/ [19:40] I'll try browse on debian now. [19:45] kandarpk: Neat. [19:46] kandarpk: Reviewing it. [19:48] manusheel sir: We can pick the code of various activities, split that into basic parts and add to the activity to provide the steps involved. [19:51] kandarpk; Interesting. [19:53] manusheel sir: this way users/developers can see the modules used and the reason for their use too becomes clear [19:53] alsroot, hi [19:54] manusheel sir: as now we can run the activity by adding the modules step by step to it. [19:54] ishan: hi [19:55] alsroot, i am having problem with starting browse activity on sugar [19:55] it is related to hulahop package [19:55] ishan: what does it log? [19:56] kandarpk:Great. [19:56] That is neat. [19:56] alsroot, http://pastebin.com/jgrDjauF [19:56] here is my log file [19:57] ishan: what distro are you using? [19:57] manusheel sir: browse needs to be tested on debian ? [19:57] ishan: anyway, do you have hulahop package? [19:58] alsroot, i am facing problems in installing hulahop package [19:58] i tried sudo apt-get install python-hulahop but it failed [19:59] ishan: w/ what error [20:00] alsroot, http://pastebin.com/ZYUDcJFY [20:00] it shows broken package [20:01] ishan: you are on karmic? [20:01] alsroot, i am presently on lucid [20:02] ishan: just ping python-xpcom maintainer, I guess it should be just rebuilt [20:02] alsroot, okay [20:48] hi ishan [20:49] lfaraone, hi === bernie is now known as bernie_afk [22:08] alsroot: Hi Aleksey. Around? [22:27] manusheel: yup [22:38] alsroot: Thanks for the pointers on the entry point for a.s.l.o project. Very helpful. [22:40] manusheel: hope, it will be helpful to create django based one [22:42] *I hope [22:47] alsroot: Sure, absolutely. [22:51] manusheel: btw, in sugar, we need a portal to share sugar objects (i.e. journal objects) as well, something like http://scratch.mit.edu/ i.e. gallery of user objects, if you think if AMO could be useful for that (it supports not only addons but also themes), would great to start thinking about it [23:00] alsroot: Sure, alsroot. This is something that I wanted to discuss. Yes, this is a very important use-case. [23:01] alsroot: Do we have a strategy in place to create a framework for uploading user objects, and then develop a Web 2.0 wrapper around it. [23:02] alsroot: Can you point me to some examples that could help us define an architecture for the same? [23:02] manusheel: heh, in that case I'm really wrong man to ask :) [23:03] manusheel: but afaik we don't have such strategy at all :/ [23:03] manusheel: would be really great if someone take it into their hands [23:04] *his [23:04] ..but better is more useful :) [23:04] *better "their" [23:05] alsroot: Ok. Thank you for bringing this idea on the table. Indeed a very important idea. [23:06] well, it is new idea.. [23:06] *is not [23:07] * alsroot need to take a rest at the end :) [23:07] alsroot: Yes, indeed. And, I am not sure whether we have open source CMS to implement such a portal. We'll have to start from scratch. [23:07] alsroot: Sure. [23:07] alsroot: We'll talk tomorrow. [23:07] manusheel: see you [23:08] alsroot: Talk to you soon. Take care. [23:08] alsroot, how are thing going?