Re: [Sugar-devel] sugar-build after osbuild change report
On 05/20/2013 07:43 PM, Simon Schampijer wrote: On 05/20/2013 05:52 PM, Daniel Narvaez wrote: On 20 May 2013 12:48, Daniel Narvaez dwnarv...@gmail.com wrote: Ok, great. Would be fantastic if '--help' would print the list of possible arguments. I'd like to avoid maintaining the docs in two places :) Though perhaps using docker we can figure out something to have both --help and the docs be generated from the same source. I have made it print out the list of commands only (no descriptions) for now, with a link to the docs. Thanks Daniel! [sugar-build sugar-build]$ ./osbuild --help Don't run osbuild inside a sugar-build shell, you can just run the commands directly. [sugar-build sugar-build]$ exit [erikos@t61 sugar-build]$ ./osbuild --help = Setup osbuild = * Create the python virtualenv * Install python packages = Available commands = shell run check-config docs clean check build bug-report check-system pull See also http://developer.sugarlabs.org/build.md.html [erikos@t61 sugar-build]$ Pulling today I got: [erikos@t61 sugar-build]$ ./osbuild pull = Updating build system = * Pulling sugar-build Already up-to-date. = Pulling = * Pulling automake * Pulling glib * Pulling gobject-introspection * Pulling pygobject * Pulling dbus-python * Pulling libsoup * Pulling webkitgtk Command failed, tail of /home/erikos/sugar-build/build/logs/pull-0.log Already up-to-date. From git://github.com/dnarvaez/webkitgtk 23a61f3..562e907 master - origin/master error: Your local changes to the following files would be overwritten by merge: GNUmakefile.in aclocal.m4 configure Please, commit your changes or stash them before you can merge. Aborting Updating 23a61f3..562e907 I did not have made any changes in webkitgtk, I did a git reset --hard origin in the webkitgtk directory and now things work. Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] sugar-build after osbuild change report
On 21 May 2013 10:15, Simon Schampijer si...@schampijer.de wrote: Pulling today I got: [erikos@t61 sugar-build]$ ./osbuild pull = Updating build system = * Pulling sugar-build Already up-to-date. = Pulling = * Pulling automake * Pulling glib * Pulling gobject-introspection * Pulling pygobject * Pulling dbus-python * Pulling libsoup * Pulling webkitgtk Command failed, tail of /home/erikos/sugar-build/**build/logs/pull-0.log Already up-to-date. From git://github.com/dnarvaez/**webkitgtkhttp://github.com/dnarvaez/webkitgtk 23a61f3..562e907 master - origin/master error: Your local changes to the following files would be overwritten by merge: GNUmakefile.in aclocal.m4 configure Please, commit your changes or stash them before you can merge. Aborting Updating 23a61f3..562e907 I did not have made any changes in webkitgtk, I did a git reset --hard origin in the webkitgtk directory and now things work. Yeah, that one is hard to fix... I tried to stash changes but that triggers other issues. The easiest approach is probably to fix webkigtk to not regenerate those files, but I haven't yet figured out how/when they are written. I couldn't even reproduce it anymore here after I added a .gitignore. So, I'll try to fix this up but until then people should git reset --hard origin (hopefully I'm not going to update webkitgtk again before I solve it, so it should only be needed one time). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] HTML Sugar: Unit testing research
On 21 May 2013 01:47, Manuel Quiñones ma...@laptop.org wrote: So if we were to follow fashion, Mocha would be the one :P . But I think the simplistic approach of Jasmine is good enough for us, specially considering the involvement of new devs. Jasmine is a bit more readable and elegant too. The only thing we should consider is the async support, if we can go with Jasmine one, or if we need Mocha one. http://pivotal.github.io/jasmine/#section-Asynchronous_Support We should run into async code tests pretty soon, let's see how good/bad it is to write them in Jasmine. If we can I'd rather stick with the simpler framework, but async tests are probably going to be pretty important, so this is something we need to keep an eye on. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] HTML Sugar: Unit testing research
On 21 May 2013 01:47, Manuel Quiñones ma...@laptop.org wrote: I gave a try to Intern http://theintern.io/ . It looks quite interesting and can do both, BDD and TDD, and async. But 1. is too new (released a few days ago) and 2. unless we want continuous integration support (CI) or Selenium support, we don't need it. Agreed. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] HTML Sugar: Unit testing research
2013/5/21 Daniel Narvaez dwnarv...@gmail.com: On 21 May 2013 01:47, Manuel Quiñones ma...@laptop.org wrote: So if we were to follow fashion, Mocha would be the one :P . But I think the simplistic approach of Jasmine is good enough for us, specially considering the involvement of new devs. Jasmine is a bit more readable and elegant too. The only thing we should consider is the async support, if we can go with Jasmine one, or if we need Mocha one. http://pivotal.github.io/jasmine/#section-Asynchronous_Support We should run into async code tests pretty soon, let's see how good/bad it is to write them in Jasmine. If we can I'd rather stick with the simpler framework, but async tests are probably going to be pretty important, so this is something we need to keep an eye on. Agreed. Async tests will be important for us. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Tests for online service support
On 20 May 2013 12:39, Daniel Narvaez dwnarv...@gmail.com wrote: * All the Account methods returns what expected. * All the MenuItem signals are emitted as expected. * Calling set_metadata results in the expected change to the journal object. On a second thought I'm not sure it make sense to test these last three points. You would be basically testing the mock service implementation, the real code is just interfaces, and I'm not sure there is any test we need to do on those? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Getting karma to work with sugar-activity-html
2013/5/20 Manuel Quiñones ma...@laptop.org: 2013/5/20 Daniel Narvaez dwnarv...@gmail.com: Accidentally sent the previous email. Sorry. New module with the test activity, I can transfer to sugarlabs if we agree on the approach. I'm pretty happy with it, it doesn't even require to touch toolkit. https://github.com/dnarvaez/sugar-html-test Excellent! So you have the executable in it, and you added a new --uri, great. Feel free to move sugar-html-test to sugarlabs user. sugar-launch improvements https://github.com/sugarlabs/sugar/pull/68 And you did some improvements in the go, great! I'll test and merge accordingly. sugar environment variables for html tests https://github.com/sugarlabs/sugar/pull/69 sugar-runner changes to use SUGAR_RUN_TEST https://github.com/sugarlabs/sugar-runner/tree/karma sugar-build changes, use SUGAR_RUN_TEST and run-karma command https://github.com/sugarlabs/sugar-build/tree/karma I checked out the karma branch, and got it working doing the change in karma.conf.js: browsers = ['sugar-html-test']; Then I did: $run-karma sugar-html-graphics/test/karma.conf.js Sugar started, the test activity opened, and after that I saw the karma output in shell.log 1369146597.616569 WARNING root: _Account.__set_current_activity_cb ESC[32mINFO [Chrome 25.0 (Linux)]: ESC[39mConnected on socket id n0CaTfj6LmRWe4SUfxN- Chrome 25.0 (Linux): Executed 1 of 2 ESC[1AESC[2KChrome 25.0 (Linux): Executed 2 of 2 ESC[1AESC[2KChrome 25.0 (Linux): Executed 2 of 2ESC[32m SUCCESSESC[39m (0.517 secs / 0.01 secs) 1369146636.664850 DEBUG root: new zoom level: 2 Great! I think we could improve that output moving it to a separate log file, and also setting colors to false in the karma conf file like: // enable / disable colors in the output (reporters and logs) colors = false; There are other configurations we could play with: // test results reporter to use // possible values: 'dots', 'progress', 'junit' reporters = ['progress']; // enable / disable watching file and executing tests whenever any file changes autoWatch = true; // Continuous Integration mode // if true, it capture browsers, run tests and exit singleRun = false; I think we should leave the current settings because is good to develop using karma interactively. It watches the js files for changes and re-runs. They can instead be overriden adding parameters to the karma start command. Minor: I got a non miningful message trying to run it without parameters (bash syntax error): [sugar-build sugar-build]$ ./osbuild run-karma File /home/manuq/prog/sugar-build/build/commands/run-karma, line 2 SUGAR_RUN_TEST=karma start $@ sugar-runner ^ SyntaxError: invalid syntax I put these together pretty quickly so there might be issues :) That aside, we still need to setup sugar-build so that it runs tests automatically for sugar-html-graphics, but that should be trivial on the top of this. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel -- .. manuq .. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Update docs
On 05/20/13 08:07, Daniel Narvaez wrote: If you could make that developer.sugarlabs.org http://developer.sugarlabs.org - http://sugarlabs.org/~buildbot/docs/index.md.html (notice the md) that would make my life a little easier. Done. What about doc.sugarlabs.org? Is it still current? Is someone still maintaining it? On 20 May 2013 12:18, Simon Schampijer si...@schampijer.de mailto:si...@schampijer.de wrote: On 05/20/2013 12:13 PM, Daniel Narvaez wrote: On 20 May 2013 12:07, Simon Schampijer si...@schampijer.de mailto:si...@schampijer.de wrote: On 05/20/2013 10:40 AM, Daniel Narvaez wrote: I think the buildbot slave which uploads the docs hasn't yet had a successfull build since the doc was changed, so no updates yet. I'm on it, I should have probably made all these changes a bit more gradually. Great! Did the infra team handed out the new docs url already? Nope :/ Hey Bernie, did you get to reserve us the sugar-doc url already? Cheers, Simon -- Daniel Narvaez -- Bernie Innocenti Sugar Labs Infrastructure Team http://wiki.sugarlabs.org/go/Infrastructure_Team ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Update docs
On 21 May 2013 17:21, Bernie Innocenti ber...@sugarlabs.org wrote: On 05/20/13 08:07, Daniel Narvaez wrote: If you could make that developer.sugarlabs.org http://developer.sugarlabs.org - http://sugarlabs.org/~buildbot/docs/index.md.html (notice the md) that would make my life a little easier. Done. Thanks! What about doc.sugarlabs.org? Is it still current? Is someone still maintaining it? At first sight only the sugar-network stuff looks recent. I know nothing about that though :) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] developer.sugarlabs.org is up
http://developer.sugarlabs.org/ This is work-in-progress but we eventually would like it to be the entry point for new developers. The documents are generated from markdown text files in the sugar-docs repository git://github.com/sugarlabs/sugar-docs.git If you want to make any change, pull requests are very welcome :) -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [sugar-build] Back green
The build slaves are all back green, so hopefully things are back to sanity. If you run into any issue please let me know. Unfortunately a clean clone might be necessary for stuff to work out of the box, if you haven't cloned recently. I will try to do changes more gradually and carefully in the future. -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] About web activities, webkit2 and backward compatibility
Question for the sugar-web-activities framework developers: * With the actual implementation, do we _really_ need webkit2? You can say, why? We already decided that! I know, but thinking in the following months: * If we continue going with webkit2, the only way to develop web activities, will be sugar-build. No real users can use that activities in a xo with sugar for at least 6 months more. * This means, there are little incentive for developers to create activities without users, or like in the case of Lionel, port custom (and working) web activities to the new framework. * If we use webkit, we can modify the way sugar-0.100 identify a web activity in the activity.info file, to make it backward compatible, and include the needed classes in the .xo, to use them if is executed in a old sugar. * We _need_ activities using the framework to make sure all is working ok, and check if we have all the needed pieces. I repeat, I know this was decided, but I think these are good enough arguments. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On 21 May 2013 20:31, Gonzalo Odiard gonz...@laptop.org wrote: Question for the sugar-web-activities framework developers: * With the actual implementation, do we _really_ need webkit2? Probably not. It should be easy to give it a try, the API didn't change that much. * If we continue going with webkit2, the only way to develop web activities, will be sugar-build. No real users can use that activities in a xo with sugar for at least 6 months more. You will also need to figure out how to provide the equivalent of the shell apisocket inside the activity. Same interface and partially different implementation might work. I repeat, I know this was decided, but I think these are good enough arguments. Personally I'm going to focus on building something that it's even worth considering to backport. We are pretty far from that goal yet. I don't see anything wrong with someone writing a backward compatible activity which can run the sugar-html-* stuff though. I think we also said that when we made the decision. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 4:04 PM, Daniel Narvaez dwnarv...@gmail.com wrote: On 21 May 2013 20:31, Gonzalo Odiard gonz...@laptop.org wrote: Question for the sugar-web-activities framework developers: * With the actual implementation, do we _really_ need webkit2? Probably not. It should be easy to give it a try, the API didn't change that much. * If we continue going with webkit2, the only way to develop web activities, will be sugar-build. No real users can use that activities in a xo with sugar for at least 6 months more. You will also need to figure out how to provide the equivalent of the shell apisocket inside the activity. Same interface and partially different implementation might work. Good point. I repeat, I know this was decided, but I think these are good enough arguments. Personally I'm going to focus on building something that it's even worth considering to backport. We are pretty far from that goal yet. I don't see anything wrong with someone writing a backward compatible activity which can run the sugar-html-* stuff though. I think we also said that when we made the decision. Great. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 12:31 PM, Gonzalo Odiard gonz...@laptop.org wrote: Question for the sugar-web-activities framework developers: * With the actual implementation, do we _really_ need webkit2? You can say, why? We already decided that! I know, but thinking in the following months: * If we continue going with webkit2, the only way to develop web activities, will be sugar-build. No real users can use that activities in a xo with sugar for at least 6 months more. webkit2 is included in F18 and is in OLPC builds. Has anyone checked if it is good enough to run the latest webapp stuff? There may be no need to go back to webkit1 if you want to continue on this path. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
webkit2 is included in F18 and is in OLPC builds. Has anyone checked if it is good enough to run the latest webapp stuff? There may be no need to go back to webkit1 if you want to continue on this path. I can'see webkit2 installed in 13.2.0, what is the package? [olpc@xo-1e-88-13 logs]$ rpm -qa | grep -i webkit webkitgtk3-1.10.2-3.fc18.armv7hl webkitgtk-1.10.2-3.fc18.armv7hl Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 1:44 PM, Gonzalo Odiard gonz...@laptop.org wrote: webkit2 is included in F18 and is in OLPC builds. Has anyone checked if it is good enough to run the latest webapp stuff? There may be no need to go back to webkit1 if you want to continue on this path. I can'see webkit2 installed in 13.2.0, what is the package? webkitgtk3 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
webkitgtk3 I think that is webkit, no webkit2 Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Getting karma to work with sugar-activity-html
On 21 May 2013 17:03, Manuel Quiñones ma...@laptop.org wrote: Feel free to move sugar-html-test to sugarlabs user. Done. I checked out the karma branch, and got it working doing the change in karma.conf.js: browsers = ['sugar-html-test']; I sent a pull request to make this change. Then I did: $run-karma sugar-html-graphics/test/karma.conf.js Sugar started, the test activity opened, and after that I saw the karma output in shell.log 1369146597.616569 WARNING root: _Account.__set_current_activity_cb ESC[32mINFO [Chrome 25.0 (Linux)]: ESC[39mConnected on socket id n0CaTfj6LmRWe4SUfxN- Chrome 25.0 (Linux): Executed 1 of 2 ESC[1AESC[2KChrome 25.0 (Linux): Executed 2 of 2 ESC[1AESC[2KChrome 25.0 (Linux): Executed 2 of 2ESC[32m SUCCESSESC[39m (0.517 secs / 0.01 secs) 1369146636.664850 DEBUG root: new zoom level: 2 Great! I think we could improve that output moving it to a separate log file, and also setting colors to false in the karma conf file like: Yeah, it also sucks for gtk tests. I will send patches for it. // enable / disable colors in the output (reporters and logs) colors = false; There are other configurations we could play with: // test results reporter to use // possible values: 'dots', 'progress', 'junit' reporters = ['progress']; // enable / disable watching file and executing tests whenever any file changes autoWatch = true; // Continuous Integration mode // if true, it capture browsers, run tests and exit singleRun = false; I think we should leave the current settings because is good to develop using karma interactively. It watches the js files for changes and re-runs. They can instead be overriden adding parameters to the karma start command. Yes I agree. I will just make buildbot use karma --single-run. Minor: I got a non miningful message trying to run it without parameters (bash syntax error): [sugar-build sugar-build]$ ./osbuild run-karma File /home/manuq/prog/sugar-build/build/commands/run-karma, line 2 SUGAR_RUN_TEST=karma start $@ sugar-runner ^ SyntaxError: invalid syntax That wrapper was pretty broken :) Pushed a proper one now, it's called just karma so it basically works transparently. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tue, May 21, 2013 at 2:02 PM, Gonzalo Odiard gonz...@laptop.org wrote: webkitgtk3 I think that is webkit, no webkit2 How are you coming to that conclusion? I just checked the spec file, webkit2 compilation is enabled, and the lib appears installed as /usr/lib/libwebkit2gtk-3.0.so.18.0.5 It is not as new as the version in F19 of course, but as far as I know nobody has investigated as to whether that really matters. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
I was confused by the rpm number, my mistake. [olpc@xo-1e-88-13 logs]$ rpm -ql webkitgtk3 | grep typelib /usr/lib/girepository-1.0/JSCore-3.0.typelib /usr/lib/girepository-1.0/WebKit-3.0.typelib /usr/lib/girepository-1.0/WebKit2-3.0.typelib Looks like the two libraries are packaged in the same rpm. On Tue, May 21, 2013 at 5:06 PM, Daniel Drake d...@laptop.org wrote: On Tue, May 21, 2013 at 2:02 PM, Gonzalo Odiard gonz...@laptop.org wrote: webkitgtk3 I think that is webkit, no webkit2 How are you coming to that conclusion? I just checked the spec file, webkit2 compilation is enabled, and the lib appears installed as /usr/lib/libwebkit2gtk-3.0.so.18.0.5 It is not as new as the version in F19 of course, but as far as I know nobody has investigated as to whether that really matters. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Marketing] Sugar 0.100 or 1.0
On Fri, May 17, 2013 at 6:21 AM, Walter Bender walter.ben...@gmail.com wrote: Perfection is the enemy of the good. On Fri, May 17, 2013 at 9:07 AM, Daniel Narvaez dwnarv...@gmail.com wrote: Hello, we need to decide if we want the next release to be 1.0 or 0.100. Here is the features we are planning for it. * Develop an HTML5 based toolkit for activities * Multiple selection in the Journal http://wiki.sugarlabs.org/go/Features/Multi_selection * Enhanced support for 3G modems http://wiki.sugarlabs.org/go/Features/3G_Support/Database_Support * Background customization http://wiki.sugarlabs.org/go/Features/Background_image_on_home_view * Multiple home views http://wiki.sugarlabs.org/go/Features/Multiple_home_views * Integration with web services http://wiki.sugarlabs.org/go/Features/Web_services * Journal comments box http://wiki.sugarlabs.org/go/Features/Comment_box_in_journal_detail_view * Icon customization http://wiki.sugarlabs.org/go/Features/Icon_Change It's a bit of weird situation because code wise we are not really 1.0 ready. We are developing a new toolkit and the old one could use an API cleanup. On the other hand we are deployed to millions of users. Personally I don't really have a strong feeling. If the marketing team sees an opportunity in a 1.0 in October with the above feature list I'd say to go ahead with it even if from a developer point of view we are not ready. Otherwise we could delay it at least another cycle. I think the marketing team had already reached consensus about 1.0. But maybe Sean can chime in. -- Daniel Narvaez ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing Plus, I think .100 is confusing. +1 Sameer -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Marketing mailing list market...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/marketing ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [Marketing] Sugar 0.100 or 1.0
On Mon, May 20, 2013 at 4:39 AM, Daniel Narvaez dwnarv...@gmail.com wrote: On 20 May 2013 12:19, Bastien b...@laptop.org wrote: Sean DALY sdaly...@gmail.com writes: I feel that 0.100 is even more unmarketable than 0.98. Agreed. Mathematically, it reads like a regression. Instead of reaching some definite level of maturity, it gives the signal that Sugar is in its early alpha (which is clearly wrong IMHO.) The problem is that Sean is also saying a 1.0 would be hard to market (without html activities, which I don't think are going to be solid at the first iteration). Speaking of activities in the Sugar sense, I was wondering how many of the HTML5 apps from FirefoxOS would slide over to our platform with little change. I just got my hands on a Geeksphone Peak (http://www.geeksphone.com/) and have been following up on how Mozilla does FirefoxOS apps. (As an aside, their apps live on Github, both as code and as zip files, and hosted through https://marketplace.firefox.com/ which looks similar on the phone as it does on a laptop). If some of the FirefoxOS apps can become Sugar HTML5 activities, we may be able to ramp up on the number of activities relatively soon. Wishful thinking, and all that... cheers, Sameer So I don't really know how we should call this release. Maybe 1.0 and we just don't make noise about it. Feels a bit like a lost opportunity though. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On Tuesday, May 21, 2013 05:09:38 PM Gonzalo Odiard wrote: I was confused by the rpm number, my mistake. [olpc@xo-1e-88-13 logs]$ rpm -ql webkitgtk3 | grep typelib /usr/lib/girepository-1.0/JSCore-3.0.typelib /usr/lib/girepository-1.0/WebKit-3.0.typelib /usr/lib/girepository-1.0/WebKit2-3.0.typelib Does sugar-build really need to clone and build Webkit2? ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] About web activities, webkit2 and backward compatibility
On 21 May 2013 23:43, Daniel Francis fran...@sugarlabs.org wrote: On Tuesday, May 21, 2013 05:09:38 PM Gonzalo Odiard wrote: I was confused by the rpm number, my mistake. [olpc@xo-1e-88-13 logs]$ rpm -ql webkitgtk3 | grep typelib /usr/lib/girepository-1.0/JSCore-3.0.typelib /usr/lib/girepository-1.0/WebKit-3.0.typelib /usr/lib/girepository-1.0/WebKit2-3.0.typelib Does sugar-build really need to clone and build Webkit2? I think for development we really want the stable 2.0 API. I'd rather not have to worry about API changes. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Getting karma to work with sugar-activity-html
Almost done! We are successfully running the sugar-html-graphics test in buildbot. The only bit left is to redirect the logs so that they don't mix up with the shell ones and buildbot can watch them. I posted a couple of sugar patches that will make that possible https://github.com/sugarlabs/sugar/pull/70 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Clock-13
Activity Homepage: http://activities.sugarlabs.org/addon/4191 Sugar Platform: 0.82 - 0.100 Download Now: http://activities.sugarlabs.org/downloads/file/28584/clock-13.xo Release notes: * Use standard lips icon for speech features (thanks Walter!) * Feature allowing dragging of clock hands to manually explore how an analogue clock works for both direct XO-4 touch interaction and trackpad use (many thanks Manuq!) * Translation updates * Redraw performance updates * AM/PM display on main clock face Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] [Marketing] Sugar 0.100 or 1.0
On 21 May 2013 23:32, Sameer Verma sve...@sfsu.edu wrote: Speaking of activities in the Sugar sense, I was wondering how many of the HTML5 apps from FirefoxOS would slide over to our platform with little change. I just got my hands on a Geeksphone Peak (http://www.geeksphone.com/) and have been following up on how Mozilla does FirefoxOS apps. (As an aside, their apps live on Github, both as code and as zip files, and hosted through https://marketplace.firefox.com/ which looks similar on the phone as it does on a laptop). If some of the FirefoxOS apps can become Sugar HTML5 activities, we may be able to ramp up on the number of activities relatively soon. Wishful thinking, and all that... Well, they won't work out of the box but it might be possible to port some of them if the source code is available. Difficulty depends on how Firefox specific their code is, aside from the usual rendering engine incompatibilities Firefox OS provides system APIs which are not available in Webkit. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] Clock-13
== Source == http://download.sugarlabs.org/sources/honey/Clock/Clock-13.tar.bz2 == Bundle == http://activities.sugarlabs.org/en-US/sugar/downloads/file/28584/clock-13.xo == News == * Use standard lips icon for speech features (thanks Walter!) * Feature allowing dragging of clock hands to manually explore how an analogue clock works for both direct XO-4 touch interaction and trackpad use (many thanks Manuq!) * Translation updates * Redraw performance updates * AM/PM display on main clock face Regards, --Gary P.S. This is intended to make the 13.2.0 OLPC release, and specifically includes features for the XO-4 touch hardware (though the features also work well with older trackpad/mouse only hardware). ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [sugar-build] Is webkitgtk becoming a barrier?
We have sugar-build use packages for certain packages on Fedora 19 that aren't available on Fedora 18 already (ragel, node, npm), so why not just add webkitgtk to the list as well? It makes sense enough to me, provided we're pulling a compatible version. To that end, I've already submitted a pull request. ;-) Manuel Quiñones mailto:ma...@laptop.org May 20, 2013 7:24 AM I was seeing the same :) Yes, would be nice for distro F19 to use the installed webkitgtk. Thanks! -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Daniel Narvaez mailto:dwnarv...@gmail.com May 20, 2013 4:42 AM Btw, I think we are currently triggering a webkitgtk build after every pull, even if nothing is really changed (I blame webkitgtk stupidity for that at least partially :P). I will fix that. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Daniel Narvaez mailto:dwnarv...@gmail.com May 19, 2013 6:41 AM Hey, It seems like building webkitgtk is a bit of a pain for many people. I would like people feedback on how bad of an obstacle it really is and about a couple of possible solutions: 1 Have buildbot generate snapshots of the base system dependencies which most people are unlikely to want to modify anyway and upload those. It would probably be a system.img file which you would put in your sugar-build directory. With that file present, the external sugar dependencies would not be downloaded and built at all. 2 Officially support Fedora 19, disable the webkitgtk build there and suggest people for which building webkigtk is too much to use Fedora19. Thoughts? Would you use 1/2 if it was available? -- Daniel Narvaez ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
