Re: [sugar] [IAEP] list of complaints from sugarcamp community building talk
Edward Cherlin wrote: On Mon, Nov 24, 2008 at 2:15 AM, Simon Schampijer [EMAIL PROTECTED] wrote: Definitely a problem. We are thinking about having a landing page similar to the one in http://www.eclipse.org/ that hopefully will give a way for everybody to find how to better interact with us depending on their role. The idea is that a prospecting developer would just click on one of those icons and would find a simple explanation of the first concepts that need to be grabbed in order to move forward. How does that sound? olpc-dev list emails are kind of over my head Yeah, we should understand better this issue. Is a coder-newbies mailing list a valid suggestion? Hmmm, I think we should not split those up. In my opinion all we can do, is to point out clearly that all contributions and questions as easy or as hard they are, are valid and welcome. We all started there, and I understand it is not always easy to ask 'stupid' questions, but I think it is important to produce a culture and atmosphere where this is possible. A FAQ will help a lot, particularly if somebody takes ownership and makes sure to capture questions and get answers from the experts. A set of introductory programming manuals on Python, PyGame, SciPy, and Etoys will help more. We can discuss this with FLOSS Manuals. Let Adam Hyde and me know which ones you would like to have, and which ones others ask you for. Sure, manuals and FAQ's are always helpful and the page must be structured in a way that people can find it. I hope that the work that is going into the restructuring will make things better. I am working on creating a newsletter for those interested in joining Sugar work. We have two volunteers so far from Olin Coll. of Eng., motivated by the fact that they can't find the news on OLPC (Who can?) and that they have had difficulties finding out how to participate. Articles on elementary Sugar programming and on opportunities for activities will be welcome, as will progress reports whenever you have a significant accomplishment or need help. I sent over my links to laptop news sources, and some references on a multitude of games that people can program if they like. We will collect many other resources. We will also include suggestions for curriculum, textbooks, and content. The idea is that anybody can participate, because everybody knows something that the children need. In particular we need subject-matter experts (SMEs) in every school subject and every kind of business, research, government, or whatever. Also artists, writers, reviewers, testers, localizers, translators, and so on and on. So I argue, to please use sugar-devel for those discussions. +1 unless the Sugar Newbies tell us otherwise. We also have other lists appropriate for content and the rest. Ok, we had this now several times, I propose the following tags for sugar-devel: [RELEASE] when developers of a sucrose component make a release (this is in use already) --- a packager should have all the information he needs when filtering for those messages [ANNOUNCE] announcements like: a new sucrose release, feature freeze, 0.86 feature process, services outage, upcoming trac activities after a release (to move tickets and clean everything), API changes --- an activity developer should have all the information he needs when only filtering for those information [BEET] (comes from sugar-beet) This is a tag that should be used by beginners questions --- To avoid having an extra list, and to produce a culture of critique Anything I have missed? If there are no objections I will take care to add this to the list info, announce it and note it in appropriate places on the wiki. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] list of complaints from sugarcamp community building talk
Carol Farlow Lerche wrote: Please DON'T introduce more sugarisms like BEET, especially for novices. How are they supposed to know what to put as a tag, even if the tag makes sense? They read it when they subscribe to the mailing list - and find it on the wiki pages for example 'Getting involved'. I don't mean to beet someone when he does not use the tag - but I don't want to create another list neither. Cheers, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] list of complaints from sugarcamp community building talk
Luke Faraone wrote: On Tue, Nov 25, 2008 at 08:48, Simon Schampijer [EMAIL PROTECTED] wrote: Carol Farlow Lerche wrote: Please DON'T introduce more sugarisms like BEET, especially for novices. How are they supposed to know what to put as a tag, even if the tag makes sense? They read it when they subscribe to the mailing list - and find it on the wiki pages for example 'Getting involved'. I don't mean to beet someone when he does not use the tag - but I don't want to create another list neither. This still raises the bar for asking a question, which is the opposite of what we are trying to accomplish. -lf I mainly was saying, I don't think another list will solve the issue. If people want to do something like Sugar classes or invite new developers at their home for sugar and tea - this sounds more fruitful to me. Cheers, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] gconf woes
Sayamindu Dasgupta wrote: On Sun, Nov 23, 2008 at 10:44 PM, Daniel Drake [EMAIL PROTECTED] wrote: Hi, As we all know, latest joyride can't launch activities. Chris Ball pointed out that disabling rainbow solves the issue. The problem is that the sugar module imports try to read the XO nickname, colours, etc, information which is now stored in gconf. But, gconf is a per-user thing, everyone has their own store. Rainbow launches activities as different users, so with the default behaviour we cannot expect activities to be able to access sugar's configuration. Potential workaround: set ORBIT_SOCKETDIR=/tmp/orbit-olpc in rainbow, and loosen permissions on /tmp/orbit-olpc/* This works, but causes gconf to complain loudly that /tmp/orbit-olpc is not owned by the current user (i.e. the one running the activity) Tomeu raised the point that GConf2-dbus would solve this, as it provides a per-session-bus settings repository, rather than a per-user one. Rainbow already shares the session bus between olpc user and activities. We actually shipped GConf2-dbus in 8.1, but dropped it for 8.2 because at the time, nobody could offer an explanation of why we might need or want it. Switching back to GConf2-dbus does raise some questions though: - It looks like a dead project. Not updated since 2.16.0. Do we want to be burdened with it? miraculously, it compiles and works fine after a BuildRequires tweak: http://koji.fedoraproject.org/koji/taskinfo?taskID=946380 - This still raises questions about our security model, IMO. Rainbow prevents activities from messing with 'the rest of the system.' But if we let activities access gconf, they can screw up any application that stores information there (e.g. sugar). - and the above point raises the possibility of a per-activity gconf store, with associated gconf daemon, but this adds about 2mb memory usage per activity... IIRC, the reason we wanted Gconf Dbus was that we wanted to avoid the dependency on Orbit and the rest of the stuff that it pulls in. Is there any reason to do otherwise at the moment ? I think upstream GNOMe has also plans to switch to GConf Dbus[1], but I'm not sure when. The maemo guys seem to be using GConf Dbus as well. Thanks, Sayamindu [1] http://projects.gnome.org/gconf/plans.html We use gconf-dbus as well in sugar-jhbuild to be able to run several instances (SUGAR_PROFILE=sayamindu2 sugar-emulator) Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Announcing a design roadmap meeting, tentatively scheduled for Wed. Nov. 26th, 1500 UTC
Eben Eliason wrote: Though it's not part of our usual biweekly cycle, we'd like to hold a meeting this week to lay out a loose roadmap for Sugar in the OLPC 9.1 timeframe, taking into account the discussions from SugarCamp last week. I've posted additional details, including a loose agenda, on the wiki: http://sugarlabs.org/go/DesignTeam/Meetings#Wednesday_November_26.2C_2008_-_15.00_.28UTC.29 In order to have a productive planning discussion, we really need all key sugar developers to participate. If the time or date conflicts, please suggest alternatives. Wednesday does work for me. As i have not been at the SugarCamp I am extremely interested in what you came up with those days. As Thursday is Thanksgiving for many, we'd like to find a time tomorrow or Wed. Thanks! - Eben I hope it is Thanksgiving for us as well, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sucrose 0.83.2 Development Release
This is our second Development Release in the 0.84 cycle [1]. Besides
all the great bug fixing that has been going into this release we want
to highlight some interesting changes.
Some great work has been going into this release regarding the 'View
source' support. The source of all the activities can be shown, and
browse does still support showing the source of the document.
Sugar now supports setting up a priority list of languages. Not all
programs have translations for all languages. You can create a list of
languages in the Control panel that are used to display messages in
place of a non-existent translation.
More work has been going into the sugar support for NM 0.7. We finished
the support for wireless devices in the frame, updated the radio off
code in the control panel to work with NM 0.7 and added WPA support.
Three great activities are now part of fructose, the Image Viewer
activity, Turtleart and Jukebox. They have been included in
sugar-jhbuild. Give them a try!
Thanks to everyone who made this release possible!
In behalf of the sugar community,
Your release team
[1] Sucrose Release Schedule:
http://sugarlabs.org/go/DevelopmentTeam/Release/Roadmap#Schedule
Full Release Notes:
http://sugarlabs.org/go/DevelopmentTeam/Release/Releases/Sucrose/0.83.2
---
== Glucose news ==
=== sugar-toolkit ===
* Fixed misformed plural equation (russian po)
* Add view-source-related methods HandleViewSource and GetDocumentPath
=== sugar ===
* fix uninstalling activities from the home view
* Make sugar control panel support selection of multiple languages d.l.o
* {{Bug|8876}} add saving and loading of the nm connections and support
for WPA
* Implement a global handler for the view source key
* Initial implementation of activity notifications
* d.s.o #9 wireless network frame device.
* {{Bug|8876}} Make sugar control panel support selection of multiple
languages
* d.s.o #7 update Icon in the AP palette
* {{Bug|8131}} Control Panel needs to list wireless firmware version
== Fructose news ==
=== read-activity ===
* Sugar API update: Use self.shared_activity not self._shared_activity
* Updated translation: ja
* Remove timeout hack for object picker
=== browse-activity ===
Return the document source to the shell for displaying in the view
source dialog. This is used by the new source view code to display the
document source.
=== imageviewer-activity ===
* Show an object picker if no file is specified initially
* Initial Journal support
=== turtleart-activity ===
* Turkish and Mongolian language support
* shebang patch
=== jukebox-activity ===
* Encoding error fixed for bn_IN.po
* Full Screen option
* Volume Control support
* Supporting m3u playlists
* Internet radios through m3u files.
* Next/Previous buttons , if you open a playlist with more than one song
== Fructose dependencies news ==
=== hulahop ===
* Remove flags which are breaking the build on latest libtool
* Add AC_PROG_CXX
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
[sugar] Module Turtle Art added to Fructose
Hi Walter, the turtleart activity has been added to fructose. It has been added to sugar-jhbuild and is listed as module under [1]. You can list here peers or add other additional information. For releases please use the descriptions at [2]. Please make sure to be subscribed to [EMAIL PROTECTED] [3] as announcements will be sent to this list. Your release announcements does go to this list as well. Feel free to ask if you have further questions, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Modules#turtleart-activity [2] http://sugarlabs.org/go/DevelopmentTeam/Release#Module_release [3] http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Module Jukebox added to Fructose
Hi Kushal, the Jukebox activity has been added to fructose. It has been added to sugar-jhbuild and is listed as module under [1]. You can list here peers or add other additional information. For releases please use the descriptions at [2]. Please make sure to be subscribed to [EMAIL PROTECTED] [3] as announcements will be sent to this list. Your release announcements does go to this list as well. Feel free to ask if you have further questions, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Modules#jukebox-activity [2] http://sugarlabs.org/go/DevelopmentTeam/Release#Module_release [3] http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Module Image Viewer added to Fructose
Hi Sayamindu, the Image Viewer activity has been added to fructose. It has been added to sugar-jhbuild and is listed as module under [1]. You can list here peers or add other additional information. For releases please use the descriptions at [2]. Please make sure to be subscribed to [EMAIL PROTECTED] [3] as announcements will be sent to this list. Your release announcements does go to this list as well. Feel free to ask if you have further questions, Your Release Team [1] http://sugarlabs.org/go/DevelopmentTeam/Release/Modules#imageviewer-activity [2] http://sugarlabs.org/go/DevelopmentTeam/Release#Module_release [3] http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-Design-Developers meeting REMINDER (Novermber 22, 23 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting]
This week is special again! We want to create a roadmap for the design team. Since this has direct impact on the development team we want to meet on Thursday at 14.00 UTC for the design meeting to create the design roadmap. And on Friday 14.00 UTC we will schedule items for the developers team then. [1] Thursday 27.11.08 14.00 UTC - Design Meeting on irc freenode.net, #sugar-meeting [2] Friday 28.11.08 14.00 UTC - Developers Meeting on irc freenode.net, #sugar-meeting Best, Simon PS: Note that I will stop sending copies to this list soon. We use [EMAIL PROTECTED] now for the meeting reminders and minutes. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-0.83.3
== Source == http://dev.laptop.org/pub/sugar/sources/sugar/sugar-0.83.3.tar.bz2 == News == fix uninstalling activities from the home view Make sugar control panel support selection of multiple languages d.l.o #8876 add saving and loading of the nm connections and support for WPA Implement a global handler for the view source key Initial implementation of activity notifications == Fixed tickets == * d.s.o #9 wireless network frame device. * #8876 Make sugar control panel support selection of multiple languages * d.s.o #7 update Icon in the AP palette * #8131 Control Panel needs to list wireless firmware version == Test cases == #8131 View About my XO in the control panel. Wireless Firmware should be listed below Firmware and should contain a value like 5.110.22.p18 (on the XO). ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Map 2
Erik Blankinship wrote: Please look at the updated Map activity wiki page for a tutorial replete with screenshots. wiki: http://wiki.laptop.org/go/Map_(activity) xo: http://mediamods.com/sugar/Map-2.xo source: http://mediamods.com/sugar/Map-2.tar.bz2 We welcome suggestions. Thanks! As you have noted in the code - this release does not run on sugar-0.84 because the util API changed to be sha_data(data). Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] sugar-devel mailing list
Ivan Krstić wrote: On Nov 17, 2008, at 10:59 PM, David Farning wrote: The Sugar developers have started a upstream list for sugar development issues that are not OLPC specific. If you are interested, please feel free to join. What will [EMAIL PROTECTED] serve? Will we move iaep there? Namely, sugar-devel: http://lists.sugarlabs.org/listinfo/sugar-devel A full feed of Sugar Labs bug mail is now also available: http://lists.sugarlabs.org/listinfo/bugs Thanks very much for making the bug list available! That is very helpful. Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] November 20 - Tarballs due for 0.83.2
Dear maintainers, the next unstable release (head branch) is the 21th November. Please provide source code tarballs by the end of November the 20th and announce them as explained here: http://sugarlabs.org/go/DevelopmentTeam/Release#Module_release The release command has been improved and can be found at: http://gitorious.org/projects/sugar-tools Just run the release script inside your module directory and it should: * Bump version, tag and push to git. (You can use --version if you need more than a simple increment) * Build a source tarball and upload it on dev.laptop.org (you need to have a shell account for that operation) * Generate a release announcement, let you edit it and then send it to the sugar list Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Pippy v30 released
Brian Jordan wrote: Hi, Cscott released Pippy version 30 today, download it [1] or get the source [2]! It's sporting a fancy new physics engine, mildly less violent default export icon, and a smaller editor font. [1] http://dev.laptop.org/~cscott/bundles/Pippy-30.xo [2] http://dev.laptop.org/git?p=projects/pippy-activity;a=summary Hi Brian, since Pippy is part of Sucrose can you upload a source tarball as well? Build a source tarball, test it carefully and make it available in a stable location. The preferred location is http://dev.laptop.org/pub/sugar/sources/ which translates to: dev.laptop.org:/var/www/sugar/sources/ You need a developer account to be able to upload there. http://sugarlabs.org/go/DevelopmentTeam/Release#Module_release Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Fwd: Sugar architecture diagram (was Re: OLPC France CodeCamp in Paris)
Walter Bender wrote: and as a wiki table: http://wiki.sugarlabs.org/go/Sugar_architectual_diagram -walter We created http://sugarlabs.org/go/DevelopmentTeam/Architecture today. Best, Simon On Sat, Nov 15, 2008 at 12:34 PM, Carol Farlow Lerche [EMAIL PROTECTED] wrote: Here is your diagram svg-ified via a nifty firefox addon (pencil). On Sat, Nov 15, 2008 at 3:26 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: Sorry, didn't checked if the sugar lists where on CC. Tomeu -- Forwarded message -- From: Tomeu Vizoso [EMAIL PROTECTED] Date: Sat, Nov 15, 2008 at 11:18 AM Subject: Sugar architecture diagram (was Re: OLPC France CodeCamp in Paris) To: LASKE, Lionel (C2S) [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED], Bastien [EMAIL PROTECTED], [EMAIL PROTECTED] [EMAIL PROTECTED] 2008/11/1 LASKE, Lionel (C2S) [EMAIL PROTECTED]: Hi all, OLPC France is proud to announce its OLPC CodeCamp in Paris on November 15th. Five workshops are planned: · Sugar: development and experimentation on Sugar/python, Hi, perhaps may help this diagram I quickly sketched (see in a fixed-width font): --- | | || | | | Non-python | Sugar shell | Python| | | Sugar | (Desktop window, |Sugar| | | Activities | panel,| Activities | | Regular| (Etoys,| journal) | | | X | Simcity, || | | Apps |Mono |--| | | activities, |Sugar toolkit (python-only) | | |etc.)| | | || | |DataStore | Presence | | | service | service| --- |Matchbox window manager| | (considering switching to Metacity for improved compatibility) | --- | | |GNOME-ish Linux desktop| |X11, HAL, D-Bus, NetworkManager, GConf, Telepathy, etc | | | --- Regards, Tomeu · School Server: setting up and test of school server on multiple platform (standard PC, Booba server, CherryPal, …), · Mono: development of new activities using Mono, · Pedagogic usage: Feedbacks from Haïti, Ethiopia and Palestine deployment. Brainstorming with French teachers to find usage and class activity for the XO. · French localization: French translators will work all the days to translate in French, sugar, activities and FLOSS manual. If you're interested to meet the French OLPC community and to have a nice trip to Paris: you're welcome ! More information on: http://olpc-france.org/wiki/index.php?title=OLPC_France_CodeCamp_15_november Best regards from France. Lionel Laské ___ Devel mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/devel ___ IAEP -- It's An Education Project (not a laptop project!) [EMAIL PROTECTED] http://lists.sugarlabs.org/listinfo/iaep -- Don't think for a minute that power concedes. We have to work like our future depends on it. -- Barack Obama ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] SugarCamp
Marco Pesenti Gritti wrote: On Thu, Nov 13, 2008 at 2:22 PM, Tomeu Vizoso [EMAIL PROTECTED] wrote: So, talks that IMO are more appropriate for this week, along with people I'm most interested in hearing, are: - How Sugar-on-a-stick can better work for deployments such as the ones carried on by http://schoolkey.net (Caroline Meeks) - How Sugar can better work in a LTSP environment (Brendan Powers) - How SugarLabs can better work together with teachers (Yamandú Ploskonka) - How SugarLabs should communicate its message (Greg DeKoenigsberg) - How SugarLabs can make easier to contribute to it (Mel Chua) - How SugarLabs could partner with for-profits that work on related projects (Collabora on GNOME's telepathy, Nokia on PyMaemo, etc) (Robert McQueen) - How SugarLabs is going to maintain the infrastructure needed to support its own operations (Bernie Innocenti) - How SugarLabs is going to fund its own operations (Walter Bender) - How SugarLabs is going to govern itself (Walter Bender, David Farning?) - How SugarLabs is partnering with other organizations (David Farning) +1, all of these sounds like excellent ideas! I would also like them to be structured more like discussion/brainstorming than talks. But we definitely need someone to lead them and the owners your proposed sounds very good. (Not sure if Robert McQueen will be there though). I'd like to propose another one: - How Sugar Labs could better work with OLPC in satisfying their customers. (Greg Smith) Marco Yes make sense to me as well. I like the nature of a workshop more than talks. And the Topics do clearly call for that. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] SugarCamp
Tomeu Vizoso wrote: Fellow Sugarites, I must say that I'm pretty much surprised as to how the SugarCamp planning is being done. My personal opinion is that SugarLabs is a global organization and cannot behave as if it had headquarters in a single place because it hasn't. SL contributors are going to travel from quite distant places and they should be involved actively in the planning. I think it is very important that planning happens with all parties involved. OLPC has decided that their XOCamp will happen in January, and I think that our SugarCamp in November shouldn't be seen as just a prelude to that. OLPC employees can legitimately see SL as a vehicle for their product to include more features, so they would be mostly interested in technical discussions about those. But I expect the people who share the SL goals to be more ambitious and to not forget that Sugar cannot stay contained at OLPC's borders. We have the mission to bring Sugar to _all_ the kids in the world. Yes, we want to open sugar to a broader community. Those goals should be reflected in the agenda of a SugarCamp - that at least is how I understand it. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Jukebox v3 released
Kushal Das wrote: On Wed, Oct 29, 2008 at 5:26 PM, Simon Schampijer [EMAIL PROTECTED] wrote: some notes on the sources: can you make those 644: Jukebox.activity/activity/activity.info Jukebox.activity/NEWS Jukebox.activity/jukeboxactivity.py and add a license field in activity.info http://wiki.laptop.org/go/Activity_bundles#.info_File_Format There is no jukebox component in the d.l.o tracker - as I understand you are the new maintainer - shall I add one? Sorry for the late reply , I made a new release after fixing the issues. Please add me as the new maintainer , my trac username: kushal Kushal Thanks for the fixes - I added the new component and you as maintainer. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday Novermber 13 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
Hello, we want to get some items together for the Sugar Workshop on Saturday the 15th Nov in Paris [1]. Collect a set of bugs that people can fix or other item they can work on during that day. And we should collect some material that Daniel can use to make an introduction (if he has not done so yet). Have a nice evening, Simon [1] http://olpc-france.org/wiki/index.php?title=Sugar_Workshop_15nov ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] sugar 0.83 in joyride
Tomeu Vizoso wrote: On Wed, Nov 5, 2008 at 10:31 AM, Tomeu Vizoso [EMAIL PROTECTED] wrote: Dear Masters of Joyride, have built updated sugar rpms and they seem to work fine on last joyrides. Marco pointed me out in #sugar that work fine may need some clarification. In fact, the following things are known to be broken currently: - no WAP support (simon is working on this) - no mesh support (sjoerd has done work on this) - rainbow is broken because depends on the old config file being present http://dev.laptop.org/ticket/8850 is the rainbow patch - Michael can you review and release a new rainbow when appropriate? Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday Novermber 6 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
With Milk? No, thanks I take some sugar only. The first part of our coffeetablish meeting will be to update everyone about the current efforts. A lot of progress has been made on the icon cache for example. The second part will be to discuss the activity maintainers situation. We really need to advance on that! See you tomorrow, and don't forget to be bring some sweets, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Sucrose 0.83.1 Development Release
Tomeu Vizoso wrote: On Fri, Oct 31, 2008 at 9:30 PM, S Page [EMAIL PROTECTED] wrote: Simon Schampijer wrote: This is our first Development Release in the 0.84 cycle. The code base has seen many refactoring efforts to improve the platform. Will OLPC joyride builds pick up the new Sucrose? Sure. Hopefully soon. Furthermore the datastore has been rewritten, to simplify and improve maintainability. The API has been kept in place. What happens when you upgrade an XO with the old datastore? The old datastore will be updated to the new format. What happens if you then downgrade it? You lose. Sugar moved to use Gconf as a back end to store the profile. When you upgrade an XO, does it import your old profile (~olpc/.sugar/default/config)? Yup. What happens if you then downgrade? You will be prompted to enter again a name, choose a color, etc. Right when we upgrade the old profile is ported to gconf and the .sugar/default/config file is erased - so when we downgrade we check for the presence of that file and will create the config like we do on first boot. An ABI policy has been figured out and modules have been marked as STABLE / UNSTABLE / DEPRECATED. Where are they marked, in the .py files? Yes, in the docstrings so it should make it to places like http://api.sugarlabs.org == Fructose news == ... Are the new activity versions backwards-compatible with 8.2? If so, the maze of Activity lists should be updated. Most of them yes, a notable exception is Browse because depends on xulrunner and hulahop. Read has the same issue, but evince hasn't been updated (yet) so for now it should work. Currently http://wiki.laptop.org/go/Activities/Joyride pulls in Activities/G1G1 , as does Activities/G1G1/8.2, and that list still references old versions -- Browse 98 not 100, Read 52 not 60, etc. -- even though the links say Browse (latest). Who could take care of this? Activities/G1G1/8.2 is right to pull in Browse 98 - since the latest browse is dependent on the latest hulahop. The others should be updated I guess. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-artwork-0.83.1
== Source == http://dev.laptop.org/pub/sugar/sources/sugar-artwork/sugar-artwork-0.83.1.tar.bz2 == News == * Ensure that all common drag operations use a sugar cursor * Generate two themes based on SUGAR_SCALING * #8779 Merge sugar-artwork patches from debian package. * #8778 Buttons cannot be prelit. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sucrose 0.83.1 Development Release
This is our first Development Release in the 0.84 cycle. The code base has seen many refactoring efforts to improve the platform. To improve performance several heavy shell dependency have been dropped and the journal and the shell service has been merged into the shell. Furthermore the datastore has been rewritten, to simplify and improve maintainability. The API has been kept in place. Sugar moved to use Gconf as a back end to store the profile. An ABI policy has been figured out and modules have been marked as STABLE / UNSTABLE / DEPRECATED. Some enhancements have been made to the clipboard to provide visual consistency with the Sugar environment. And of course many many bugs have been fixed, which you can see in detail below. Thanks to everyone who made this release possible! In behalf of the sugar community, Your release team Full Release Notes: http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.83.1 Sucrose Release Schedule: http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Schedule == Glucose news == === sugar-toolkit === * Mark modules as STABLE/UNSTABLE/DEPRECATED * #8420 Failure to handle 404 in ChunkedGlibHTTPRequestHandler * #7649 Activities needs to access sugar-toolbox's members directly * #8617 Clipboard scroll buttons icons point left/right, should point up/down * #8604 Tray control should support highlight on drag * #8840 Can't join shared activity * #8674 8.2-764, Software Update erased complete /home/olpc/Activities directory * #8626 Icons overlap unnecessarily in crowded neighborhood view. * #8563 Sugar Palette doesn't handle 'table menus'. * #8532 SIGCHLD fights with threads. * #8485 Shell navigation leaks * #8375 gst usage in the shell wastes 2.6mb * #8394 sugar shell leaks presence service info * #8469 palette.menu is leaked * #8394 sugar shell leaks presence service info * #8392 Remove dynamic font height computation * #5428 downloads not starting in Browse due to old compreg.dat * #7999 7+% of shell startup time is spent in `grab' of sugar._sugarext.KeyGrabber * #8000 Pulsing icon on activity launch significantly slows activity start-up * #7270 setup release does not update the bundle number * #7959 gettext translations slows journal's scrolling * #7733 Cannot install Wikipedia-10.xo * #7533 Activity does not respond to ctrl-q keyboard shortcut unless the 'Activity' tab is visible === sugar === * Modularized the shell to have every major UI component like the frame the home view and the control panel reside in his own module and be self contained * Use gconf as a backend to store the profile. * Several heavy shell dependency have been dropped. * Merge of the journal and of the shell service into the shell * #5867 Battery fully charged shows up in error (battery is removed) * #8623 Jabber server description is ambiguous * #8900 Should re-request closed random views * #7545 Should request random activities/buddies to populate the mesh view * #5751 Clipboard objects need meaningful labels. * #8606 Dragging within the clipboard creates duplicate clippings * #7408 Cursor lock while dragging icons in Home (or anywhere) * #8604 Tray control should support highlight on drag === sugar-artwork === * Ensure that all common drag operations use a sugar cursor * Generate two themes based on SUGAR_SCALING * #8779 Merge sugar-artwork patches from debian package. * #8778 allow prelightning of buttons === sugar-base === * Add dispatcher implementation from django * Mark modules as STABLE === sugar-datastore === * The datastore has been rewritten, to simplify and improve maintainability. As a first step the API was not changed at all (other than removing removable devices support), so that the new implementation was swapped in without changes to activities and Sugar * Drop for now the management of removable devices inside the DS. Removable devices support in Sugar should happen without intervention from the DS * #8155 The datastore should hard link identical files, to handle repeated downloads of the same content without filling up NAND * Support arbitrary metadata properties that activities wish to add #4662 * Degrade gracefully if a database gets corrupted- Basic functionality should only depend on the filesystem being available. Any other data structures (full text index) should be rebuildable from the filesystem #6269 === sugar-presence-service === * #7581: Don't ignore buddies without keys. This improve interoperability with non Sugar clients. * #7849: Display PS version in the log. * Use gconf to get Sugar profile settings. * #8444: Don't rely on the roster to check if a contact handle is channel specific or not - so PS will properly create Buddy objects discovered using Gadget. Furthermore, this workaround has the nice side effect to improve compatibility with bugged shared roster (as the one of ejabberd). * #5618: Discard invalid handles if InspectHandles failed. === etoys === This
[sugar] [RELEASE] sugar-base 0.83.1
sources: http://dev.laptop.org/pub/sugar/sources/sugar-base/sugar-base-0.83.1.tar.bz2 News: * Add dispatcher implementation from django * Mark modules as STABLE Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-toolkit 0.83.1
== Source == http://dev.laptop.org/pub/sugar/sources/sugar-toolkit/sugar-toolkit-0.83.1.tar.bz2 == Fixed tickets == * #8420 Failure to handle 404 in ChunkedGlibHTTPRequestHandler * #7649 Activities needs to access sugar-toolbox's members directly * #8617 Clipboard scroll buttons icons point left/right, should point up/down * #8604 Tray control should support highlight on drag * #8840 Can't join shared activity * #8674 8.2-764, Software Update erased complete /home/olpc/Activities directory * #8626 Icons overlap unnecessarily in crowded neighborhood view. * #8563 Sugar Palette doesn't handle 'table menus'. * #8532 SIGCHLD fights with threads. * #8485 Shell navigation leaks * #8375 gst usage in the shell wastes 2.6mb * #8394 sugar shell leaks presence service info * #8469 palette.menu is leaked * #8394 sugar shell leaks presence service info * #8392 Remove dynamic font height computation * #5428 downloads not starting in Browse due to old compreg.dat * #7999 7+% of shell startup time is spent in `grab' of sugar._sugarext.KeyGrabber * #8000 Pulsing icon on activity launch significantly slows activity start-up * #7270 /setup release does not update the bundle number * #8000 Pulsing icon on activity launch significantly slows activity start-up * #7959 gettext translations slows journal's scrolling * #7733 Cannot install Wikipedia-10.xo * #7533 Activity does not respond to ctrl-q keyboard shortcut unless the 'Activity' tab is visible Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar 0.83.1
== Source == http://dev.laptop.org/pub/sugar/sources/sugar/sugar-0.83.1.tar.bz2 == Fixed tickets == * #5867 Battery fully charged shows up in error (battery is removed) * #8623 Jabber server description is ambiguous * #8900 Should re-request closed random views * #7545 Should request random activities/buddies to populate the mesh view * #5751 Clipboard objects need meaningful labels. * #8606 Dragging within the clipboard creates duplicate clippings * #7408 Cursor lock while dragging icons in Home (or anywhere) * #8604 Tray control should support highlight on drag Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] October 29 - Tarballs due for 0.83.1
Marco Pesenti Gritti wrote: Dear maintainers, the next stable release is the 30th October. Please provide source code tarballs by the end of tomorrow and announce them as explained here: http://wiki.sugarlabs.org/go/ReleaseTeam#Module_release If you are fearless and want to try the automatic release script see my mail about it: http://lists.laptop.org/pipermail/sugar/2008-October/009524.html Note, that the ./setup.py release has been removed from bundlebuilder - so you need to use marco's release script. It is not required to provide a NEWS file anymore. Feel free to keep a NEWS file if you like, but please drop it from git if you are not keeping it up to date. Some general notes about sources (this is for example important when packaging the activities for Fedora): - get the permissions right (e.g. these should be non executable - 644) sugar-jukebox.noarch: E: script-without-shebang /usr/share/sugar/activities/Jukebox.activity/NEWS sugar-jukebox.noarch: E: script-without-shebang /usr/share/sugar/activities/Jukebox.activity/jukeboxactivity.py - provide a license file (COPYING file) - make sure to have a license field in activity.info http://wiki.laptop.org/go/Activity_bundles#.info_File_Format - remove unnecessary files (e.g. empty AUTHORS files etc) Feel free to add things here that i might have forgot. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Jukebox v3 released
Kushal Das wrote: Hi all, I just released Jukebox activity v3. This is an activity for playing audio/video. You can download the .xo file from [1], the source is available at [2]. New feature added in this release in: * pls playlist file support Since .pls files are supported, some radio stations (such as schizoid.in) are playable with the XO provided that you have the right Gstreamer plugins Feedbacks are mostly welcome :) [1] http://wiki.laptop.org/images/0/09/Jukebox-3.xo [2] http://kushaldas.in/tmp/Jukebox-3.tar.bz2 Kushal Hi Kushal, some notes on the sources: can you make those 644: Jukebox.activity/activity/activity.info Jukebox.activity/NEWS Jukebox.activity/jukeboxactivity.py and add a license field in activity.info http://wiki.laptop.org/go/Activity_bundles#.info_File_Format There is no jukebox component in the d.l.o tracker - as I understand you are the new maintainer - shall I add one? Best, Simon Btw: Jukebox is already in the process of being packaged for Fedora https://bugzilla.redhat.com/show_bug.cgi?id=468539 :) ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Module Proposal: Jukebox activity
Kushal Das wrote: Hello, I would like to propose the inclusion of the Jukebox Activity into Fructose: * Short description of the features: Media player with the following features * plays both video and audio * m3u and pls playlist file support * volume control * Fullscreen display * Screenshots or screencasts. http://www.flickr.com/photos/kushaldas/sets/72157607691417450/ * Are you willing to follow the project schedule? Yes * Are you willing to provide regular source releases? Yes * System components the activity depends on. Gstreamer * Maintainer and members of the developer team, with links to a User page on the wiki or their homepage on the web. Kushal Das: http://kushaldas.in * Status of internationalization Internationalized, not in Pootle yet * Code repository. http://dev.laptop.org/git?p=projects/jukebox-activity;a=summary * Bug tracking system. dev.laptop.org * Homepage. http://wiki.laptop.org/go/Jukebox Kushal Thanks for taking on that task of maintaining that activity. Unless someone objects I'll add it to the list of modules. If you give me your trac name I will add the jukebox component to trac and make you the owner of it. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] hulahop 0.4.7
sources: http://dev.laptop.org/pub/sugar/sources/hulahop/hulahop-0.4.7.tar.bz2 Provide the ground to make downloads and uploads work for multiple instances (marco). Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Browse 100
Dear Browse, happy birthday! Marco and Tomeu honored you and provided excellent new features and fixed a very hard one - the download/upload alert issue for multiple instances! Wish you 100 more, Simon sources: http://dev.laptop.org/pub/sugar/sources/web-activity/Browse-100.tar.bz2 ---NEWS--- * Add a Download image option to the image palette (tomeu) * Add a Download link option to the link palette (tomeu) * Get downloads and upload alerts for multiple windows to work (marco) * Handle download names with non-ascii characters #8857 (tomeu) Note: Browse-100 is dependent on the latest hulahop v0.4.7 ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] October 29 - Tarballs due for 0.83.1
Marco Pesenti Gritti wrote: Dear maintainers, the next stable release is the 30th October. Just for the record - it is an unstable release :) Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] October 29 - Tarballs due for 0.83.1
Bert Freudenberg wrote: On 28.10.2008, at 04:01, Simon Schampijer wrote: Marco Pesenti Gritti wrote: Dear maintainers, the next stable release is the 30th October. Just for the record - it is an unstable release :) Is this basically what's in jhbuild right now? - Bert - Yes - the master branches. Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday October 16 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
Hello, this meeting we will do another iteration on the Roadmap and will discuss API policy (http://lists.laptop.org/pipermail/sugar/2008-October/009199.html) and changes. See you there, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] API policy
Marco Pesenti Gritti wrote: Hello, for 0.84 we are planning to refactor and start stabilizing our public API. Given the high pressure to ship and the very early involvement of activity authors, our API quality is currently not as good as we would like it and is going to require substantial changes. An important part of the work is to figure out which guarantees we have and are able to provide at the moment and which policy we should adopt for the future. The following is an initial proposal, I would like to discuss it on the mailing list and in the next developer meetings. The proposal applies to the following areas: * Glucose dbus services: datastore and presence service. * Sugar public python package (provided by sugar-base and sugar-toolkit). * Window management protocols. Each interface, being a python module, a service or a protocol can be in one of the following states. The state should be always explicitly documented. UNSTABLE Changes are possible at any time, except after the feature freeze of each release cycle, but they should be well documented. It should be used for API which requirements are not yet well enough to be able to settle on a stable interface. As Sugar mature we should aim to have as little as possible components in this state. STABLE No *incompatible* change is possible. The API should be well documented and a set of unit tests should prevent breakage. To be able to remove a stable interface it will have to first be deprecated. DEPRECATED Interfaces which are not useful anymore or are being replaced by better, incompatible ones should be deprecated and removed in the next *major* version. When deprecating an interface a replacement should be available and the migration to it well documented. --- Now, how to apply this in practice, starting with 0.84. We should consider 0.82 as our first major release from an API point of view. The next one will be 1.0. I'm unhappy about this, but the reality is that Sugar has been deployed to a large user base already and there are lots of activities written for it. So we are forced to consider the part of our API which is useful to activities as stable. So for example if I land a more powerful graphics/alert in 0.84 the old one would be deprecated at that moment and I would be able to remove the deprecated one completely by 1.0, correct? I like your proposal, I think once we categorized it and documented it we made a huge step forward. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] (very) Little Proposals for 9.1
Carlo Falciola wrote: - Messaggio originale - Da: Simon Schampijer [EMAIL PROTECTED] A: [EMAIL PROTECTED] Cc: sugar@lists.laptop.org; Carlo Falciola [EMAIL PROTECTED] Inviato: Lunedì 13 ottobre 2008, 15:26:18 Oggetto: Re: [sugar] (very) Little Proposals for 9.1 [EMAIL PROTECTED] wrote: simon wrote: Carlo Falciola wrote: Giovanna: Why not to enable shut-down from the XO icon of any of the standard view? The icon is always there in the middle of screen but works only in one... (in general, maybe enabling the hoovering menu in all of the views Home, Neighborhood, Group could make sense and could be reasonably easy to do) The idea was that you do not need to shut down, rather suspend the machine :) The palette in the mesh and group view could be used for i realize simon was smiling as he said this, and that giovanna's need is a relatively small one, but this exchange, along with many conversations surrounding the importance of fast boot time, are a perfect example of something Elana Langer said just yesterday: You cannot tell people how to use their computers or what to expect from them. ... All we can do is offer a tool (computer) and help folks think about integrating it into their communities and curriculums but you CANNOT change expectations by simply not meeting them. the fact is that we don't (and may never) consume so little power that the laptop can be used heavily on a daily basis, in a place where power is scarce, and not need to be shut down. simply repeating suspend will take care of that eventually won't solve our users needs today. (again, not picking on simon. elana's observation just happened to strike a chord for me yesterday, and this note gave me an excuse to reiterate it.) paul =- paul fox, [EMAIL PROTECTED] I like the comment from marco, that we should be consistent. So maybe the shutdown option should be added to all the views, Eben what do you think? In any case as sugar runs on other hardware than the XO, we need to have the shutdown option (or at least make it optionally available like the log out one). But as you said I think we are far from consuming that little power to never need to shut down, so we should leave the button where it is. Best, Simon Yes, that was exactly the point from Giovanna I tried to expose... She know she had to shut down the XO, because of battery charge. So I told her of hoovering the mouse and wait for shutdown to appear.. Off Topic: Just in case you did not know. You can reveal all the palettes as well by right-clicking on the icon. There is an extra delay for the hovering to not invoke unintentional revealing. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] (very) Little Proposals for 9.1
Carlo Falciola wrote:
Hi,
during past week-end I spent a few hours playing with the 676 -Candidate ,
mainly in order to check translated strings here an there.
Then let my very personal user base (My children: Nicola, 7 and Giovanna, 6)
to play a bit with the updated XO.
After these user sessions we have a very personal wish list and small
inputs for the next software iteration that we would like to share:
Carlo : nowhere in the default GUI there is a clock, even if, in the control
panel there is a panel to configure it. I think that personal watches are
maybe not so easily owned by kids around the word, so a standard clock could
be a little, but welcomed feature. (not talking about the clock activity that
it is more a learn to read a clock thing than an everyday tool). any
feedback and suggestion regarding how and where to put/show it are welcomed.
There were long discussions already whether a clock is useful or not.
Not sure there was a conclusion. Personally I would not mind having one
in the frame devices as long as I can set the fuzziness (e.g. middle of
week) :)
Giovanna: Why not to enable shut-down from the XO icon of any of the standard
view? The icon is always there in the middle of screen but works only in
one... (in general, maybe enabling the hoovering menu in all of the views
Home, Neighborhood, Group could make sense and could be reasonably easy to
do)
The idea was that you do not need to shut down, rather suspend the
machine :) The palette in the mesh and group view could be used for
something else as well.
Nicola: Should be nice to have a bit more feedback regarding already running
activity into the home view, since now he has a more immediate approach to
the system and he is not, as now, yet really interested to the past story of
his interaction to the system, so he do not care ('till now) so much of the
journal and frame.
For his approach a visual hints of running activities (let's say the activity
icon in the circle to became colored and switch default click acton to be
resume ), maybe could be more useful for his basic approach
Eben had some ideas about that. Eben, what was the last outcome on this?
Thanks for the feedback,
Simon
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
Re: [sugar] convert_profile crashes on ubuntu
Tomeu Vizoso wrote:
Hi, I suspect this issue is related to sugar-jhbuild running on Ubuntu:
Traceback (most recent call last):
File /home/tomeu/sugar-jhbuild/install/bin/sugar-session, line 95,
in module
main()
File /home/tomeu/sugar-jhbuild/install/bin/sugar-session, line 62, in main
intro.check_profile()
File
/home/tomeu/sugar-jhbuild/install/lib/python2.5/site-packages/jarabe/intro/__init__.py,
line 16, in check_profile
profile.convert_profile()
File
/home/tomeu/sugar-jhbuild/install/lib/python2.5/site-packages/sugar/profile.py,
line 157, in convert_profile
volume = int(cp.get('Sound', 'Volume'))
ValueError: invalid literal for int() with base 10: '81.0'
Regards,
Tomeu
Thanks for the report. Fixed in master. I simply had a profile laying
around where the volume was int already from playing with the profile
code :/ So no food for the ubuntu/fedora discussion :)
Best,
Simon
___
Sugar mailing list
Sugar@lists.laptop.org
http://lists.laptop.org/listinfo/sugar
Re: [sugar] Journal Object Picker in Read
Bert Freudenberg wrote: Am 08.10.2008 um 10:33 schrieb Morgan Collett: I filed #8350 regarding adding the journal object picker to Read, for the case when it is launched from Home View without a document. There was a recent discussion on the library list about this, since the show_launcher setting isn't relevant any more - Read appears in Home View if you star it. (If Read is installed in the software updater, it will be starred...) I have implemented this, and could release it for 8.2.1, but the journal object picker doesn't currently have any filters for an Activity to restrict the view to only relevant entries - so it pops up with the entire journal visible - images, Write entries, Browse entries, etc where all we can handle in Read are relevant downloaded documents, and previous Read instances. Is this going to cause more problems than it's worth? I could make the object picker pop up again if the selected entry failed to load, if that helps. An alternative to using the object picker is to have a string break and add a dialog that explains that you launched Read without a document, and so it isn't useful, and make that stop Read when acknowledged. Why not extend the object chooser to include a query parameter? We discussed this a long time ago and it makes sense, it just has not bubbled to the top of the to-do list yet ... - Bert - http://sugarlabs.org/go/DevelopmentTeam/0.84/Ideas It is reflected here. Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday October 9 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
===Topics=== Roadmap * update and discuss the existing concrete items (i.e. icon cache) See you there, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] New modules/activities proposal
Marco Pesenti Gritti wrote: Hello! there is time until October 29 to propose new modules, and new activities in particular, to be part of the 0.84 release. If you are an activity maintainer and would like to propose its inclusion please send mail to this list, providing the following informations. There a bunch of interesting activities which are being developed and I hope to see many of them included in the coordinated release. As proved by the 0.82 cycle coordination is very useful for development, translation and distribution. You can see what will be your duties from here: http://sugarlabs.org/go/ReleaseTeam#Module_release In retrospect to the 0.82 cycle I want to stress out those two points marco mentioned. * Are you willing to follow the project schedule? * Are you willing to provide regular source releases? It is the duty of the maintainer to release the activity. It does not take long to do so, and we are working on making it even simpler in the future. As a maintainer you should not only release when there were changes to the code, you should do so as well when there were translation updates. Translations are hard work, and you should help the translators to get them in. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEAESE] browse-99
sources: http://dev.laptop.org/pub/sugar/sources/web-activity/Browse-99.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82.1/Browse-99.xo - translation update - Remove x permissions from activity.info (needed for fedora packaging) Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Which pygame version is Sugar currently used?
Christoph Derndorfer wrote: Hey all, someone at university here is currently planning an activity and asked me which pygame version Sugar is currently using. Neither he nor I couldn't really find any information on it on [[Pygame]] or [[Software components]] or the more recent archives... Any pointers and help are appreciated. Thanks, Christoph Hey Christoph, http://dev.laptop.org/~bert/8.2/767 says pygame.i386 0:1.8.0-1.olpc3.3 On the XO you can get the version with 'rpm -q pygame' HTH, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Status of tamtam
Philippe Clérié wrote: I am trying to figure what the status of tamtam is outside of OLPC. It's nowhere in Debian or Fedora or Ubuntu that I can find. Anyone has any info? Philippe Hi Philippe, there is the idea of packaging tamtam for fedora but we need someone to do it :) https://fedoraproject.org/wiki/PackageMaintainers/WishList#Activities They use their own alsa client - so this is something that maybe needs to be figured out when packaging. http://dev.laptop.org/git?p=projects/tamtam;a=blob;f=common/Util/Clooper/aclient.cpp;h=213d72e2eb6a0170d9778aed3190a0072c01c07c;hb=651d916538ad274d0541721b70fa729ce9f5088f Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [PATCH] sugar gconf schema
Marco Pesenti Gritti wrote: On Fri, Oct 3, 2008 at 6:29 PM, Simon Schampijer [EMAIL PROTECTED] wrote: Hi, please find attached the sugar gonf schema and give feedbakc about the genera layout. I guess the power one can be made customizable since it is OLPC specific. Some thoughts: key/schemas/desktop/sugar/backup/url/key applyto/desktop/sugar/user/nick/applyto There is a mismatch there... Do we really need a backup category? What else are you thinking will go in there? Yeah, not sure what else would go there. So /desktop/sugar/backup_url I guess for now. key/schemas/desktop/sugar/favorites/layout/key applyto/desktop/sugar/favorites/layout/applyto I would use /desktop/sugar/desktop/favorites_layout (the double desktop is a bit strange but...). That way we can fit all the desktop preferences inside this category. Ok. key/schemas/desktop/sugar/jabber/server/key What about making the category collaboration and the property jabber_server. Yup, done. Marco Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [PATCH] sugar gconf schema
Hi, please find attached the sugar gonf schema and give feedbakc about the genera layout. I guess the power one can be made customizable since it is OLPC specific. Thanks, Simon ?xml version=1.0? gconfschemafile schemalist schema key/schemas/desktop/sugar/user/nick/key applyto/desktop/sugar/user/nick/applyto ownersugar/owner typestring/type default/default locale name=C shortUser Name/short longUser name that is used throughout the desktop./long /locale /schema schema key/schemas/desktop/sugar/user/color/key applyto/desktop/sugar/user/color/applyto ownersugar/owner typestring/type default/default locale name=C shortUser Color/short longColor for the XO icon that is used throughout the desktop. The string is composed of the stroke color and fill color, format is that of rbg colors. Example: #AC32FF,#9A5200 /long /locale /schema schema key/schemas/desktop/sugar/sound/volume/key applyto/desktop/sugar/sound/volume/applyto ownersugar/owner typeint/type default50/default locale name=C shortVolume Level/short longVolume level for the sound device./long /locale /schema schema key/schemas/desktop/sugar/sound/mute/key applyto/desktop/sugar/sound/mute/applyto ownersugar/owner typebool/type defaultfalse/default locale name=C shortSound Muted/short longSetting for muting the sound device./long /locale /schema schema key/schemas/desktop/sugar/backup/url/key applyto/desktop/sugar/user/nick/applyto ownersugar/owner typestring/type default/default locale name=C shortBackup URL/short longUrl where the backup is saved to./long /locale /schema schema key/schemas/desktop/sugar/date/timezone/key applyto/desktop/sugar/date/timezone/applyto ownersugar/owner typestring/type defaultUTC/default locale name=C shortTimezone/short longTimezone setting for the system./long /locale /schema schema key/schemas/desktop/sugar/favorites/layout/key applyto/desktop/sugar/favorites/layout/applyto ownersugar/owner typestring/type defaultring-layout/default locale name=C shortFavorites Layout/short longLayout of the favorites view./long /locale /schema schema key/schemas/desktop/sugar/frame/edge_delay/key applyto/desktop/sugar/frame/edge_delay/applyto ownersugar/owner typefloat/type default1000.0/default locale name=C shortEdge Delay/short longDelay for the activation of the frame using the edges./long /locale /schema schema key/schemas/desktop/sugar/frame/corner_delay/key applyto/desktop/sugar/frame/corner_delay/applyto ownersugar/owner typefloat/type default0.0/default locale name=C shortCorner Delay/short longDelay for the activation of the frame using the corners./long /locale /schema schema key/schemas/desktop/sugar/jabber/server/key applyto/desktop/sugar/jabber/server/applyto ownersugar/owner typestring/type default/default locale name=C shortJabber Server/short longUrl of the jabber server to use./long /locale /schema schema key/schemas/desktop/sugar/jabber/registered/key applyto/desktop/sugar/jabber/registered/applyto ownersugar/owner typebool/type defaultfalse/default locale name=C shortJabber Registered/short longFlag to keep track of the registration status with the jabber server./long /locale /schema schema key/schemas/desktop/sugar/power/automatic/key applyto/desktop/sugar/power/automatic/applyto ownersugar/owner typebool/type defaultfalse/default locale name=C shortPower Automatic/short longPower Automatic./long /locale /schema schema key/schemas/desktop/sugar/power/extreme/key applyto/desktop/sugar/power/extreme/applyto ownersugar/owner typebool/type defaultfalse/default locale name=C shortPower Extreme/short longPower Extreme. /long /locale /schema /schemalist /gconfschemafile ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting CANCELED (Thursday October 2 2008 - 14.00 (UTC))
Hello, we skip this week - you might want to join in for eben's wonderful design meeting at 15.30 UTC though. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] evince/poppler
Simon Schampijer wrote: Hi, we are using an old version of evince and poppler. Are there any intentions to update? Current poppler we use is 0.6 and the latest stable is 0.8 http://poppler.freedesktop.org/ And in jhbuild we use a custom evince branch http://dev.laptop.org/git?p=users/rwh/evince;a=summary Thanks for clearing up, Simon Hah, found the answer :) http://dev.laptop.org/ticket/7926 Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Breaking API (Fwd: Minutes of the GTK+ Team Meeting - 2008-09-23)
Hmmm, this is a really tough subject. I guess that we have to guarantee some kind of backwards compatibility unless we are totally convinced that we fix something broken. I think we have to discuss concrete cases, with the thoughts below in mind, and see what we change and what we should not. Best, Simon Marco Pesenti Gritti wrote: I found this interesting while we are thinking about our API policy. Obviously Sugar is way less mature then gtk 1.2 but still we have a bunch of activities using it. Marco -- Forwarded message -- From: Havoc Pennington [EMAIL PROTECTED] Date: Sat, Sep 27, 2008 at 5:31 AM Subject: Re: Minutes of the GTK+ Team Meeting - 2008-09-23 To: Gtk+ Developers [EMAIL PROTECTED] Even though the update to each line may be trivial, I would say that if a deprecation touches a lot of lines in every app, it really has to meet a high bar for worthwhile-ness, or we're just wasting a whole lot of people's time. Deprecation should not be about aesthetics, or second-guessing the kind of judgment calls where maybe one way to do it is 5% better, but honestly it doesn't matter that much. Deprecation should be about fixing things that were previously impossible, or things that were outrageously inconvenient, or things that are unfixably broken. It should be enabling 100% better not 5% better. A goal with 1.2 - 2.0 was that many apps would recompile without changes, and many did. Even with that goal, porting 1.2-2.0 was a huge effort and made a lot of people unhappy. Do not underestimate how much work app developers can easily end up with once a couple years of small deprecations all add up. Programmers don't like busywork. On the specific issue of GtkBox: just leave vbox and hbox in there. They are hardly any code; they are not hurting anything; and why would you create an enormous amount of busywork for literally thousands of people to save, what, a 10K object file and 100 lines of source? Something on that order I bet. It doesn't make any sense. So there are two tiny leftover source files. I'm sure in the time saved not redoing all their box code, app developers can find some more valuable optimizations than removing those files from gtk. There's even a precedent from 1.2 - 2.0: http://svn.gnome.org/svn/gtk+/trunk/gtk/gtkseparatormenuitem.c How much has anyone suffered due to gtkseparatormenuitem.c? One of the box subclasses (whichever orientation is the default) should be the same size as gtkseparatormenuitem.c, and the other one should have 1 more line in its _init() to set the orientation. Saving that code does not warrant changing tens of thousands of lines of application code. Havoc (if one is compelled to hack on boxes, my suggestion is to leave GtkBox alone but add a new nicer container like HippoCanvasBox, its features include: * have left/right/center/fill x/y alignment * you only need 1 expand boolean, alignment replaces fill with something more powerful * support IF_FITS mode * support children that are requested/allocated but not shown * support setting four (painted or transparent) borders independently * virtualize the content of the box vs. the the layout part, enabling many widgets to subclass box and thus automatically be containers with alignment and borders * and yes, support dynamically setting orientation Or whatever the nicer features are ... you could call the new container GtkLayout since that name is likely old enough to be recycled ;-) ___ gtk-devel-list mailing list [EMAIL PROTECTED] http://mail.gnome.org/mailman/listinfo/gtk-devel-list ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday September 25 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
Thursday September 25 2008 - 14.00 (UTC) Form the Sugarlabs Bugsquad At this meeting we want to form the Sugarlabs Bugsquad, the Quality Assurance (QA) team for Sugar. The squad keeps track of current bugs in the sugar software and try to make sure that major bugs do not go unnoticed by developers. You do not need any programming knowledge to be in the Bugsquad; in fact it is a great way to return something to the Sugar community if you cannot program. The squad is modelled on the gnome bugsquad: http://developer.gnome.org/projects/bugsquad/ ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Multiple branches and translation of strings - seeking suggestions for best practices
Hi Arjun, Sarwal wrote: Hi, For the Activity that I maintain, I maintain two branches - devel and stable. At the time of a release contents of devel=stable. I am realizing that I am not implementing the best practice. As time passes stable continues to remain the same while I do development in devel. Thus devel becomes very divergent from stable. This also causes a large amount of strings to remain untranslated because stable is being translated and perhaps it doesnt make sense (?) to translate devel until a release into stable is made. So I want to ask, 1. Is there any use of maintaining such branches ? Or should I have just one development branch and 'tag' it at a release ? We do our development (unstable) on the master branch. Then when we have a special moment in time like the 8.2 release we make a special branch for that release, and do fixes specific to that release in that branch, this is now a stable branch (http://sugarlabs.org/go/ReleaseTeam#Branching). Ongoing development happens then in master. (Have a look at the browse activity, the master and sucrose-0.82 branch or the sugar module...) It is good to follow this. For example i was not able to see where the last measure activity has been released from http://dev.laptop.org/git?p=projects/measure;a=summary Do you use ./setup.py release to do a release? 2. If I do maintain such branches, should one undergo a cycle of localization(Translation) after each release of code from devel branch is made ? Translators do now have the ability (in pootle) to translate in the stable or unstable branch (sayamindu can give a more detailed explanation). Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Sugar DIgest 2008-09-22
6. Workshop of Telematics: Luis Michelena from the faculty of engineering at the Universidad de la República, Uruguay, will be using Sugar as a central theme for the projects to be carried out by students. Project suggestions most welcome. It is a bit dependent on the scope of the project what items you can suggest. If it was a semester project for example, working on the jukebox http://dev.laptop.org/git?p=projects/jukebox-activity;a=summary or a image viewer activity (zoom, rotate...) might be fructoseful. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-artwork 0.82.3
Sources: http://dev.laptop.org/pub/sugar/sources/sugar-artwork/sugar-artwork-0.82.3.tar.bz2 News: Fix corrupted network-wireless-060.svg ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Calculate 24
Reinier Heeres wrote: Hi, I released a new version of Calculate, it's available at: http://dev.laptop.org/~rwh/calculate/Calculate-24.xo Sources are at: http://dev.laptop.org/pub/sugar/sources/calculate-activity/Calculate-24.tar.bz2 NEWS entries: * Division by 0 returns 'Undefined' * Make 'clear' and 'enter' translatable * Remove pseudo.po * Fix ne.po (newlines) * Fix translations that had taken mul_sym litterally * Add COPYING and AUTHORS * Update MANIFEST Regards, Hmm you did not use the sucrose branch for your release http://dev.laptop.org/git?p=projects/calculate;a=shortlog;h=sucrose-0.82 Translators does push there. We need to get the translations you modified into Pootle - because Pootle does not know how to resolve git conflicts :/ So maybe best revert this commit and send a note to the localization list that the translators can push the changes themselves and then release from the sucrose branch (or discuss with sayamindu how to go best forward). Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Unannounced String Freeze break ??
Marco Pesenti Gritti wrote: On Fri, Sep 19, 2008 at 8:32 PM, Sayamindu Dasgupta [EMAIL PROTECTED] wrote: Hi all, While chewing through the translations on the final leg for 8.2, I noticed this commit in Sugar. http://dev.laptop.org/git?p=sugar;a=commitdiff;h=afaa5f77dd01948a27575602cf5c655d025990b9 It adds five new strings to sugar, and the patch mentions it does not come in the way of string freeze :-S (http://dev.laptop.org/attachment/ticket/7480/updated-network-module-for-control-panel-v3.diff). I am a bit confused. This is definitely a break in string freeze, and yet, the patch mentions that string freeze is not affected. Was a string freeze break approval asked for in this case ? I think we approved this in IRC. The reason the patchs says that it doesn't break the string freeze is that a previous version of the patch was changing strings, while this one only adds them. Yeah the comment could have been clearer :/ Sorry, I will make sure to announce it properly next time. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday September 18 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
---Topics--- * keep on reviewing the list we have at ReleaseTeam/Roadmap/0.84#Goals ---Note--- we want to hand out roadmap items to people if possible. So would be nice if the developers interested would join. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting MINUTES (Thursday September 18 2008 - 14.00 (UTC))
We made good progress on reviewing the list we have at ReleaseTeam/Roadmap/0.84#Goals * assigned owners and peers to all groups * started to assign owners to each feature You can find the orphaned items under ''Unassigned'' in each section. Give them a home! Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-0.82.7
sources: http://dev.laptop.org/pub/sugar/sources/sugar/sugar-0.82.7.tar.bz2 * finally remove numpy ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar 0.82.6
sources: http://dev.laptop.org/pub/sugar/sources/sugar/sugar-0.82.6.tar.bz2 = Closed tickets = * #8438 control panel fails when run with python -OO * #8470 SpreadLayout leaks self._collisions * #8375 gst usage in the shell wastes 2.6mb * #8372 Remove numpy usage from the shell = Testcases = #8375 Show the speaker icon and click on the slider/adjustment widget to the left of its handle. It should move an amount to the left and stop. Start an application playing that generates sound, so the volume changes in subsequent tests can be verified. |TestCase| Show the speaker icon and click on the slider/adjustment widget to the left of its handle until the handle is more than halfway to the left. The icon should display as partially, but not entirely, full. |TestCase| Show the speaker icon and click on the slider/adjustment widget to the left of its handle until it is most of the way to the left. The icon should display as mostly, but not entirely, empty. |TestCase| Show the speaker icon and move the slider/adjustment widget's handle all the way to the left. The icon should become white and the Mute text icon should change to Unmute. |TestCase| Show the speaker icon and move the slider/adjustment widget's handle all the way to the left. The icon should become white and the Mute text icon should change to Unmute. Now move the handle to the right one increment (by clicking or the right arrow key). The icon should become un-white and the Unmute text icon should change to Mute. |TestCase| Show the speaker icon and click Mute. The icon should become white and the Mute text icon should change to Unmute. |TestCase| Show the speaker icon and click Mute. The icon should become white and the Mute text icon should change to Unmute. Hide the speaker icon. Show it again. The icon should remain white and with the Unmute text/icon shown. Repeat hiding and showing the icon three (3) times. |TestCase| Show the speaker icon and move its slider's handle to somewhere near the middle. Click Mute. The icon should become white and the Mute text icon should change to Unmute. Now move the slider/adjustment widget's handle to the left or right and the icon should become un-white and the Unmute text icon should change to Mute. |TestCase| Show the speaker icon and note its slider/adjustment's handle's position. Press the XO volume up and volume down keys (F8, F9, IIRC) a few times to verify that those keys affect the slider. |TestCase| Set the volume to less than 100%. The icon should not be full. |TestCase| Show the speaker icon and note how full it is. Press the XO volume up and volume down keys (F8, F9, IIRC) a few times to verify that those keys affect the fullness. |TestCase| Show the speaker icon's popup menu and lower the volume slider. Close the popup menu. Press the XO increase volume/volume up button. Bring up the popup menu. Verify the slider has moved higher. |Test Case| Show the speaker icon/popup and note its slider/adjustment's handle's position. Using the slider, lower the volume just a bit. Close the popup menu. Press the XO keyboard's increase volume button. Bring up the popup menu. The slider should be higher. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] control panel keeps focus
Mikus Grinbergs wrote: Was using the Control Panel (called up from the palette of the central icon in Home View). Wanted to see which users were online, so pressed the key to take me to Neighborhood View. But could see very little of the Neighborhood View, since the XO was still showing me the Control Panel as occupying most of the screen. My question -- should the Control Panel be associated with Home View, such that calling up any other screen would hide the Control Panel, and allow the information from that other screen to occupy the entire display area -- or should the Control panel take over what the user sees, such that the user would have to complete what he was doing with the Control Panel in order for the Control Panel _NOT_ to overlay any other screen that the use might wish to see ? mikus The control panel is set transient to the home window (mesh, friends and home view). The journal and the activity zoom level can be retrieved when the panel is up. There was some discussion to make it only transient to the home view, eben what was your intention here? Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday September 11 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
---Topics--- * Roadmap ** keep on reviewing the list we have at ReleaseTeam/Roadmap/0.84#Goals * Sugarbot Zach Riggle will be talking about the sugarbot. sugarbot is a GUI automation utility for the OLPC Project's Sugar GUI. It provides functionality for developers to write tests for their Activities, and monitor those tests in a similar manner to unit-tests. sugarbot supports continuous integration with buildbot, so that multiple platforms and host configurations may be tested seamlessly. more here: http://sugarlabs.org/go/DevelopmentTeam/Meetings#Sugarbot ---Note--- We want to limit the meeting to 45 minutes - so be prepared to a dense, quick but hopefully successful meeting :) Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Gmail Activity
Marco Pesenti Gritti wrote: On Wed, Sep 10, 2008 at 3:02 AM, Walter Bender [EMAIL PROTECTED] wrote: I have finally gotten around to recreating the Gmail activity based on Browse-96. There is almost no resemblance to the original gmail activity, which was based on the old web activity. So the question is, do I try to make a giant patch, or just start from scratch? A diff would be better I think. We need to address the root problem here though. We can't duplicate the web activity code in every web based activity like we are doing. I tend to think it should be part of the 0.84 roadmap (as Stable activity API). I'm happy to work on refactoring the generic part of the Browse activity code into hulahop, if you are available to give me feedback on the requirements and try things out... I think we should make creating a web based activity as simple as subclassing hulahop.WebActivity and setting a few properties... Marco Yeah with last night experience I was reminded of that need. I think this would be a goal worth it. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [IAEP] Developing activities.
Marco Pesenti Gritti wrote: On Tue, Sep 2, 2008 at 6:05 PM, David Farning [EMAIL PROTECTED] wrote: 1. Create [EMAIL PROTECTED] mailing list. We have discussed this a few time over the last few months. Now that we are getting distro (other the OLPC) related comments the time seems right 2. Create [EMAIL PROTECTED] mailing list. This will focus on activity developer related issues. Are there strong reasons to separate the two lists? (Morgan seem to be making a different recommendation). Marco Yeah it is only meant as a way to notify the activity authors. An announcement list: http://wiki.laptop.org/go/User:Morgs/Activities_survey/Recommendations#Mailing_Lists All the rest of the discussion is going to the sugar-ml. Best, Simon PS: some will argue that you can use headers for that as well - but from morgan's survey I think we saw that this was the best way to go. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] related to #7856 and other Measure Activity Bugs
Marco Pesenti Gritti wrote: On Wed, Sep 3, 2008 at 6:38 PM, Arjun Sarwal [EMAIL PROTECTED] wrote: * If the problem related to #7856 is a sugar related bug, or if the Activity needs to do something differently It's a Sugar bug. In yesterday release meeting we agreed to give the Sugar devs (i.e. us!) another week to get a fix for this one in. I've been working on it a bit with Simon. I'll let you know how it goes. I have attached a patch to the ticket. However the bug of the grey screen does not seem to be effected by this. From my testing it is gone with the switch from measure-18 to measure-19. This is tested on 757 and 2385. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [Code-review] Please review recent rainbow patches.
It works but in the removing of rainbow/sugaractivity patch you have to include a little change. rainbow/rainbow/service.py:50:preload_common_modules 'rainbow.sugaractivity' Best, Simon Marco Pesenti Gritti wrote: I tested it a bit and the fixes for #5428 and #7921 seems to work. Can we get it in joyride asap to get more testing? Thanks, Marco On Thu, Aug 28, 2008 at 4:21 AM, Michael Stone [EMAIL PROTECTED] wrote: Folks, I've got a small flurry of rainbow patches (everything from rainbow-0.7.19..HEAD in http://dev.laptop.org/git/users/mstone/security) that could use a bit of review. Many thanks, Michael P.S. - http://teach.laptop.org/~mstone/rainbow.rpm is an RPM containing these patches. It's as yet untested, so I may well have broken things; however, fixing that can happen in parallel with the review. :) P.P.S. - I still haven't figured out how to really fix #8016 except by excruciatingly dirty hacks. Any thoughts would be appreciated. :( ___ Code-review mailing list [EMAIL PROTECTED] http://lists.laptop.org/listinfo/code-review ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] PlayGo v2 and v3
Andrés Ambrois wrote: On Friday 29 August 2008 04:17:01 Simon Schampijer wrote: Hi Andrés, thanks for your work! Ambrois wrote: I have put up the xo bundle for PlayGo version 3. I didn't announce v2 cause it was still lacking some features (like scoring at game end), which it now has. You can find it here: http://dev.laptop.org/~aa/PlayGo/PlayGo-3.xo Here are the Release Notes: v2 New Features: - Cleaner code - Save and resume games from Journal - Added a toolbar with options to set board size restart the game. - Better collaboration (turn enforcement, notifications) - Pass and Undo in hotseat (not shared) mode. - Full Spanish translation v3 New features: - Integration with GnuGo (play against AI) - Game end after two consecutive passes - Scoring under Japanese rules One thing that is lacking is a proper Icon (current one doesn't correctly change color), hopefully a generous soul will give us a new kick-ass icon for PlayGo! =P Yeah, maybe eben can have a quick look. I would really appreciate testing on the XO because I don't have one. Some breakfast notes: - when i resume a 9x9 game the tokens are squares no circles resuming the other games seem to work fine Yes, this bug is fixed in the git. With the recent Journal breakage (modalalert import error) I couldn't test it much. This bug was also triggered by #7904. - the reset game button maybe eben has an idea here (memorize uses one that is game specific, maybe we could have a general one) Sure, a common game restart icon should add consistency. I think best you file a ticket for the component 'interface-design' otherwise the idea gets lost. - is the 'You need to install gnugo...' a conditional message that changes or goes away when gnugo is installed? Right, it checks wether gnugo is on the PATH at startup and enables or disables that toggle button. So it should be yum install gnugo and you're ready to go. Hmm these dependency issues in general need to be solved at one point. Ideally gnugo should be installed with playgo. For the missing xo, maybe you want to apply for one at http://projectdb.olpc.at/ I'm on the DB. However I didn't apply for a project cause 'Developing an activity and do some general tinkering and hacking' didn't sound like a project that would get approved :). Oh I think it is worth it. You should apply. Having reliable maintainers of an activity is worth an xo in my opinion. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] PlayGo v2 and v3
Hi Andrés, thanks for your work! Ambrois wrote: I have put up the xo bundle for PlayGo version 3. I didn't announce v2 cause it was still lacking some features (like scoring at game end), which it now has. You can find it here: http://dev.laptop.org/~aa/PlayGo/PlayGo-3.xo Here are the Release Notes: v2 New Features: - Cleaner code - Save and resume games from Journal - Added a toolbar with options to set board size restart the game. - Better collaboration (turn enforcement, notifications) - Pass and Undo in hotseat (not shared) mode. - Full Spanish translation v3 New features: - Integration with GnuGo (play against AI) - Game end after two consecutive passes - Scoring under Japanese rules One thing that is lacking is a proper Icon (current one doesn't correctly change color), hopefully a generous soul will give us a new kick-ass icon for PlayGo! =P Yeah, maybe eben can have a quick look. I would really appreciate testing on the XO because I don't have one. Some breakfast notes: - when i resume a 9x9 game the tokens are squares no circles resuming the other games seem to work fine - the reset game button maybe eben has an idea here (memorize uses one that is game specific, maybe we could have a general one) - is the 'You need to install gnugo...' a conditional message that changes or goes away when gnugo is installed? For the missing xo, maybe you want to apply for one at http://projectdb.olpc.at/ Regards, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] PlayGo v2 and v3
Simon Schampijer wrote: Hi Andrés, thanks for your work! Ambrois wrote: I have put up the xo bundle for PlayGo version 3. I didn't announce v2 cause it was still lacking some features (like scoring at game end), which it now has. You can find it here: http://dev.laptop.org/~aa/PlayGo/PlayGo-3.xo Here are the Release Notes: v2 New Features: - Cleaner code - Save and resume games from Journal - Added a toolbar with options to set board size restart the game. - Better collaboration (turn enforcement, notifications) - Pass and Undo in hotseat (not shared) mode. - Full Spanish translation v3 New features: - Integration with GnuGo (play against AI) - Game end after two consecutive passes - Scoring under Japanese rules One thing that is lacking is a proper Icon (current one doesn't correctly change color), hopefully a generous soul will give us a new kick-ass icon for PlayGo! =P Yeah, maybe eben can have a quick look. I would really appreciate testing on the XO because I don't have one. Some breakfast notes: - when i resume a 9x9 game the tokens are squares no circles resuming the other games seem to work fine - the reset game button maybe eben has an idea here (memorize uses one that is game specific, maybe we could have a general one) - is the 'You need to install gnugo...' a conditional message that changes or goes away when gnugo is installed? For the missing xo, maybe you want to apply for one at http://projectdb.olpc.at/ Regards, Simon My d.l.o-down go at the icon :) Have fun, Simon inline: activity-go.svg___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Could someone test the Home search entry...?
Eben Eliason wrote: Hello all - I've recently experienced some very buggy behavior with the search entry in Home in my jhbuild (master). I want to ensure that this gets properly tested in the upcoming joyride build (as I'll be moving/on vacation myself), so I'm going to leave a couple test cases here for someone to take on. 1. Switch to the list view of Home and enter 'bro' into the search entry. The Browse activity should turn up as the only result in the filtered list. 2. Append a nonsense string to your search eg. 'broasdf'. If all goes well, you should have an empty list, though in my jhbuild testing, Browse remained visible. 3. Clear the search entry (select text and delete, or click the little 'x' button within the entry). The full list of installed activities should return. In my jhbuild testing, nothing could be done to restore the full list. If the above all work as expected, please verify the test case attached to http://dev.laptop.org/ticket/7874 as well. Finally, if this is all verified as working in joyride, it's probably still worth testing on the master branch in jhbuild, since I can't seem to get it to work there. Oddly, I tried reverting both sugar and sugar-toolkit to the last commits on August 13th (the day I submitted the patch attached to the aforementioned ticket, at which time that test case DID work fine in jhbuild), but the problem remained after rebuilding. Perhaps git just hates me. In any case, thanks for testing for me! If this IS broken, I nominate it as a blocker for 8.2.0, since it's easy to trigger a search, and impossible to clear it to reveal all installed activities, thus making it impossible to set favorites or launch some activities at all without a reboot. - Eben Eben I think a simple explanation is that there is old code in master :) def __entry_activated_cb(self, entry): if self._autosearch_timer: gobject.source_remove(self._autosearch_timer) new_query = entry.props.text if self._query != new_query and new_query is not '': That part should not be there: and new_query is not '': And maybe other parts as well. Will have a look once d.l.o is up again and verify your test case for master. Enjoy your holidays, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Could someone test the Home search entry...?
Simon Schampijer wrote: Eben Eliason wrote: Hello all - I've recently experienced some very buggy behavior with the search entry in Home in my jhbuild (master). I want to ensure that this gets properly tested in the upcoming joyride build (as I'll be moving/on vacation myself), so I'm going to leave a couple test cases here for someone to take on. 1. Switch to the list view of Home and enter 'bro' into the search entry. The Browse activity should turn up as the only result in the filtered list. 2. Append a nonsense string to your search eg. 'broasdf'. If all goes well, you should have an empty list, though in my jhbuild testing, Browse remained visible. 3. Clear the search entry (select text and delete, or click the little 'x' button within the entry). The full list of installed activities should return. In my jhbuild testing, nothing could be done to restore the full list. If the above all work as expected, please verify the test case attached to http://dev.laptop.org/ticket/7874 as well. Finally, if this is all verified as working in joyride, it's probably still worth testing on the master branch in jhbuild, since I can't seem to get it to work there. Oddly, I tried reverting both sugar and sugar-toolkit to the last commits on August 13th (the day I submitted the patch attached to the aforementioned ticket, at which time that test case DID work fine in jhbuild), but the problem remained after rebuilding. Perhaps git just hates me. In any case, thanks for testing for me! If this IS broken, I nominate it as a blocker for 8.2.0, since it's easy to trigger a search, and impossible to clear it to reveal all installed activities, thus making it impossible to set favorites or launch some activities at all without a reboot. - Eben Eben I think a simple explanation is that there is old code in master :) def __entry_activated_cb(self, entry): if self._autosearch_timer: gobject.source_remove(self._autosearch_timer) new_query = entry.props.text if self._query != new_query and new_query is not '': That part should not be there: and new_query is not '': And maybe other parts as well. Will have a look once d.l.o is up again and verify your test case for master. Enjoy your holidays, Simon So it was only the commit you made to the sucrose-0.82 branch missing in the master one (Fix clearing of search entry in Home (#7874)). The master is now working as you describe in your testcase. Have fun, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Log 14
sources: http://dev.laptop.org/pub/sugar/sources/log-activity/Log-14.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82.1/Log-14.xo News: - translation updates Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] August 28 - Sucrose 0.82.1 Tarballs Due
Dear maintainers, the next stable release is today the 28th August. Please provide source code tarballs by the end of today for the following modules: http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Glucose_Modules http://wiki.sugarlabs.org/go/ReleaseTeam/Roadmap#Fructose_Modules Please announce them as explained here: http://wiki.sugarlabs.org/go/ReleaseTeam#Module_release Please release as well when there are only string changes that we get the work that has the translators been doing in as well. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Browse 96
sources: http://dev.laptop.org/pub/sugar/sources/web-activity/Browse-96.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82.1/Browse-96.xo = Closed tickets = * #8055 Downloaded files have random part in their names * #5428 Added the updating of the profile dependent on version changes (note that for this to work you need the latest hulahop, rainbow, sugar and sugar-toolkit) = Testcases = #8055 open browse and download a file. The name should be recognizable and not have a random part in it Enjoy, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Hulahop 0.4.4
sources: http://dev.laptop.org/pub/sugar/sources/hulahop/hulahop-0.4.4.tar.bz2 News: Update the profile dependent on version changes #5428 Reflected are changes in the browse bundle version or the xulrunner version (marco) Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Journal 98
sources: http://dev.laptop.org/pub/sugar/sources/journal-activity/Journal-98.tar.bz2 = Closed tickets = * #7588 Sugar should provide messages indicating when NAND is getting full and critically full * #6800 Journal window should be mirrored in RTL locales = Testcases = #6800 Change sugar to use an arabic language. Open the journal. Try to modify the title of an entry. And the translations have been updated as well! Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting MINUTES (Thursday August 28 2008 - 14.00 (UTC))
We made good progress on our roadmap today http://sugarlabs.org/go/ReleaseTeam/Roadmap/0.84#Goals Please keep on updating and completing those pages, thanks! The next meeting will be September 11 since we will be at Fudcon http://fedoraproject.org/wiki/FUDCon/FUDConBrno2008 See you then, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar-meeting REMINDER (Thursday August 28 2008 - 14.00 (UTC)) --- irc.freenode.net, #sugar-meeting
Topics = Update = (Thrilling news of this week) Roadmap = * review the list we have at [[ReleaseTeam/Roadmap/0.84#Goals]] * do we finally agree on a 6 months cycle? = Status of bugfixing = * 82.0 bugs Please make sure to update the 0.84 roadmap since we want to talk about such points in this meeting. http://sugarlabs.org/go/ReleaseTeam/Roadmap/0.84#Goals Best, Simon PS: /me hopes that Eben is happy with our header format ;p ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [Announce] XO / Sugar Book Sprint
---please forgive crossposts--- XO / Sugar Book Sprint This week in Austin, Texas a team of writers are gathering together to immerse themselves in a one week intensive documentation jam. The purpose of the Book Sprint is to produce documentation in 1 week to support the forthcoming 2008 roll-out off the OLPC G1G1. The team in Austin consists of members of FLOSS Manuals (Adam Hyde, Anne Gentle), OLPC (Adam Holt), Sugar (David Farning, Walter Bender), and the Austin XO Users Group, and YOU! We have set up the online tools so you too can contribute! To make a contribution please do the following : 1. Register To contribute to the documentation you can register at FLOSS Manuals : http://en.flossmanuals.net/register 2. Contribute! There are several manuals planned to be finished by the end of the week (August 29) including a Sugar manual, an XO manual, and 5 Sugar Activities manuals. You can see the structure of the manuals here: Sugar : http://en.flossmanuals.net/bin/view/Sugar XO (OLPC Hardware) : http://en.flossmanuals.net/bin/view/XO Sugar Activities : http://en.flossmanuals.net/bin/view/Browse http://en.flossmanuals.net/bin/view/Chat http://en.flossmanuals.net/bin/view/Record http://en.flossmanuals.net/bin/view/Terminal http://en.flossmanuals.net/bin/view/Write To contribute you must register and then select a manual and a chapter to work on. if it is not marked 'complete' then press the edit button! Its as simple as that. Contributions can include cleaning up layout, spell checking, adding images, proof reading, or taking responsibility for writing one of more chapters. You don't have to be a technical writer or a super geek, you just need to know how to write. If you need to ask us questions about how to contribute then join the chat room listed above and ask us! We look forward to your contribution! For more information on using FLOSS Manuals you may also wish to read our manual : http://en.flossmanuals.net/FLOSSManuals 3. Chat Its a good idea to talk with us so we can help co-ordinate all contributions. We have a chat room for this using Internet Relay Chat (IRC). If you know how to use IRC you can connect to the following : server : irc.freenode.net channel : #olpc-content If you do not know how to use IRC then visit the following web based chat software in your browser : http://irc.flossmanuals.net/ Information on how to use this web based chat software is here : http://en.flossmanuals.net/FLOSSManuals/IRC ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Changes in Trac
Hello, in yesterdays sugar meeting and after some discussions on the devel mailing list we (michael, marco and myself) decided that the default milestone should be 'Not Triaged'. We renamed 'Retriage Please!' to 'Not Triaged' and made it the default milestone. In the end we think that it is up to the maintainer to set the milestone for a ticket. If the submitter or another person thinks this ticket is worth inclusion in a specific milestone he/she can express it in the keywords. Another change was the removing of the 'control panel' component. Components should map software modules which means that tickets for the control panel belongs in the sugar component. Please file your bugs regarding the control panel against sugar. All the existing tickets for the component 'control panel' have been moved to sugar before doing that change. In the hope that all the changes are working out well for you, Michael, Marco and Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [Announce] Sucrose 0.82 Final Release
Watch out your teeth! The Sucrose 0.82 Final Release is out! Sucrose 0.82 is the latest version of the Sugar education platform, consisting of Glucose, the base system environment; and Fructose, a set of demonstration activities. Sucrose is released every six months and contains many new features, improvements, bug fixes, and translations. Sucrose 0.82 continues this tradition and is our most well-planned release to date. To learn more about this release please visit the detailed release notes [1]. There will be another stable release (0.82.1) soon [2] and planning on the upcoming 0.84 has been started [3]. Many people contributed to this release indirectly, including testing, documentation, translation, contributing to the wiki, outreach to education and developer communities. On behalf of the community, we give our warmest thanks to the developers and contributors who made this sugar release possible. In behalf of the sugar community, Your release team [1] Release notes: http://sugarlabs.org/go/ReleaseTeam/Releases/Sucrose/0.82 [2] Schedule: http://sugarlabs.org/go/ReleaseTeam/Roadmap#Schedule [3] 0.84: http://sugarlabs.org/go/ReleaseTeam/Roadmap/0.84 ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar mtg minutes, August 21 2008
Logs http://dev.laptop.org/~erikos/meeting_logs/sugar-meeting-Aug-21-2008.log Topics = Update (Thrilling news of this week) = No special news this week = Roadmap = What do we want to do for [[ReleaseTeam/Roadmap/0.84]] ? * we aim for a 6 months cycle (another week to set this in stone) * please add your points to this page [[ReleaseTeam/Roadmap/0.84#Goals]] - we want to discuss these next week = Status of bugfixing = * which bugs rest for 0.82 ** marco will review the open reviews and give his opinion about landing in 8.2 ** erikos has to do 7480 and 7871 ** everyone should work on blockers, until 8/27 we can push fixes we have code already for (even though they are high and no blockers) if we get marcopg, cscott, or micahel to okay them. michael is happy if other bugs get fixed; he just don't want other bugs getting fixed at the expense of the blockers (more details will follow in another email). * stable releases: 0.82.1 will be a stable coordinated release (which will help to resynchronize translations), we will rely on non-coordinated module releases until then, the packages for the non-coordinated releases should be announced on the mailing list that packagers can step in and do the packaging work for their distributions ** release date for 0.8.2 is planned to be September the 17th (more details from michael) ** release date for 0.82.1 is planned to be September the 5th (more details in another email) = Control panel updater = has not happened this week Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Stable sucrose release 0.82.1
Hi, The stable sucrose release 0.82.1 is planned to be September the 5th. This coordinated release will help to resynchronize translations as well. Please get your translations in by then. We will rely on non-coordinated module releases until then. This means that each module maintainer that sees fit can do a release. This should help to reduce administrative overhead. The packages for the non-coordinated releases should be announced on the mailing list that packagers can step in and do the packaging work for their distributions. * release date for 0.8.2 is planned to be September the 17th (more details from Michael) * release date for 0.82.1 is planned to be September the 5th http://sugarlabs.org/go/ReleaseTeam/Roadmap#Schedule Sincerely, Your release team ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] 0.84 goals
Marco Pesenti Gritti wrote: Hello, I started working on the goals for 0.84 in the wiki: http://sugarlabs.org/go/ReleaseTeam/Roadmap/0.84#Goals Here is what I have so far. * Next generation journal * File sharing * Collaboration scalability * Responsive UI * Stable activities API * Official Sugar LiveCD * Compatibility with desktop applications * Quality and reliability Each of them points to a separate page in the wiki. I'll be working on several of these pages in the next weeks, writing down requirements, designs and thoughts about resourcing. Help wanted! As you can see the scope is very large. The plan is to narrow down each item to more concrete action items and then probably punt some of the high level goals. But I really want to get a bunch of stuff done this cycle!!! I know it's very vague for now. But if something is obvious missing please let me know or edit directly. Thanks, Marco Some points that came to my mind: - use of gconf for the control panel - what is about performance work - is this covered by 'Quality and reliability' ? - for the 'Next generation journal' I would like to see the possibility to have start-with in the palette of the entry (use-case: to open the source page you created in browse in write you need to use the detail view at the moment #7860). Eben had some ideas on what he want already. Thanks, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar mtg reminder, Thursday August 21 2008 - 14.00 (UTC) --- irc.freenode.net, #sugar-meeting
* Update Thrilling news of this week. * Roadmap What do we want to do for http://sugarlabs.org/go/ReleaseTeam/Roadmap/0.84#Goals * Status of bugfixing which bugs rest for 0.82 and when and in which manner do we release the new packages (the localization team asked for clarification as well) * Introducing the new developers * Control panel updater Design, consequences, profit! We will have guest speaker Scott coming in to talk about the sugar-control-update module and what this means to activity authors. Hope to see you there, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] Sugar mtg reminder, 14rd August 2008 --- 14.00 UTC --- irc.freenode.net, #sugar-meeting
* Update * Roadmap * Status of bugfixing * Introducing new developers * Better activity development communication - including activity development mailing list *Control panel updater - Implications for activity developers: How to publish releases Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [Announce] Memorize 27
Hi, I had been sad lately I did not have time to look into Memorize. This weekend I thought to at least release it so the translations are picked up. sources: http://dev.laptop.org/~erikos/sources/Memorize-27.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/Memorize-27.xo I added Memorize to the http://wiki.laptop.org/go/Activities/Joyride page so you can retrieve it from the activity updater in the control panel. NEWS: - added many new languages and updated a lot of translations (go translation team go!) For working sound you need to have a recent build (=joyride-2286). Thanks to Victor Lazzarini for fixing the liboggplay linking! The Memorize wiki page does need some love. Someone started a tutorial like section http://wiki.laptop.org/go/Memorize#Instructions What would really be great would be a tutorial on how to create new games. As I am short in time those days maybe someone wants to take this task :) Best, Simon PS: I am looking as well for possible maintainers, coders and people to document memorize. Feel free to contact me off or on-list. ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Reviews report
Gary C Martin wrote: On 11 Aug 2008, at 13:15, Release Team wrote: = Rejected requests = Palette persist over zoom levels http://dev.laptop.org/ticket/4084 GTK stock icon problems (has patch) http://dev.laptop.org/ticket/7641 Greyscreen on home view after looking at list view http://dev.laptop.org/ticket/7836 HippoCanvas does not support RTL rendering in RTL locales http://dev.laptop.org/ticket/3108 Presence Service should start even with no interfaces up http://dev.laptop.org/ticket/7451 Updates to Browse-92 fail. http://dev.laptop.org/ticket/7494 Zoom toolbar button should have a fixed order http://dev.laptop.org/ticket/6643 Default home view should be Ring, not Freeform http://dev.laptop.org/ticket/7759 Safer to always install, rather than comparing versions http://dev.laptop.org/ticket/7534 alt+tab switching is slow because activities are notified unneccessary http://dev.laptop.org/ticket/7625 Journal with time filters (most commonly 'past week') scrolling behaviour anomaly http://dev.laptop.org/ticket/7234 Sugar shell crashes when threads used. http://dev.laptop.org/ticket/7486 ohm and sugar should cooperate to unfreeze dcon http://dev.laptop.org/ticket/7357 sugar-shell enters in infinite loop after a failed shutdown http://dev.laptop.org/ticket/7566 cp: Inconsistent behavior after changing the xo color http://dev.laptop.org/ticket/7560 No feedback from 'register' request. http://dev.laptop.org/ticket/6136 Speaker device has inconsistent behavior http://dev.laptop.org/ticket/7248 react gracefully to dbus services being restarted http://dev.laptop.org/ticket/7740 H, all the review reports upto now seemed to make sense (and was useful to see), but this one's got me confused... I recognise quite a few of these rejected request as items already fixed, tested and working in the joyride builds. Are we just down to release timing cuts now to try and make the 8.2.0 official branch? --Gary Yeah sorry my bad. When triaging the bugs this morning i removed some r+ and moved the bugs to 'finalize'. The ones you see here are all fine and all in builds already. Like morgan pointed out this was a 'Premature optimization' :) Sorry for the noise, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Calculate 23
Reinier Heeres wrote: Hi, The Calculate-23 bundle should now include all necessary files due to the updated MANIFEST file. http://dev.laptop.org/pub/sugar/sources/calculate-activity/Calculate-23.tar.bz2 http://dev.laptop.org/~rwh/Calculate-23.xo Regards, Thanks, updated our release notes and the updater page: http://wiki.laptop.org/go/Activities/Joyride Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Pippy 24
sources: http://dev.laptop.org/pub/sugar/sources/pippy-activity/Pippy-24.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Pippy-24.xo - many new great translations Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Log 12
sources: http://dev.laptop.org/pub/sugar/sources/log-activity/Log-12.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Log-12.xo - translation update Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-base 0.82.1
sources: http://dev.laptop.org/pub/sugar/sources/sugar-base/sugar-base-0.82.1.tar.bz2 - update ALL_LINGUAS Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Journal 97
sources: http://dev.laptop.org/pub/sugar/sources/journal-activity/Journal-97.tar.bz2 * added languages Norwegian and Slovenian * translation updates Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-datastore 0.82.0
sources: http://dev.laptop.org/pub/sugar/sources/sugar-datastore/sugar-datastore-0.82.0.tar.bz2 - no news only updated to get the 0.82 version Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] sugar-artwork 0.82.0
sources: http://dev.laptop.org/pub/sugar/sources/sugar-artwork/sugar-artwork-0.82.0.tar.bz2 7641: Install GTK compatibility symlinks using icon-naming-utils package. The GTK stock icons use pre-standardized icon names. The sugar theme uses icon names from http://www.freedesktop.org/wiki/Specifications/icon-naming-spec but GTK still uses its internal names for stock icons. In order for stock buttons, icons, and existing GTK applications to be themed correctly, we need to install symlinks. NOTE: This commit adds a build dependency on the icon-naming-utils package, available in both Fedora and Debian. Packagers, take note. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Pippy 24
Simon Schampijer wrote: sources: http://dev.laptop.org/pub/sugar/sources/pippy-activity/Pippy-24.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Pippy-24.xo - many new great translations Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar sources: http://dev.laptop.org/pub/sugar/sources/pippy-activity/Pippy-25.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Pippy-25.xo ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] [RELEASE] Log 12
Simon Schampijer wrote: sources: http://dev.laptop.org/pub/sugar/sources/log-activity/Log-12.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Log-12.xo - translation update Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar sources: http://dev.laptop.org/pub/sugar/sources/log-activity/Log-13.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Log-13.xo ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
[sugar] [RELEASE] Write 57
sources: http://dev.laptop.org/pub/sugar/sources/write-activity/Write-57.tar.bz2 bundled: http://dev.laptop.org/~erikos/bundles/0.82/Write-57.xo * added languages Norwegian and Slovenian * translation updates Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
Re: [sugar] Proposal: Activity developers mailing list
Marco Pesenti Gritti wrote: Greg Smith wrote: Hi Bernie, I read the lists in digest except for Sur which I get individually because I was the first admin for that the list (can't seem to turn that off :-( I focus 100% on delivering the best experience possible for users of the 400K XOs shipped so far (50K more shipping every month). So I scan or read all the lists on lists.laptop.org and I try to stay up to date with wiki.laptop.org. Hello Greg, Sugar is a project with a very large scope. Many of the core contributors believes that the resources OLPC is able to devote to it are not going to be sufficient to fullfill it's long term goals or even to get near enough to them. We need to make Sugar available and used also outside OLPC to attract more contributors. That's the very reason of the existence of SugarLabs. On the long term that's going to be very useful to those 400K XOs in the field. That requires to establish Sugar as an independent FOSS project and building a community around it. And it's important for the identity of the project that the mailing lists and other services are available from its domain. After 8.2 is out and we are all a little less pressed, I'd like to propose that: 1 We move [EMAIL PROTECTED] to [EMAIL PROTECTED] OLPC specific issues related to Sugar can be discussed on [EMAIL PROTECTED] 2 We move Fructose git repositories on sugarlabs.org. They would be a couple of good steps towards the long-term goal and they would not hinder in any way the immediate OLPC goals. Cheers, Marco Right, the independent sugar FOSS project is the reason for all this moving. As marco said, we are quite sure that in the end this will help sugar to mature which will directly make the experience on the XO much better. Best, Simon ___ Sugar mailing list Sugar@lists.laptop.org http://lists.laptop.org/listinfo/sugar
