[15:42] <manusheel> kandarpk: Hi Kandarp.
[15:42] <manusheel> Around?
[15:42] <kandarpk> manusheel sir: hello sir
[15:43]  * ishan is going for dinner
[15:46] <manusheel> kandarpk: How is the activity coming along?
[15:46] <manusheel> Any help needed?
[15:47] <kandarpk> manusheel sir: about to consult alsroot on it.
[15:47] <kandarpk> alsroot: around ?
[15:47] <alsroot> kandarpk: yup
[15:47] <kandarpk> alsroot: I could launch other activities by including their source and providing their activity name.
[15:49] <kandarpk> alsroot: now the idea is to break the activity into different steps as the modules are included in it so as to understand the functionality of these modules
[15:49] <kandarpk> s/as the modules are included/when the modules are included/
[15:50] <alsroot> kandarpk: what about just creating different modules for every new stage (w/ copying code from previous stage)
[15:51] <kandarpk> alsroot: yes, that is what I meant.
[15:52] <kandarpk> alsroot: instead of creating new modules, can we use the existing activities ?
[15:53] <alsroot> kandarpk: the problem is that sugar doens't support dependencies, so you can't be sure that all needed activities are installed
[15:54] <kandarpk> alsroot: what about using the activities installed on the machine ?
[15:55] <alsroot> kandarpk: you mean any activities that are installed, not particular ones?
[15:55] <kandarpk> alsroot: yes.
[15:56] <alsroot> kandarpk: sugar-launch will start them anyway
[15:56] <alsroot> but you need to know their bundle_id
[15:57] <kandarpk> alsroot: actually, we wanted to automate the process ofinserting markers into the existing/installed activities so as to split it into different steps
[15:58] <kandarpk> s/ofinserting/of inserting/
[15:58] <alsroot> kandarpk: you mean changing source code of other activities?
[15:58] <kandarpk> alsroot: is that feasible ?
[15:59] <kandarpk> alsroot: the source will be copied into our activity's directory and changes will be made there
[16:01] <alsroot> kandarpk: well, it will be possible, at least you can find all instlaled activities using sugar.env.get_user_activities_path()
[16:02] <alsroot> kandarpk: and sugar.bundle.ActivityBundle to parse its activity.info
[16:02] <alsroot> *theirs
[16:03] <kandarpk> alsroot: copying isn't a problem right now. We can manually add some activities ourself instead of checking for installed activities
[16:04] <kandarpk> alsroot: for the time being.
[16:05] <kandarpk> alsroot: I was more interested in inserting markers.
[16:06] <kandarpk> alsroot: to create something like http://seeta.in/sugar/api/documentation/activity/Screenshots/Screenshot-1.1.png
[16:07] <kandarpk> alsroot: instead of description we can show the commands used
[16:08] <alsroot> kandarpk: well, changing source in automated manner might be a problem, what about just using prepared code
[16:10] <kandarpk> alsroot: will that be good enough ?
[16:10] <kandarpk> alsroot: if we add 2-3 activities and show their functionality ...
[16:10] <alsroot> kandarpk: why not
[16:15]  * ankur is going for dinner
[17:28] <kandarpk> manusheel sir: read is getting launched from inside DevTutor.
[17:29] <kandarpk> I copied all the .py files and passed ReadActivity as the name of class which should be initiated.
[17:30] <kandarpk> **copied .py files from Read to DevTutor.
[18:12] <manusheel> kandarpk: Awesome
[18:12] <manusheel> This is great.
[18:13] <kandarpk> manusheel sir: and read isn't updated.
[18:13] <manusheel> kandarpk: Ok.
[18:13] <kandarpk> so it is just launching for now.
[18:13] <manusheel> kandarpk: Let me call you in 30 mins to discuss on this.
[18:13] <kandarpk> manusheel sir: fine sir.
[18:45] <kandarpk> manusheel sir: write is getting launched perfectly.
[18:46] <kandarpk> manusheel sir: will add some breakpoints into it now.
[18:52] <kandarpk> manusheel, http://bugs.sugarlabs.org/ticket/1900
[19:02] <kandarpk> manusheel sir: evince.document_factory_get_document has been changed to evince.document_factory_get_document
[19:02] <kandarpk> manusheel sir: http://stackoverflow.com/questions/3411929/simple-hello-world-program-for-python-evince
[19:05] <kandarpk> **evince.factory_get_document has been changed to evince.document_factory_get_document
[19:06] <kandarpk> and some other changes at ^^
[19:17] <manusheel> kandarpk: Can you send me the link to that file on bugs?
[19:18] <kandarpk> manusheel sir: http://bugs.sugarlabs.org/ticket/1900 << this one ?
[19:20] <manusheel> kandarpk: Does it list all the bugs in activities?
[19:20] <manusheel> The one we just discussed.
[19:21] <kandarpk> manusheel sir: OK, looking for that in the e-mail.
[19:36] <manusheel> kandarpk: Sure, Kandarp.
[19:36] <kandarpk> manusheel sir: sent.
[19:42] <manusheel> kandarpk, thanks.
[20:00] <ishan> alsroot, hi
[20:00] <alsroot> ishan: hi
[20:01] <ishan> alsroot, i want to know how a activity uses a server for collaboration
[20:02] <ishan> can you guide me in which file i could find the code for this
[20:03] <alsroot> ishan: you can start from reading James Simmons tutorial http://en.flossmanuals.net/ActivitiesGuideSugar/SugarCollaboration
[20:03] <ishan> alsroot, okay
[20:04] <kandarpk> manusheel sir: some screenshots after inserting breakpoints in write :
[20:04] <kandarpk> http://seeta.in/sugar/api/documentation/activity/write_screenshots/
[20:05] <alsroot> ishan: there is also hello-world example activity http://git.sugarlabs.org/projects/hello-mesh/