[15:20] <dfarning> good morning kandarp and ishan.
[15:20] <kandarp> dfarning: good morning
[15:20] <ishan> dfarning, good morning
[15:20] <kandarp> dfarning: how are you doing ?
[15:20] <dfarning> how are you guys doing?
[15:22] <dfarning> kandarp, your activity looks good:) and ishan, I am impressed how fast your getting up to speed:)
[15:22] <kandarp> dfarning: I am doing good.
[15:22] <ishan> dfarning, i am doing good
[15:22] <ishan> thank you
[15:23] <kandarp> dfarning: and thanks.
[15:23] <dfarning> +1
[15:23] <kandarp> dfarning: I wish I could make it a bit dynamic.
[15:24] <kandarp> dfarning: i.e., it will be great if it could automatically break an activity into different parts and then generate the output
[15:24] <dfarning> ishan, do you know who was working on the mouse bug stops after running sugar bug?  We need to get that pushed into Debian as soon as possiable.
[15:24] <kandarp> so that the gradually improved activity could be studied
[15:25] <ishan> dfarning, no
[15:25] <kandarp> s/ gradually improved/ gradually improving/
[15:25] <ishan> dfarning, let me check
[15:25] <dfarning> ishan, thanks
[15:26] <kandarp> dfarning: that was due to gdm not being upto date, IIRC.
[15:26] <kandarp> dfarning: the mouse bug.
[15:26] <dfarning> kandarp, hhhm is gdm upto date in the latest maverick?
[15:27] <kandarp> dfarning: I think so.
[15:27] <kandarp> dfarning: but, I'll confirm when I log into maverick.
[15:28] <dfarning> kandarp, I apt-get updated yesterday and still had the problem.  We can't release for wider testing until that bug is fixed.
[15:29] <ishan> dfarning, neeraj is working on the mouse bug
[15:29] <dfarning> kandarp, users get upset (and lose faith) when one of our programs makes their computer unusable until they reset something in setting:(
[15:29] <kandarp> dfarning: OK. That means gdm isn't the only reason.
[15:30] <kandarp> dfarning: +1.
[15:30] <dfarning> neeraj, good morning.
[15:30] <neeraj> dfarning: good morning :)
[15:31] <dfarning> kandarp, about you activity.... that is the great thing about open source.  Put you source on git.sl.o and upload your activity to aslo and if other find it useful they will improve it.
[15:31] <dfarning> neeraj, how are you?
[15:32] <neeraj> dfarning: I am good. Thanks for asking.
[15:32] <kandarp> dfarning: +1.
[15:32] <neeraj> dfarning: how about u?
[15:33] <dfarning> neeraj, I was just asking ishan about the status of the mouse bug no working ofter running sugar.  how is that coming?
[15:34] <dfarning> neeraj, great! I am flying home this afternoon. So two day from now I will be in my own home again:)  Traveling is nice, But I like being at home too.
[15:34] <neeraj> dfarning: :)
[15:35] <neeraj> dfarning:  about the mouse bug, I know the solution, its just that we need to attach patch using quilt on LP.
[15:36] <neeraj> dfarning: I was waiting for my control panel icon cut off patch to get accepted so that I can update the revision number of mouse bug patch acco. otherwise version numbers of these two patches will conflict. As we are change sugar-0.88 package in both bugs
[15:37] <neeraj> also lately I was little busy with some personal work. So couldn't come much on irc. Till then was helping ishan and mukul with some issues :)
[15:38] <dfarning> neeraj, I think you just incrementally number the patches.  In most cases it should not matter in which order the patches are applied.
[15:39] <dfarning> neeraj, as we get moving it will be common to have ten if not hundreds of patches in the pipe waiting to be review and applied.
[15:39] <neeraj> dfarning: Ok. Actually previously while creating patches, I used to submit debdiff file and update the changelog file also.
[15:40] <neeraj> Changelog, to give information about the changes made and closing of bug.
[15:41] <dfarning> neeraj, Use what ever lfaraone suggests.  He understands the processes for ubuntu and debian.
[15:42] <dipankar> dfarning, hello
[15:42] <neeraj> dfarning: Ok.
[15:43] <dipankar> neeraj, ishan, kandarp  : hi guys
[15:43] <neeraj> dipankar: hi
[15:43] <kandarp> dipankar: Hi.
[15:43] <dfarning> neeraj, please don't take this as a critisim.... The "problem" is the Sugar on Ubuntu is getting good enough that I would like to do an Alpha release next week for testers:)
[15:43] <dfarning> dipankar, hello how are you?
[15:45] <neeraj> dfarning: sure. Will ask lfaraone correct way. Though he had send us a mail on debian-olpc, i still have some confusion.
[15:45] <neeraj> dipankar: what method are u now using for patches?
[15:46] <dipankar> dfarning, I am doing great. Got an email from Sascha Silbe
[15:46] <dfarning> dipankar, +1
[15:47] <dipankar> dfarning, Sascha liked my idea for the fullscreen bug. But also mentioned that Tomeu should give me a r+ for the patch to be added
[15:47] <dipankar> neeraj, I have currently used git format-patch HEAD^ command to make patch
[15:47] <dipankar> neeraj, it is for sugarlabs though
[15:48] <ishan> dipankar, hi
[15:48] <dfarning> dipankar, nice.
[15:48] <dipankar> neeraj, I still haven't found something to make a patch for Ubuntu. Sorry :(
[15:49] <dfarning> dipankar, isn't it kind of cool to upstream an patch..... knowing that a few months from now millions of kids will be using your code
[15:49] <dipankar> dfarning, and Tomeu has already indicated that the patch I referred to isn't the one to be added in the upstream. He wants me to test with gtkrc :(
[15:49] <neeraj> dipankar: I assume that now we have submitting the patches on sugarlabs directly which will be directly applied in debian and ubuntu and other distro when ever they will update their packages :)
[15:50] <dipankar> dfarning, yeah It will be awesome and a great achievement for me
[15:50] <neeraj> of course all patch will not be send to sugarlabs directly :)
[15:51] <ishan> dipankar, neeraj:i went through the documents on xephyr but could not find anything that could help me in debugging the bug
[15:51] <dipankar> neeraj, yeah, if the sugarlabs directly use our patches, that will reflect in both Debian and Ubuntu! A great thing for us
[15:51] <dipankar> ishan, you still working on the name bug?
[15:53] <dfarning> dipankar, neeraj yes, but.... if the bug is significant.  We will want to temporarily fix it in debain -> ubuntu.  Any modifications made to upstream sugar now will not flow downstream to ubuntu until version 11.04
[15:55] <neeraj> dfarning: yeah. Thats why at present I was using this method. But I was following this method-> Attach the debdiff for ubuntu
[15:55] <dfarning> neeraj, +1
[15:55] <dipankar> dfarning, thats in april next year!
[15:55] <neeraj> and add the patch in debian/patches folder so that it can be later applied in debian
[15:56] <neeraj> By using quilt, we can keep track of the patches applied and send patch to sugarlabs later as needed.
[15:57] <ishan> dipankar, yes
[15:58] <dfarning> lfaraone, can you look at https://bugs.edge.launchpad.net/ubuntu/+source/sugar-chat-activity-0.86/+bug/565770
[15:58] <ubot2> Launchpad bug 565770 in sugar-chat-activity-0.86 (Ubuntu) "[removal request] sugar-chat-activity-0.86 (affects: 1) (heat: 35)" [Undecided,Incomplete]
[15:58] <dipankar> ishan, use synaptic to track down a file
[15:59] <dfarning> lfaraone, it ^^ seems to have been superceeded by the neeraj's recent sync request.
[15:59] <dipankar> search the package and see properties->installed files
[15:59] <ishan> dipankar, okay
[16:01] <ishan> dipankar, dipankar i have tracked down all files related to xephyr
[16:02] <dipankar> ishan, great.now if you see, you will find /usr/bin/Xephyr
[16:03] <dipankar> ishan, I think you should edit this file to bring in the required changes. ask alsroot in detail.
[16:05] <dfarning> ishan, were you working on packaging turtle art?
[16:05] <ishan> dfarning, mukul was working on turtle art
[16:05] <dfarning> ishan, thanks
[16:13] <ishan> dipankar, sir how to open xephyr file
[16:13] <ishan> it shows blank file with gedit
[16:13] <dipankar> let me check
[16:14] <dipankar> ishan, I check the case "Xephyr"
[16:15] <dipankar> I am unable to open the file myself, its a binary file
[16:16] <dipankar> ishan, I think you should refer to ankur or someone senior
[16:17] <ishan> dipankar, okay
[16:18] <dipankar> dfarning, I think I have followed the process of reviewing properly: http://bugs.sugarlabs.org/ticket/2180
[16:18] <ishan> dipankar, ankur sir is not online
[16:19] <dipankar> ishan, ask alsroot then :P
[16:19] <ishan> alsroot, hi
[16:19] <alsroot> ishan: hi
[16:20] <alsroot> ishan: what you are planing to do w/ /usr/bin/Xephyr?
[16:20] <dfarning> dipankar, +1 if you don't get a review in a few days please ask for a review on the sugar-devel mailing list.  Sometimes things get stuck in launchpad.
[16:21] <ishan> alsroot, i am thinking of making some changes which could change the displayed text
[16:21] <dipankar> dfarning, ohk sure :)
[16:21] <alsroot> ishan: but you need to start from its sources, not from /usr/bin/Xephyr (which is binary)
[16:21] <dipankar> dfarning, do you mean sugarlabs? (you mentioned launchpad)
[16:21] <alsroot> ishan: just got to its home page and found how to download sources
[16:22] <ishan> alsroot, okay
[16:22] <alsroot> *find
[16:22] <alsroot> ishan: it should be something low level X11 coding, sorry didn't do such things by myself and can't help here
[16:23] <dfarning> dipankar, yep too many bugtrackers for me to keep track of them all:(
[16:24] <ishan> alsroot, no problem
[16:24] <dipankar> dfarning, :). Btw, copying is not working on my system (Sugar Emulator). Can you please confirm whether you can copy a small file from a pend drive to your journal?
[16:25] <dipankar> alsroot, hi, could you please do the above ^^ and confirm if copy is working?
[16:25] <dfarning> ishan, I would recommend moving on to another bug.  That one looks ugly,  but it really does not reduce usability.  You can come back to it in a couple of weeks with freash eyes.
[16:25] <dfarning> dipankar, i am testing it
[16:25] <dipankar> thanks
[16:26] <ishan> dfarning, okay. let me ask manusheel sir
[16:27] <alsroot> dipankar: works fine in my case (git sugar), if it fails in your case, it should log something
[16:31] <dfarning> dipankar, hmmm I have manage to crash sugar by switching between the journal and usb:(
[16:31] <dipankar> dfarning, don't use a big pen drive, mine also gets stuck with a big one
[16:32] <dipankar> *s/big one -> in which no. of folders is large
[16:32] <dfarning> dipankar, 8 gig is all I have with me:(
[16:32] <dipankar> alsroot, ohk, what file did you copy? I am trying to copy a small pdf
[16:32] <dipankar> dfarning, that should crash
[16:32] <dfarning> dipankar, can you file a bug on this in LP?
[16:32] <dipankar> *s/shouldn't
[16:33] <alsroot> dipankar: me too
[16:33] <dipankar> dfarning, just a minute. I need to confirm whether I am doing it properly :P
[16:35]  * lfaraone waves.
[16:36] <dipankar> lfaraone, hey, how are you?
[16:36] <lfaraone> kandarpk, dfarning: GDM never had any effect on the metacity mouse bug.
[16:37] <dfarning> dipankar, with regard to your question about copying to usb.... the last message in my log is at http://pastebin.com/aBELZYsV
[16:37] <dipankar> alsroot, which log should I refer to for copying? shell.log?
[16:37] <dfarning> just before the crash
[16:37] <alsroot> dipankar: yup
[16:37] <dfarning> lfaraone, thanks
[16:38] <lfaraone> dfarning: by the way, we should tell mukul et al that they don't need to be spending time on turtleart.
[16:38] <dfarning> lfaraone, how is the package queue coming
[16:39] <dipankar> alsroot, I am not getting any error in shell.log
[16:39] <dipankar> :(
[16:39] <dipankar> dfarning, I am not getting any error in shell.log
[16:39] <lfaraone> dfarning: since `turtleart` is already packaged standalone and I recently created a "sugar-turtleart-activity" package which linked the right files for TA Standalone to work in Sugar.
[16:39] <lfaraone> dfarning: it'll get reuploaded to NEW as soon as walter releases.
[16:39] <alsroot> dipankar: how does it fail, no copy?
[16:40] <dfarning> lfaraone, +1
[16:40] <dipankar> alsroot, here is what is happening:
[16:40] <dipankar> 1
[16:41] <satellit_> dfarning: are you using drag-drop for transfer to USB? link of how I do it http://wiki.sugarlabs.org/go/Features/Soas_V4/ASLOxo_Activity_Test_Table#How_To_Test
[16:41] <alsroot> dipankar: ^
[16:42] <dfarning> satellit_, +1 I dragged an icon from the journal on the usb icon.
[16:43] <satellit_> : )
[16:44] <dipankar> dfarning, satellit_, alsroot, I copy using right clicking on the pdf in usb drive. There is some flashing on the journal and after sometime its stops
[16:44] <satellit_> on the bottom left under frame or the right display....have to click on journal on top of frame  then let frame retract then 2 icons on left bottom are the ones to use
[16:44] <lfaraone> dipankar: please let the other people at SEETA know that the upstream author is *not* "Jonas Smedegaard"... they're misfiling the ITPs with the wrong name.
[16:45] <dipankar> lfaraone, ohk, I will tell them for sure
[16:45] <satellit_> dipankar this also works to install .xo packages
[16:47] <dfarning> satellit_, that sounds like a usability bug.  Can you file a bug in the sugar labs bug tracker please?
[16:47] <satellit_> bug? it works ?
[16:47] <lfaraone> dfarning: so Mukul packaged sugar-turtleart-activity and sugar-turtleblocks-activity :(
[16:48]  * ishan is going to dinner
[16:48] <lfaraone> (I had been working with Walter on that, and both of those packagings are wasted time)
[16:48]  * ishan to/for
[16:49] <dfarning> lfaraone, Mukul is listed as the packager on http://wiki.debian.org/Sugar/tasks
[16:51]  * satellit_ new feature? wish we had drop down box when clicked item  in journal "copy to 2nd USB"(when one was present ) or visa versa
[16:51] <dipankar> satellit_, alsroot, dfarning ,: The drag and drop from journal to usb is working, and vice-versa is also work :)
[16:51] <dipankar> *s/work/working
[16:52] <satellit_> yes I use it all the time
[16:53] <lfaraone> dfarning: that's right. I didn't list s-ta-a because Matthew, Walter and I were thinking about how to proceed.
[16:53] <lfaraone> dfarning: Matt had already packaged "turtleart", standalone, and I had uploaded that to Debian about a week ago.
[16:54]  * dipankar is off to dinner
[16:56] <lfaraone> dfarning: It was listed as being packaged by "Matthew Gallagher" on the tasks page last I looked.
[16:57] <dfarning> lfaraone, these things happen... As a team learning coordination is as important as learning the technical skills.
[16:58] <lfaraone> dfarning: yeah. one thing that would have been useful is if when the ITPs for those other packages were filed they CC'd the debian-olpc-devel mailing list.
[16:58]  * lfaraone could have been better about documenting his progress.
[16:59] <dfarning> lfaraone, I assume that because matt was not working it, manu assigned it.
[17:00]  * lfaraone will be off and on for the next few hours, going on a drive.
[17:00] <lfaraone> (college visits, actually)
[17:00] <dfarning> lfaraone,  yes, as far as I am concern this is no worse then a r- on a review.  We fix the problem, if necessary fix the documentation, and move on:)
[17:00] <dfarning> lfaraone, enjoy.
[17:01] <lfaraone> college visits,a ctually <_<;
[17:04] <dfarning> kandarpk, can you take a look at https://bugs.edge.launchpad.net/ubuntu/+source/sugar-jigsawpuzzle-activity/+bug/284968
[17:04] <ubot2> Launchpad bug 284968 in sugar-jigsawpuzzle-activity (Ubuntu) "Jigsaw fails to launch (dups: 1) (heat: 18)" [Medium,In progress]
[17:04] <dfarning> it is related to the jigsaw activity you packaged.
[17:05] <dfarning> kandarpk, can you assign it to yourself unless it has already been fixed
[17:06] <kandarpk> dfarning: OK.
[17:06] <dfarning> kandarpk, thanks.
[17:11] <dfarning> kandarpk, do you know who packaged etoys? http://packages.qa.debian.org/e/etoys.html still list jose.
[17:11] <alsroot> ishan: btw, Xephyr has -title argument, you can just pass arbitrary title (from emulator.py)
[17:12] <kandarpk> dfarning: Ankur packaged etoys-activity.
[17:14] <dfarning> kandarpk, thanks
[17:14] <kandarpk> dfarning: np.
[17:18] <kandarpk> alsroot: can you help me out with the activity I am working on ?
[17:18] <alsroot> kandarpk: sure
[17:19] <kandarpk> alsroot: I've added the second activity in another file.
[17:19] <kandarpk> alsroot: the main file is: http://paste.ubuntu.com/481497/
[17:19] <kandarpk> alsroot: and the second activity is in http://paste.ubuntu.com/481498/
[17:22] <alsroot> kandarpk: you need to call activity.Activity.__init__ from from __init__ method
[17:22] <kandarpk> alsroot: OK.
[17:24] <kandarpk> alsroot: changed to http://paste.ubuntu.com/481503/
[17:25] <kandarpk> alsroot: getting error http://paste.ubuntu.com/481504/
[17:25] <alsroot> kandarpk: you need to call activity.Activity.__init__ in any case otherwise class will be not fully initiated
[17:26] <alsroot> kandarpk: well the error is obvious "global name 'handle' is not defined
[17:26] <alsroot> you dont have 'handle'
[17:26] <kandarpk> alsroot: how do I correct it ?
[17:26] <alsroot> kandarpk: it is passed to your Activity class by sugar, see 1st activity
[17:28] <alsroot> kandarpk: "def __init__(self, handle):" from 1st activiy
[17:28] <kandarpk> alsroot: OK. I thought it is a variable inherited from Activity class.
[17:34] <kandarpk> alsroot: how do I display the second instance of the activity ?
[17:35] <alsroot> kandarpk: what do you mean by display? after invoking sugar-launch command, second activity will be launched as regular activity i.e. will be added to launched activgity list
[17:35] <kandarpk> alsroot: GtkWarning: gtk_widget_show: assertion `GTK_IS_WIDGET (widget)' failed
[17:35] <kandarpk>   activity.show()
[17:36] <kandarpk> alsroot: clicking on the button hangs sugar.
[17:36] <alsroot> kandarpk: what the backtrace for this error is?
[17:37] <kandarpk> alsroot: http://paste.ubuntu.com/481509/
[17:43] <kandarpk> alsroot: It got resolved.
[17:44] <kandarpk> alsroot: as you told the activity had to be initialised anyway, I moved activity.__init__ out of if-else.
[17:55] <kandarpk> alsroot: is there a way by which the previous method could work ?
[17:56] <kandarpk> alsroot: I wanted to replace SubActivity by activities of sugar, they will have their own init calls.
[17:58] <alsroot> kandarpk: not sure if I got your idea, you mean launching regular sugar activities from main one ?
[17:58] <kandarpk> alsroot: yes
[17:59] <alsroot> kandarpk: you just need to pass particular bundle_id to sugar-launch command in os.system()
[18:00] <kandarpk> alsroot: I would include files from other activities as submodules.
[18:00] <kandarpk> alsroot: that wont require bundle_id I think.
[18:01] <kandarpk> alsroot: wont it be the same as launching SubActivity ?
[18:03] <alsroot> kandarpk: the option could be, passing class name that should be launched in the next launching iteration via envar, so you need to tweak "exec" option in acitivty.info file that will get class to start from this envar
[18:04] <alsroot> i.e. w/o any special coding in activity class (classes are different)
[18:06] <kandarpk> alsroot: hmmm, getting the idea.
[18:08] <kandarpk> alsroot: that means we'll need to grep for the activity name and then launch that activity using bundle_id ?
[18:09] <kandarpk> alsroot: or include the other activity as submodule and use its class name to execute it ?
[18:10] <alsroot> kandarpk: nope, I meant: there is only one activity all time(one bundle_id), it has several modules(with Activity classes) including main one, by default (if envar wasn't passed), main will be launched, main actiivty will start itself by passing envar (thus tother activity modules will be launched)
[18:11] <kandarpk> alsroot: got it.
[18:16] <kandarpk> alsroot: can you please see http://paste.ubuntu.com/481528/ and http://paste.ubuntu.com/481526/
[18:18] <alsroot> kandarpk: that won't work because DevTutorActivity is uninitialized if /tmp/1 exists
[18:24] <kandarpk> alsroot: OK.
[18:24] <alsroot> kandarpk: in my mind all logic for what activity(class) will be started should be in "exec" (to be exact in bash script wich will be launched from "exec"), e.g. 'sugar-activity ${TUTOR_CLASS-DevTutorActivity} "$@"'
[18:25] <alsroot> s/TUTOR_CLASS-DevTutorActivity/TUTOR_CLASS:-DevTutorActivity/
[18:27] <alsroot> if TUTOR_CLASS is not defined, "DevTutorActivity" will be used (to start main), main will start itself w/ defining TUTOR_CLASS envar to class of sub activity to start
[18:32] <kandarpk> alsroot: how can I set envar ?
[18:32] <alsroot> kandarpk: use subprocess module http://docs.python.org/library/subprocess.html, see "env" argument that could be passed to subprocess.call() method
[18:33] <alsroot> kandarpk: also see how subprocess is used in sugar code code and other activities
[18:39] <kandarpk> alsroot: I didn't understand 'sugar-activity ${TUTOR_CLASS:-DevTutorActivity} "$@"'
[18:40] <alsroot> kandarpk: that should be in launch script http://pastebin.org/676637, use its name as "exec" value in actiivty.info and it will be started
[18:42] <alsroot> otherwise (if you will use this string as "exec" value), sugar won't expand "${TUTOR_CLASS:-DevTutorActivity}"
[18:43] <alsroot> ..afaik
[18:44] <kandarpk> alsroot: how is "${TUTOR_CLASS:-DevTutorActivity}" expanding ?
[18:45] <kandarpk> it doesn't seem to be bash string operation
[18:45] <alsroot> kandarpk: it is a bash (see man bash), if TUTOR_CLASS is defined, it will be expanded, otherwise "DevTutorActivity" will be used
[18:46] <kandarpk> alsroot: OK.
[18:53] <kandarpk> alsroot: why do we need to include "$@" ?
[18:54] <alsroot> kandarpk: it will be expanded to the args that sugar will pass to "exec" value eg -o or -a
[18:55] <kandarpk> alsroot: can we add these parameters in activity.info ?
[18:55] <kandarpk> does that work ?
[18:56] <alsroot> kandarpk: sugar launch "exec" in non shell mode (see subprocess do page) thus all these stuff won't be expanded
[18:57] <kandarpk> alsroot: I mean -o and -a flags, can we use them ?
[18:58] <alsroot> kandarpk: nope, only sugar knows what values for these arguments are
[18:59] <kandarpk> alsroot: OK, thanks.
[19:48] <manusheel> kandarpk: Hi kandarp.
[19:48] <manusheel> Around?
[19:48] <kandarpk> manusheel sir: hello sir.
[19:48] <manusheel> kandarpk: Neat description.
[19:49] <manusheel> However, I am not sure on how the activity could take inputs from other Sugar activities.
[19:49] <kandarpk> manusheel sir: we are almost there
[19:49] <kandarpk> manusheel sir: alsroot has provided some pointers.
[19:50] <manusheel> kandarpk: Neat.
[19:50] <manusheel> That is great to hear.
[19:51] <kandarpk> manusheel sir: we'll be able to run complete activity from our activity, will need to insert some markers in other activities to create different parts.
[19:51] <kandarpk> or study different modules in them.
[19:51] <manusheel> kandarpk: Can't we have a function, which can do it at our end?
[19:52] <kandarpk> manusheel sir: that will be a bit difficult.
[19:52] <manusheel> kandarpk: Inserting markers in other activities means running around and having a word with lot of activity authors.
[19:52] <manusheel> kandarpk: Let us see if we can do that. Sure, it will need some understanding.
[19:53] <kandarpk> manusheel sir: the activity is structured to understand other activities.
[19:54] <manusheel> kandarpk: Right, Kandarp.
[19:54] <kandarpk> manusheel sir: I was thinking instead of making use of modules to show their functionality, we could use the already existing ones, i.e. other activities.
[19:55] <manusheel> kandarpk: That is another approach. However, think like a developer writing the first activity in Sugar.
[19:56] <manusheel> kandarpk: You won't be interested in browsing through all the activities and understanding modules in them.
[19:56] <kandarpk> manusheel sir: yes sir, that is where our activity helps.
[19:56] <manusheel> kandarpk: Right.
[19:57] <kandarpk> manusheel sir: by inserting markers, we show the output after each module is included, which makes their functionality clear
[20:00] <manusheel> kandarpk: Ok. let me think about it more.
[20:00] <manusheel> kandarpk: Let me talk to you in 5 mins.
[20:00] <kandarpk> manusheel sir: OK sir.
[20:03] <manusheel> kandarpk: Back.
[20:03] <manusheel> kandarpk: Yes, inserting markers/indicators is good. But, we'll have to determine a way to do this at our end through some function.
[20:03] <kandarpk> manusheel sir: what approach should we follow ?
[20:04] <kandarpk> manusheel sir: that means automating the process of inserting the markers ?
[20:04] <manusheel> kandarpk: Yes, I think we need to maintain a dictionary.
[20:05] <manusheel> kandarpk: This dictionary relates to the modules and sub modules as they are used.
[20:08] <manusheel> kandarpk: How does that sound?
[20:08] <kandarpk> manusheel sir: sounds great.
[20:09] <manusheel> kandarpk: Ok, let us try this approach.
[20:10] <kandarpk> manusheel sir: moreover most part of a module is used continuesly
[20:10] <manusheel> kandarpk: Right.
[20:10] <manusheel> kandarpk: What all have we accomplished right now for a developer, can you summarize in points -
[20:11] <kandarpk> manusheel sir: 1) if we place an activity under our activity, we can launch that activity.
[20:12] <kandarpk> manusheel sir: 2) the basic GUI is prepared to show steps in an activity
[20:13] <manusheel> kandarpk: Ok. Most importantly, how about the usage of modules?
[20:14] <kandarpk> manusheel sir: right now, we need to manually break an activity into steps and show the usage accordingly.
[20:15] <manusheel> kandarpk: Ok, we mean that we have someone sitting next to the beginner, who knows Sugar.
[20:15] <kandarpk> alsroot: if I use 'exec = activityname.sh' in activity.info, will activityname.sh run as normal bash script ?
[20:15] <kandarpk> manusheel sir: yes sir.
[20:16] <manusheel> kandarpk: Who is breaking the activity into a number of modules, and then explaining the person.
[20:16] <kandarpk> manusheel sir: correct.
[20:16] <alsroot> kandarpk: yup, but you need to place it to bin/ directory
[20:16] <manusheel> kandarpk: Sure, it is a good use-case. But, very few times, we can have that scenario.
[20:17] <kandarpk> alsroot: will 'exec = ../activityname.sh' work ?
[20:18] <manusheel> kandarpk: So, we should focus on our original use-case. Of automating the procedure.
[20:18] <alsroot> kandarpk: nope, use just "activityname.sh" and place script to bin/ subdirectory, don't remember all details but it should work
[20:19] <kandarpk> manusheel sir: definitely, that way, if anyone wants to undertand an activity, he can just place the activity under our activity.
[20:20] <kandarpk> alsroot: OK.
[20:22] <manusheel> kandarpk: Yes, absolutely.
[20:49] <kandarpk> alsroot: around ?
[20:49] <alsroot> kandarpk: yup
[20:49] <kandarpk> alsroot: please see http://paste.ubuntu.com/481583/
[20:51] <alsroot> kandarpk: you are trying to run command w/ name "sugar-launch org.sugarlabs.DevTutor", you need t use ['sugar-launch', 'org.sugarlabs.DevTutor']
[20:51] <kandarpk> alsroot: OK.
[20:53] <kandarpk> alsroot: I tried to understand how to use env variable in Popen.
[20:53] <kandarpk> alsroot: it is only being used to set PATH variable
[20:54] <alsroot> kandarpk: initialize your env variable w/ os.environ value (which is a copy of current envars), then just add your envar
[20:55] <kandarpk> alsroot: OK.
[20:59] <mukul> alsroot: hi
[21:00] <alsroot> mukul: hi
[21:02] <mukul> alsroot : I was looking at the bug #621898 with the link https://bugs.launchpad.net/ubuntu/+source/sugar-0.88/+bug/621898
[21:02] <ubot2> Launchpad bug 621898 in sugar-0.88 (Ubuntu) "Copy in right click menu doesnot work in sugar emulator (affects: 2) (heat: 16)" [Undecided,New] https://launchpad.net/bugs/621898
[21:02] <ubot2> mukul: Error: Bug #621898 is private.
[21:03] <mukul> alsroot: Where will I find the source code relating to the above problem?
[21:04] <alsroot> mukul: just grep sugar sources for "'Copy'" string, it is src/jarabe/journal/palettes.py
[21:05] <alsroot> mukul: btw I'm sure it is a bug, i.e. Copy mean copy file to clipboard
[21:05] <alsroot> s/I'm/I
[21:05] <alsroot> 'm not/
[21:05] <mukul> alsroot: Ok, It copies to the clipboard but how to we then paste it
[21:06] <alsroot> mukul: open clipboard (left framebar) and choose "Keep" menu item on copied item
[21:07] <mukul> alsroot: That doesn't copy too
[21:07] <mukul> alsroot: I noticed only the drag worked for me
[21:08] <alsroot> mukul: then it is a bug, Copy works fine in (git) sugar
[21:15] <kandarpk> alsroot: subprocess is working :)
[21:15] <kandarpk> alsroot: thanks a lot.
[21:16] <alsroot> yw
[21:29] <mukul> alsroot: Sorry, I had got disconnected.
[21:30] <mukul> alsroot: If right click-->copy then keep seems to be working for now
[21:32] <alsroot> mukul: in fact, after choosing Copy, clipboard icon should flash to let users know about adding new item to clipboard
[21:32] <mukul> alsroot: However,how are we supposed to copy something from journal to the USB, except for dragging
[21:32] <alsroot> mukul: there are only two UI ways, dragging and via clipboard
[21:32] <alsroot> afaik
[21:34] <alsroot> there is also panel menu "Journal" for Copy button in details dialog
[21:34] <alsroot> ..but it is too hidden
[21:34] <mukul> alsroot: To copy from USB to Journal works fine via clipboard as well as dragging. But while copying from the Journal to the USB, only dragging seems to be the way
[21:35] <alsroot> mukul: yup, because "Keep" in clipboard menu means "Keep in journal"
[21:36] <mukul> alsroot: Yes
[21:36] <mukul> alsroot: Then the bug mentioned at launchpad is not actually a bug right?
[21:37] <alsroot> mukul: yup, it is a feature :)
[21:37] <manusheel> mukul: Yes, it is a feature request.
[21:37] <manusheel> mukul: It is mentioned like a bug.
[21:38] <manusheel> Bugs and feature requests are managed in the same bug tracker.
[21:39] <mukul> manusheel sir: Okay
[21:40] <mukul> alsroot: How to I resolve it?
[21:40] <alsroot> mukul: well, thats the question :)
[21:42] <alsroot> mukul: you can create new menu item in palette in src/jarabe/journal/palettes.py, but anyway it sound like a user visible feature that could affect users experience, better to discuss proper implemnettion on sugar-devel@ (post an email w/ tag [DESIGN])
[21:46] <mukul> I 'grep'ed 'Copy' in the file
[21:47] <mukul> alsroot: I had another doubt. There is no provision to copy multiple files at a time.Is that possible?
[21:49] <alsroot> mukul: only by dragging one after another
[21:50] <mukul> alsroot: If that feature has to be implemented, how is to be done?
[21:50] <alsroot> mukul: see the code which will be called after clicking "Keep" button on clipbord menu
[21:52] <mukul> alsroot: palettes.py doesn't contain 'Keep'
[21:53] <alsroot> mukul: grep it in entirely sugar project, it lives in clipboardmenu.py
[22:01] <mukul> alsroot: I am having a look at the code which is called after clicking Keep
[22:30] <manusheel> alsroot: Hi Aleksey. Around?
[22:31] <alsroot> manusheel: hi
[22:31] <manusheel> alsroot: Thank you so much for your guidance to SEETA team. They highly appreciate your time and effort.
[22:32] <manusheel> alsroot: Appreciate it.
[22:32] <alsroot> manusheel: np, I'm just trying to not forget sugar code while coding 0sugar :)
[22:33] <manusheel> alsroot: Great.
[22:34] <manusheel> alsroot: Wish to have your feedback on a couple of questions related to our earlier discussion on switching the framework of A.S.L.O from Remora to Django.
[22:34] <alsroot> manusheel: sure
[22:35] <manusheel> alsroot: Django is python based and Remora is cake php based. When we shift the framework from Remora to Django, we'll be refactoring code according to Django. Right? Not, re-writing cakephp code to Python code? We might have to do this for a couple of modules. But, not for all.
[22:36] <alsroot> manusheel: just how it will be useful in your case
[22:37] <alsroot> manusheel: I didn't take a look to new AMO code base, if it's too different to previous one, maybe just reimplement ASLO patch from basic things would be useful
[22:39] <manusheel> alsroot: Can you send me the link of new AMO? I am not sure we have gone through that.
[22:40] <alsroot> manusheel: https://wiki.mozilla.org/AMO:Developers
[22:42] <manusheel> alsroot: Zamboni is a python based completely. Does that mean the cakephp developers will be learning Python and re-writing the whole of it to Python?
[22:44] <alsroot> manusheel: well, we have to follow mozilla in any case (otherwise we will have unmaintained AMO)
[22:44] <alsroot> at least in my mind
[22:46] <manusheel> alsroot: Ok. But, the structure of Django is pretty different from Remora. Both follow MVC architecture. However, Remora places all the files (i.e. uploader.php, version.php and others) in folder for M, V and C respectively. But, in Django, we'll have to create seperate directories for each functionality. One directory for uploader; one for versions etc.
[22:47] <alsroot> manusheel: thats why I thought about reimplementing ASLO patch and startr from doing basic things
[22:49] <manusheel> alsroot: Ok. Sure. We are focusing on the upload of xo files only at this juncture.
[22:50] <manusheel> alsroot: We have boiled down the files in Model, View and Controller section in Remora that manages uploads.
[22:50] <manusheel> We'll re-write them to see how they work in Zamboni.
[22:51] <alsroot> manusheel: thanks