Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate

#sugar-newbies, 2016-07-02

 « Previous day | Index | Today | Next day »     Channels | Search | Join

All times shown according to UTC.

Time Nick Message
10:59 meeting <meeting!~sugaroid@rev-18-85-44-69.sugarlabs.org> has joined #sugar-newbies
15:10 iamutkarshtiwari <iamutkarshtiwari!0e8bee62@gateway/web/freenode/ip.> has joined #sugar-newbies
15:14 iamutkarshtiwari has quit IRC
15:42 iamutkarshtiwari <iamutkarshtiwari!0e8bee62@gateway/web/freenode/ip.> has joined #sugar-newbies
15:46 iamutkarshtiwari has quit IRC
16:23 iamutkarshtiwari <iamutkarshtiwari!0e8bee62@gateway/web/freenode/ip.> has joined #sugar-newbies
16:36 tony37 <tony37!~tony@93-137-177-21.adsl.net.t-com.hr> has joined #sugar-newbies
16:36 tony37 Hello
16:37 iamutkarshtiwari hello
16:37 tony37 and the topic for today is?
16:38 iamutkarshtiwari #FixingYourSaveAsIssue
16:38 tony37 Ok
16:38 iamutkarshtiwari Did you install teamviewer?
16:38 tony37 No, I don't think that is necessary.
16:39 iamutkarshtiwari I need to have a look at the sugar-build you are using.
16:39 I think I can help you :)
16:39 tony37 I am not using sugar-build
16:39 iamutkarshtiwari Then how did you test my patch?
16:39 tony37 I replaced the files in my image with your files
16:40 iamutkarshtiwari image?
16:40 #startmeeting
16:40 meeting Meeting started Sat Jul  2 16:40:24 2016 UTC. The chair is iamutkarshtiwari. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:40 tony37 You are familiar with the OLPC OS images on laptop.org
16:40 meeting Useful Commands: #action #agreed #help #info #idea #link #topic #endmeeting
16:40 iamutkarshtiwari Yes.
16:40 tony37 I am using the 13.2.5 image
16:40 iamutkarshtiwari I am not familiar with image packing.
16:41 I would be better if you test the patches on sugar-build
16:41 It*
16:41 tony37 Why?
16:41 iamutkarshtiwari Might be that the technique
16:41 of placing files requires making
16:41 more changes to the image
16:41 than just 'replacing files' and modifying
16:41 'makefile.am'
16:42 tony37 You are right because there is not telling what is in an 'os build'. An image is fixed so we can know we are using the same code.
16:42 iamutkarshtiwari Are you using linux?
16:42 tony37 Makefile is not relevant in this case.
16:43 Of course, Sugar is a Fedora remix
16:43 iamutkarshtiwari No. I meant OS on your laptop/desktop
16:44 tony37 Sadly, this is one of the problems with GSOC. As a participant, you have had no opporunity to work with a deployed version of Sugar. Only in the developer's environement
16:44 That is why I consider the XO-1.75 critical.
16:44 iamutkarshtiwari oh.. Did you try placing my files on an XO-1.75 ?
16:44 tony37 Yes
16:45 iamutkarshtiwari What were the results?
16:45 tony37 Same
16:45 Nothing happened.
16:45 The problem is more difficult on the Sugar Ubuntu image. There are permission issues since the Activities have been moved to /usr/share/sugar/activities and are owned by root
16:46 In addition, the user is not 'olpc' but the Linux login username.
16:46 iamutkarshtiwari Can you guide me test those files on my XO?
16:46 tony37 In debugging, I use the Log activity to see if there are any errors or exceptions logged
16:47 Yes. I think that will be very valuable.
16:47 iamutkarshtiwari I need to see what is the exact issue. From my side the feature is complete and works as expected.
16:47 tony37 Have you tried it on a released image such as 13.2.5 (there is a later release 13.2.7 also)?
16:48 Incidentally, the Write activity has been ported to sugar3
16:48 iamutkarshtiwari The patches are based on Gtk3
16:49 tony37 That is why that is important. We need a sugar3 activity to test.
16:49 iamutkarshtiwari on my sugar-build the 'write' acitivity is already ported to gtk3
16:49 tony37 and mine
16:51 The development team operates in a different world that those of us in the field. One of the confusions they create is the impression that Sugar activities are part of Sugar.
16:51 The activities are independent programs supported by Sugar. Changes to activities are not related to Sugar releases or osbuild.
16:53 We sometimes encourage users to modify Sugar to make it work for them. Hence, the view source feature.
16:53 iamutkarshtiwari I'll be replacing the files in my XO. Before that I need to make a backup of the 'activitiy.py' and the 'alerts.py' ?
16:53 tony37 I think that is prudent, I do the same.
16:55 iamutkarshtiwari Where do I need to
16:55 tony37 One caution, on the 'resume' feature, I have made coding errors. This results in an unusable system (had to reflash the image). The homeview.py and favoritesview.py are executed at boot time to display the home page. If there is an exception, the system keeps retrying.
16:55 iamutkarshtiwari place the files in XO?
16:56 tony37 Get on your XO-1.75 and launch the Terminal. You will find the layout is exactly what you expect. For example, the sugar3 activity.py is in /usr/lib/python2.7/site-packages/sugar3/activity/
16:57 iamutkarshtiwari I am not familiar with all the terminal commands.
16:57 tony37 I tend to do something live mv activity.py to save-activity.py and then load the test version.
16:57 Note: on an XO-1.75 you must be root - either sudo or su. However, there is no root password.
16:58 Standard bash shell
16:58 One nice feature of Terminal is that it has tabs.
16:59 For fiddler, I had one tab open to /home/olpc/Activities/Browse.activity and another to /home/olpc/.sugar/default/org.laptop.WebAct​ivity2/instance/Web_Console_Files/default/
17:00 iamutkarshtiwari It's pretty tricky as compared to testing on 'sugar-build'
17:00 I need to first figure out all the necessay terminal commands. I use 'terminal' but not in depth.
17:01 necessary*
17:01 I'll test my patch after the meeting *because it will take time*
17:02 And let you know the issues on mail.
17:02 #ActivityResume
17:02 tony37 Agreed. Learning the shell is very valuable.
17:02 Go
17:03 iamutkarshtiwari The two files homeview.py and
17:03 favouritesview.py
17:03 Where do I need to make the changes.?
17:04 And I want to added the 'toggle' setting to gsettings, how to do it?
17:04 if I*
17:04 tony37 Your task! My suggestion is to read the code looking for the boolean that sets the mode. The goal here is to set this boolean by gsetting so that it either defaults to resjme or defaults to star new.
17:05 I don't know gsettings. Probably need to Google. This is a new configuration tool (the third in our history - starting with an ini file, then gconf and now gsetting.
17:05 iamutkarshtiwari Is the toggling settings already coded by Sugar developers ?
17:06 tony37 The boolean is there. The problem is that it is set by the 'alt' key - so the trick will be to ensure that the setting is consistent through the changes.
17:07 For example, if default is start new, then the alt key should switch to resume while pressed.
17:09 iamutkarshtiwari Currently the 'alt' key toggle the 'start new' -> 'resume' and vice versa ?
17:09 toggles*
17:09 tony37 Yes beginning with a default of 'resume mode'
17:10 iamutkarshtiwari And if I press the 'alt' key once, it changes to 'start new mode' ?
17:11 Oh! I get it :D
17:11 What we need to do is, remove the 'alt' key for toggle.
17:11 and make it consistent thoughtout sugar.
17:11 tony37 While you hold it down. You can see in the home view because the colors are present in resume mode but the start new is in black and white
17:12 iamutkarshtiwari If the user what's to change, he has to do it by the terminal?
17:12 tony37 No, just configure the default to one or the other. After that alt should toggle.
17:13 iamutkarshtiwari The toggle should happen with just one click instead of pressing the 'alt key' consistenly?
17:13 tony37 For now, we don't need to provide a user capability to set the default. This can be done at install time by a bash script.
17:14 I think we can leave it as a toggle from the default only while it is pressed (e.g. recognize key down and key up).
17:15 At some point, we should provide user configuration options through the control panel. But that is not in place at present.
17:16 iamutkarshtiwari How should that 'user configuration' option look like?
17:16 Could you please provide me UI mockup?
17:16 tony37 I am thinking along the lines of the Firefox 'about:config'
17:17 I am saying that this option is not available at present. There is no control panel option to set gsetting configuration options. I think it beyond our scope to implement that.
17:18 iamutkarshtiwari So we need to provide a settign in 'about:config' of Browse-activity for the user to change that 'toggle' setting ?
17:18 tony37 If I were doing it, I would try to have a control panel section that displays a list of the gsettings (probably gtk listview) with the user able to select one and edit it
17:19 This would be accessed by 'mysettings' not Browse.
17:19 iamutkarshtiwari I think we should discuss it on sugar-devel, so that we can get community consensus.
17:20 With everyone's agreement we can proceed as required.
17:20 tony37 I am saying - don't do it. It is another project beyond our scope.
17:20 iamutkarshtiwari Oh..
17:20 tony37 Simply provide a configuration option that can be set from the command line.
17:20 iamutkarshtiwari Ok.
17:21 How should the command look like ?
17:21 tony37 I believe these options are specified in a text file, possibly in /usr/share.
17:21 You can google gsettings to get documentation on how it works.
17:22 iamutkarshtiwari To summarize- I need to make a configuration to allow the user to change(boolean) the 'resume/start-new mode' from terminal?
17:23 tony37 Yes, exactly
17:23 iamutkarshtiwari For that I would be needing help from sugar-devel. I'll start a new thread for the same.
17:24 tony37 Why do you need help from sugar-devel?
17:25 iamutkarshtiwari They might give some nice ideas.
17:25 tony37 The reason I am asking is that when you pose a question there, developers will need take their time to respond. They appreciate it when you do the research on your own.
17:25 iamutkarshtiwari Oh.. I agree.
17:27 tony37 You need to discuss any changes to Sugar that you propose to make that affect the current way it works. I like to make changes which are compatible with the Sugar, but offer additional capabiliies at the user's option.
17:27 That is one of the reasons that I consider the resume option a mistake, it was an incompatible change to sugar from the default of start new.
17:28 Naturally, these changes need to be presented to Sugar_devel with the PR.
17:28 iamutkarshtiwari I'll look into the code and go through getting configuration.
17:28 tony37 Great!
17:28 iamutkarshtiwari And Will also test the patch on my XO.
17:29 I can't wait to show you how it works.
17:30 Let's meet tomorrow at the same time.
17:30 tony37 When I am coding, I try to have a method to determine when the code fails, how far did it get (same concept as breakpoints). In Sugar, this often involves print statements. I have never learned to use the 'logging' module.
17:30 iamutkarshtiwari I do make use of 'print' in python for sugar.
17:31 When I send you a patch.
17:31 tony37 So if the code doesn't show an alert, I would try to find how far it got. Note: the log shows exceptions but often the code just goes away.
17:31 iamutkarshtiwari I make sure that it looks clean
17:31 I'll try it my end with 'print' statements.
17:31 Will let you know the errors.
17:31 tony37 OK. The problem may turn out to be in my test. Let me know if it works for you so we can investigate what is happening at my end.
17:32 Bye, see you tomorrow.
17:32 iamutkarshtiwari Sure.
17:32 Bye
17:32 17 UTC
17:32 tony37 has quit IRC
17:32 iamutkarshtiwari has quit IRC

 « Previous day | Index | Today | Next day »     Channels | Search | Join

Powered by ilbot/Modified.