Re: [Sugar-devel] [OLPC-AU] Browse is old
On 13 March 2012 07:15, Mikus Grinbergs mi...@bga.com wrote: I don't use it day-to-day, but for more than two years now I've been installing (via 'rpm') the midori browser in all the XO-1 builds that have ever been made available. My intent has been to have at least one (not counting Surf) webkit-based browser for comparison purposes. Depending upon the base-build content, sometimes additional dependencies (packages) needed to be installed to let midori run -- but I've always had this non-Gecko browser available on my XO systems. Do you know where I can get binaries for this that will work on F14-based XO builds? Thanks, Sridhar Sridhar Dhanapalan Engineering Manager One Laptop per Child Australia ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [OLPC-AU] Browse is old
On Wed, Mar 14, 2012 at 6:39 AM, Sridhar Dhanapalan srid...@laptop.org.au wrote: On 13 March 2012 07:15, Mikus Grinbergs mi...@bga.com wrote: I don't use it day-to-day, but for more than two years now I've been installing (via 'rpm') the midori browser in all the XO-1 builds that have ever been made available. My intent has been to have at least one (not counting Surf) webkit-based browser for comparison purposes. Depending upon the base-build content, sometimes additional dependencies (packages) needed to be installed to let midori run -- but I've always had this non-Gecko browser available on my XO systems. Do you know where I can get binaries for this that will work on F14-based XO builds? yum install midori from a terminal prompt running as root, but you'll get a browser running the version of webkit that ships on F-14. It's basically the same functionality as epiphany in that they both use the same underlying version of webkit. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [OLPC-AU] Browse is old
I've been installing (via 'rpm') the midori browser Do you know where I can get binaries for this that will work on F14-based XO builds? On build au200 I do 'yum install midori'. [The package comes in from the Fedora updates repository.] mikus ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] RFC:Simple Help widget for activities
El día 13 de marzo de 2012 00:22, Manuel Quiñones ma...@laptop.org escribió: Hi Gary, hi everybody, El día 9 de marzo de 2012 21:09, Gary Martin garycmar...@googlemail.com escribió: Hi Manuel, On 9 Mar 2012, at 03:36, Manuel Quiñones wrote: Hi Gonzalo, El día 7 de marzo de 2012 09:37, Gonzalo Odiard gonz...@laptop.org escribió: We receive many times request about adding help in the activities, and if is true Sugar propose a exploratory approach, not all the people learn in the same way, and there are people who prefer a little guidance. For the development we need a simple api, and easy i18n, and a non obtrusive experience for the user. Inspired by the DescriptionItem, I was experimenting with a widget to add simple help to activities. This is not: * A manual * Lessons * Tips Is a short startup help for the activity. I think tips can be better than direct guidance. Do this, then do that manner is counterproductive for exploration. Of course tips can be ordered in a convenient way, is a matter of manners. Would be better to see each section at once instead of a large scrollable list. I imagine a slideshow with back/forward buttons. Also I think visual help can be used instead of text when possible, so would be great if the widget allows it. Images can be understand by early children, and are universal, so no need to translate. Of course a little paragraph below the image can be convenient too. Here is a mockup I did for the same activity with this ideas: http://dev.laptop.org/~manuq/simple_help_mock.png What do people think? I think Gonzalo's mockup is a more attainable goal for most activities, it's using standard UI feature designs as used already else where in Sugar, and introduces no new metaphors (e.g. the iOS/iTunes like page dots). The trick (in either case) will be to keep them short and to the point, too much text, or too much fine detail and few will read much of them – writing the one for Calculate or Write is going to be a challenge to get right ;-) I think we should not be afraid to add new metaphors if this allows a better user experience to the children. I find an image with highlights, circled items and lines, a better explanation for an interaction than just text. Of course text-only can be left as a fallback, and we can concentrate in designing nice startup graphics for the core activities. I would like to see the text-only also having this slideshow view, so there is not too much text shown at the same time inside a scrolled window. Separated by sections / tips. At a side note, many iOS apps take the startup help route where they provide a graphical overlay that indicates what each button does (sometimes several overlays are needed for each different app view). These provide plenty of flexibility to the developer for the types of information they include (mixed text, graphics, even animation), and they place the help in context next to the real widgets; however they are harder to localise for more than a few languages and require reliable alpha compositing support for fullscreen overlays (ideally through hardware). Folding this information into a single palette, as per Gonzalo's mockup, looses the spacial information context (though the existing palette hints are still there for context if needed), but it seems a good design for us to provide some additional information and help point a user in the right direction. Yes, that help in context is so much more nice because it shows next to the real widgets. I think something similar is doable now with the GtkOverlay widget, but only for GTK+3. Maybe what Chrome does is a good intermediate between overlays in the real widgets and an image help. When opening Chrome for the first time I get a tab labelled First steps with this content: http://www.google.com/chrome/intl/es-419/welcome.html That is, an image with overlays. -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Fw: [REQUEST] ChimePlay-1
Dear Art, Well, music may be the universal language, but English UI strings sadly are not. In order to expand the potential user base for your efforts, I would encourage you to work on the internationalization of the UI strings with gettext in future versions. http://en.flossmanuals.net/make-your-own-sugar-activities/going-international-with-pootle/ and I will be happy to work with you on getting them set up in Pootle for localization. cjl Sugar Labs Translation Team Coordinator On Tue, Mar 13, 2012 at 3:56 PM, Walter Bender walter.ben...@gmail.com wrote: On Tue, Mar 13, 2012 at 1:13 PM, Art Hunkins abhun...@uncg.edu wrote: I'd appreciate a reviewer taking the time to review my new activity, ChimePlay. It has been in the queue for several weeks now (originally the queue contained 13 activities; it still does, FWIW). In case it matters, I've included here my response to Walter's request in regard to ChimePlay. (My response wasn't originally addressed to this list or to Walter personally.) Perhaps someone was waiting for me to address it? In any case, thanks for your support. Hmm. I thought someone pushed it through. Will take care of it now. I would like to sort a few things out with you regarding how to make all of your activities a little more friendly to some of our younger users. But that can happen sometime when we both have a bit more time. -walter Art Hunkins - Original Message - From: Art Hunkins abhun...@uncg.edu To: activit...@sugarlabs.org Cc: a...@lists.sugarlabs.org Sent: Saturday, March 03, 2012 4:36 PM Subject: Re: [REQUEST] ChimePlay-1 Hello, Walter, Thanks so much for your on-going help and encouragement for and with my Sugar activities. Without it, and similar counsel from other seasoned Sugar activity developers, I'd still be stuck in the Sugar starting gate. Your observations here can apply just as well to my previous 7 activities. Indeed, perhaps it is ironic that in ChimePlay there is the *least* amount of displayed verbiage of any of my activities; I've done my best to keep it down. (For my last three activities, which urge children to create their own audio samples, most of my commentary is included in a ReadMe.txt file. Only immediately relevent material is presented on-screen.) Some context: I am a professional art music composer, whose main electronic language is Csound. All my Sugar activities are spinoffs of live-performance Csound works composed for adults (please see my website, www.arthunkins.com, where these relationships are clear enough). At the urging of Richard Boulanger, I was led into OLPC, Sugar and the XO, to offer some of my work to at least the older children of the world. As an exclusively Windows person, Linux has been a strange new world - also inhabited by Sugar, Python, PyGTK, git, Inkscape - all equally new and strange. ChimePlay almost didn't get written; I thought that SamplePlay was my last activity. However, inspired by a couple of chime sets at the St. Francis Springs Prayer Center (Stoneville, NC, USA) and my life-long fascination with chimes and bells, ChimePlay manifested and here we are. In the future, I intend no more activities; I'll simply maintain and continue to test the 8 activities I have so that hopefully they remain useful. Hopefully you can humor me this one last time. I also hope my work points the way for other Csound artists to become involved with Sugar with an equally limited investment of time and technology. (Though I admit the requirements of my doing *anything* in Linux/Sugar was infinitely beyond any investment I'd anticipated. It's been an incredibly difficult and arduous learning curve. For example, I just spent three intense and frustrating days relearning Inkscape in order to create a passable icon for ChimePlay.) Early in my activity work, I found some Python/GTK code structures that I could reasonably understand and continue to use in all my activites. I've intentionally limited the depth of tech work I've exposed myself to, and only bugged other developers, like yourself, with issues I considered crucial. I've dealt with others (such as on-screen text, the limit to English, the treatment of MIDI device insertion/detection) in non-Sugar-like ways, which were understandable by low/non-tech me. I did this to protect myself and my sanity - as well as to complete anything. I'm well aware that most children will not have access to MIDI devices. For live Csound work in the adult world, however, MIDI devices are universally required. (In my recent activity ReadMe's, I've indeed recommended certain inexpensive devices to children and their teachers, especially the Korg nanoKontrol.) It seems to me that for any performance activity with Csound (such as for the XO or Sugar), classrooms might well opt to invest in a few MIDI devices, such as keyboard controllers. My activities allow for a very wide range of devices. In previous activities,
Re: [Sugar-devel] [PATCH sugar] If available use systemd to reboot/shutdown the system
El día 2 de marzo de 2012 05:51, Simon Schampijer
si...@schampijer.de escribió:
ConsoleKit is being obsoleted by systemd [1]. Accordingly use the
systemd D-Bus API now to Reboot and PowerOff the system. We keep the
fallback for ConsoleKit around. This adds a dependency on systemd.
[1] http://fedoraproject.org/wiki/Features/ckremoval
Signed-off-by: Simon Schampijer si...@laptop.org
Reviewed-by: Manuel Quiñones ma...@laptop.org
---
src/jarabe/model/session.py | 51 ++
1 files changed, 36 insertions(+), 15 deletions(-)
diff --git a/src/jarabe/model/session.py b/src/jarabe/model/session.py
index 9b277ff..4e66bdc 100644
--- a/src/jarabe/model/session.py
+++ b/src/jarabe/model/session.py
@@ -28,6 +28,10 @@ from sugar import env
_session_manager = None
+def have_systemd():
+ return os.access(/sys/fs/cgroup/systemd, 0) = 0
+
+
class SessionManager(session.SessionManager):
MODE_LOGOUT = 0
MODE_SHUTDOWN = 1
@@ -53,21 +57,38 @@ class SessionManager(session.SessionManager):
if env.is_emulator():
self._close_emulator()
elif self._logout_mode != self.MODE_LOGOUT:
- try:
- bus = dbus.SystemBus()
- proxy = bus.get_object('org.freedesktop.ConsoleKit',
- '/org/freedesktop/ConsoleKit/Manager')
- pm = dbus.Interface(proxy,
- 'org.freedesktop.ConsoleKit.Manager')
-
- if self._logout_mode == self.MODE_SHUTDOWN:
- pm.Stop()
- elif self._logout_mode == self.MODE_REBOOT:
- pm.Restart()
- except:
- logging.exception('Can not stop sugar')
- self.session.cancel_shutdown()
- return
+ bus = dbus.SystemBus()
+ if have_systemd():
+ try:
+ proxy = bus.get_object('org.freedesktop.login1',
+ '/org/freedesktop/login1')
+ pm = dbus.Interface(proxy,
+ 'org.freedesktop.login1.Manager')
+
+ if self._logout_mode == self.MODE_SHUTDOWN:
+ pm.PowerOff(False)
+ elif self._logout_mode == self.MODE_REBOOT:
+ pm.Reboot(True)
+ except:
+ logging.exception('Can not stop sugar')
+ self.session.cancel_shutdown()
+ return
+ else:
+ CONSOLEKIT_DBUS_PATH = '/org/freedesktop/ConsoleKit/Manager'
+ try:
+ proxy = bus.get_object('org.freedesktop.ConsoleKit',
+ CONSOLEKIT_DBUS_PATH)
+ pm = dbus.Interface(proxy,
+ 'org.freedesktop.ConsoleKit.Manager')
+
+ if self._logout_mode == self.MODE_SHUTDOWN:
+ pm.Stop()
+ elif self._logout_mode == self.MODE_REBOOT:
+ pm.Restart()
+ except:
+ logging.exception('Can not stop sugar')
+ self.session.cancel_shutdown()
+ return
Would be great to unify those try/except clauses, but the APIS differ
slightly, one uses pm.Stop/Restart, the other pm.PowerOff/Reboot, so
the separation is ok for me.
session.SessionManager.shutdown_completed(self)
gtk.main_quit()
--
1.7.7.6
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
--
.. manuq ..
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Kiwix for Sugar.
Hi. I found this on Tomeu's G+, good news. http://blog.wikimedia.org/2012/03/13/offline-reader-available-for-sugar/ Cheers. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar] If available use systemd to reboot/shutdown the system
On 03/14/2012 04:43 PM, Manuel Quiñones wrote:
El día 2 de marzo de 2012 05:51, Simon Schampijer
si...@schampijer.de escribió:
ConsoleKit is being obsoleted by systemd [1]. Accordingly use the
systemd D-Bus API now to Reboot and PowerOff the system. We keep the
fallback for ConsoleKit around. This adds a dependency on systemd.
[1] http://fedoraproject.org/wiki/Features/ckremoval
Signed-off-by: Simon Schampijersi...@laptop.org
Reviewed-by: Manuel Quiñonesma...@laptop.org
Thanks for the review. Pushed as
99bb52c5dbea01a3ffc9b8821ec12af2536f76ca after testing on F17 as working
fine so we can get wider testing.
---
src/jarabe/model/session.py | 51 ++
1 files changed, 36 insertions(+), 15 deletions(-)
diff --git a/src/jarabe/model/session.py b/src/jarabe/model/session.py
index 9b277ff..4e66bdc 100644
--- a/src/jarabe/model/session.py
+++ b/src/jarabe/model/session.py
@@ -28,6 +28,10 @@ from sugar import env
_session_manager = None
+def have_systemd():
+return os.access(/sys/fs/cgroup/systemd, 0)= 0
+
+
class SessionManager(session.SessionManager):
MODE_LOGOUT = 0
MODE_SHUTDOWN = 1
@@ -53,21 +57,38 @@ class SessionManager(session.SessionManager):
if env.is_emulator():
self._close_emulator()
elif self._logout_mode != self.MODE_LOGOUT:
-try:
-bus = dbus.SystemBus()
-proxy = bus.get_object('org.freedesktop.ConsoleKit',
- '/org/freedesktop/ConsoleKit/Manager')
-pm = dbus.Interface(proxy,
-'org.freedesktop.ConsoleKit.Manager')
-
-if self._logout_mode == self.MODE_SHUTDOWN:
-pm.Stop()
-elif self._logout_mode == self.MODE_REBOOT:
-pm.Restart()
-except:
-logging.exception('Can not stop sugar')
-self.session.cancel_shutdown()
-return
+bus = dbus.SystemBus()
+if have_systemd():
+try:
+proxy = bus.get_object('org.freedesktop.login1',
+ '/org/freedesktop/login1')
+pm = dbus.Interface(proxy,
+'org.freedesktop.login1.Manager')
+
+if self._logout_mode == self.MODE_SHUTDOWN:
+pm.PowerOff(False)
+elif self._logout_mode == self.MODE_REBOOT:
+pm.Reboot(True)
+except:
+logging.exception('Can not stop sugar')
+self.session.cancel_shutdown()
+return
+else:
+CONSOLEKIT_DBUS_PATH = '/org/freedesktop/ConsoleKit/Manager'
+try:
+proxy = bus.get_object('org.freedesktop.ConsoleKit',
+ CONSOLEKIT_DBUS_PATH)
+pm = dbus.Interface(proxy,
+'org.freedesktop.ConsoleKit.Manager')
+
+if self._logout_mode == self.MODE_SHUTDOWN:
+pm.Stop()
+elif self._logout_mode == self.MODE_REBOOT:
+pm.Restart()
+except:
+logging.exception('Can not stop sugar')
+self.session.cancel_shutdown()
+return
Would be great to unify those try/except clauses, but the APIS differ
slightly, one uses pm.Stop/Restart, the other pm.PowerOff/Reboot, so
the separation is ok for me.
Yes, we will remove ConsoleKit support at one point, that is why I did
conclude that I should not spend too much time to get fancy here.
Regards,
Simon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Glucose URGENT
Dear Localizers and Developers, The Glucose 0.95 development cycle is nearing it's completion with the release of Glucose 0.96 planned by the end of March. http://wiki.sugarlabs.org/go/0.96/Roadmap We have a number of languages that are complete and many more that are in need of a little more work to finish them off. http://translate.sugarlabs.org/projects/glucose/ Please make a special effort to get your Glucose project completed (and committed by your lang admin) in the next two weeks so that we can make this the best localized release of Sugar yet. We desperately need your help to make that goal. Localizations of Fructose and Honey activities are readily updated after the release, but it is important to get Glucose (and the sugar-update-control.po file from http://translate.sugarlabs.org/projects/olpc_software/) in the best shape possible for the release which will be repackaged for Linux distros with the L10n available at a given point in time. Please reach out to other potential localizers to help and as a special request to our developer community (which comes from a wide variety of mother tongues), please put on your localizer hat for a few days if you have your features for this release cycle landed. Warmest Regards, cjl Sugar Labs Translation Team Coordinator ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [RELEASE] sugar-0.95.5
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.95.5.tar.bz2 == News == * Release 0.95.5 (Simon Schampijer) * If available use systemd to reboot/shutdown the system (Simon Schampijer) * Journal detail view: don't choke on invalid 'keep' property (fixes SL#1591) (Sascha Silbe) * Avoid using a protected member in the filter of the favorites view (Gonzalo Odiard) * String format fix for View Source activity title, SL #3272 (Manuel Quiñones) * Commit from Sugar Labs: Translation System by user danishka.: 365 of 388 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user HoboPrimate.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 30 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 120 of 388 messages translated (5 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 125 of 388 messages translated (15 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 106 of 388 messages translated (24 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 146 of 388 messages translated (11 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 168 of 388 messages translated (12 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 153 of 388 messages translated (9 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 145 of 388 messages translated (7 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 224 of 388 messages translated (9 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 197 of 388 messages translated (5 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 255 of 388 messages translated (23 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 271 of 388 messages translated (5 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 297 of 388 messages translated (7 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 331 of 388 messages translated (3 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 360 of 388 messages translated (2 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 361 of 388 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 360 of 388 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 207 of 388 messages translated (17 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user mschlager.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user mschlager.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user samybt.: 388 of 388 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 276 of 388 messages translated (7 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 292 of 388 messages translated (5 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 125 of 388 messages translated (15 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 361 of 388 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 271 of 388 messages translated (5 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 158 of 388 messages translated (8 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 211 of 388 messages translated (12 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 357 of 388 messages translated (2 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 268 of 388 messages translated (6 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 60 of 388 messages translated (8 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 270 of 388 messages translated (5 fuzzy). (Pootle
[Sugar-devel] [RELEASE] sugar-toolkit-gtk3-0.95.4
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-toolkit-gtk3/sugar-toolkit-gtk3-0.95.4.tar.bz2 == News == * Release 0.95.4 (Simon Schampijer) * Port get_preview method to cairo (Simon Schampijer) * Commit from Sugar Labs: Translation System by user HoboPrimate.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 21 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 30 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 25 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 25 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 25 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user aputsiaq.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 30 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 34 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 25 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 29 of 35 messages translated (1 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 2 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 35 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 28 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 2 of 35 messages translated (0 fuzzy). (Pootle daemon) * Commit from Sugar Labs: Translation System by user cjl.: 30 of 35 messages translated (0 fuzzy). (Pootle daemon) *
[Sugar-devel] [RELEASE] sugar-artwork-0.95.3
== Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar-artwork/sugar-artwork-0.95.3.tar.bz2 == News == * Release 0.95.3 (Simon Schampijer) * Use border/padding properties in Gtk.Entry instead of inner-border property (Simon Schampijer) * Specify default border color as transparent (Simon Schampijer) * Revert another unintentional part of the gtk3 theme commit (Simon Schampijer) * Specify units for âborder-radiusâ, âborder-widthâ and âpaddingâ (Simon Schampijer) * Revert the unintentional part of the gtk3 theme (Simon Schampijer) ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Missing sysdep in Debian Testing (jhbuild)
Hello, I was compiling sugar with jhbuild and I found a missing dep. So, I created a ticket on the trac and I attached a patch. Here it is; * https://bugs.sugarlabs.org/ticket/3370 See you, -- Kaufmann Manuel Blog: http://humitos.wordpress.com/ Portfolio: http://fotos.mkaufmann.com.ar/ PyAr: http://www.python.com.ar/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Glucose URGENT
On Wed, Mar 14, 2012 at 3:54 PM, Khaled Hosny khaledho...@eglug.org wrote: Hi Chris: On Wed, Mar 14, 2012 at 01:45:29PM -0400, Chris Leonard wrote: Dear Localizers and Developers, The Glucose 0.95 development cycle is nearing it's completion with the release of Glucose 0.96 planned by the end of March. http://wiki.sugarlabs.org/go/0.96/Roadmap We have a number of languages that are complete and many more that are in need of a little more work to finish them off. http://translate.sugarlabs.org/projects/glucose/ While updating the Arabic translation I noticed that we now have an ar_SY translation (that is less complete that the ar one), and I think it should be removed since both are using Standard Arabic so the duplication will lead to inconsistent user experience (and less complete translation) for users running under a ar_SY locale than users running other Arabic locales. Regards, Khaled Khaled, This project was inherited from my predecessors; however, given your well known work in the field of Arabic FOSS L10n and contributions to Sugar and AbiWord RTL handling, I am inclined to take your advice. In the absence of a strong counter-argument, I will remove the ar-SY variant from Pootle in the next few days. Do you think there are any strings present there that you will want to harvest before I remove it? cjl Sugar Labs Translation Team Coordinator ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [DESIGN] Help with clipboard issue
I have filled the ticket http://bugs.sugarlabs.org/ticket/3371 with a issue with the clipboard and TTS. Do not copy all the explanation here, but I need a opinion about the proposed behaviour. Also I was testing the clipboard and reviewing the already existing tickets, and summarized the situation here http://wiki.laptop.org/go/User:Godiard/TestingClipboard Any help confirming my finding, if the tickets can be closed, or testing / solving the pending issues is welcomed. Regards, Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Glucose URGENT
I've been working on the translations, and by the weekend will have them finished. By then I'll also shout out here in the list for the other pt_PT translators to review them (I don't remember talking to any of them, but by looking in pootle I know they are out there. The same way they probably feel about me :) ) Eduardo No dia 14 de Março de 2012 17:45, Chris Leonard cjlhomeaddr...@gmail.com escreveu: Dear Localizers and Developers, The Glucose 0.95 development cycle is nearing it's completion with the release of Glucose 0.96 planned by the end of March. http://wiki.sugarlabs.org/go/0.96/Roadmap We have a number of languages that are complete and many more that are in need of a little more work to finish them off. http://translate.sugarlabs.org/projects/glucose/ Please make a special effort to get your Glucose project completed (and committed by your lang admin) in the next two weeks so that we can make this the best localized release of Sugar yet. We desperately need your help to make that goal. Localizations of Fructose and Honey activities are readily updated after the release, but it is important to get Glucose (and the sugar-update-control.po file from http://translate.sugarlabs.org/projects/olpc_software/) in the best shape possible for the release which will be repackaged for Linux distros with the L10n available at a given point in time. Please reach out to other potential localizers to help and as a special request to our developer community (which comes from a wide variety of mother tongues), please put on your localizer hat for a few days if you have your features for this release cycle landed. Warmest Regards, cjl Sugar Labs Translation Team Coordinator ___ Localization mailing list localizat...@lists.laptop.org http://lists.laptop.org/listinfo/localization ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Bulletin Boards
I think it never passed the idea phase, i.e., no planning or code (almost certain, but I'm not that involved in the project, just noticed that you had no answer yet). Eduardo No dia 12 de Março de 2012 00:11, Sridhar Dhanapalan srid...@laptop.org.au escreveu: We have recently started work on a new activity, which we called Noteboard [1]. I have since discovered that there is a very similar concept mentioned in the Sugar HIG, Bulletin Boards [2]. Is this idea implemented anywhere? I don't want us duplicating effort. If it doesn't exist, does anyone have any advice on how we can approach this? Thanks, Sridhar [1] https://dev.laptop.org.au/issues/634 [2] http://wiki.sugarlabs.org/go/Human_Interface_Guidelines/The_Laptop_Experience/Bulletin_Boards Sridhar Dhanapalan Engineering Manager One Laptop per Child Australia ___ IAEP -- It's An Education Project (not a laptop project!) i...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/iaep ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] sugar-0.95.5
On Wed, Mar 14, 2012 at 02:58:37PM -0400, Simon Schampijer wrote: == Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.95.5.tar.bz2 == News == The pootle commits hide the interesting commits. I suggest excluding them. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Glucose URGENT
On Thu, Mar 15, 2012 at 1:45 AM, Chris Leonard cjlhomeaddr...@gmail.com wrote:
Dear Localizers and Developers,
The Glucose 0.95 development cycle is nearing it's completion with the
release of Glucose 0.96 planned by the end of March.
http://wiki.sugarlabs.org/go/0.96/Roadmap
We have a number of languages that are complete and many more that are
in need of a little more work to finish them off.
http://translate.sugarlabs.org/projects/glucose/
Please make a special effort to get your Glucose project completed
(and committed by your lang admin) in the next two weeks so that we
can make this the best localized release of Sugar yet. We desperately
need your help to make that goal.
Localizations of Fructose and Honey activities are readily updated
after the release, but it is important to get Glucose (and the
sugar-update-control.po file from
http://translate.sugarlabs.org/projects/olpc_software/) in the best
shape possible for the release which will be repackaged for Linux
distros with the L10n available at a given point in time.
Please reach out to other potential localizers to help and as a
special request to our developer community (which comes from a wide
variety of mother tongues), please put on your localizer hat for a few
days if you have your features for this release cycle landed.
Warmest Regards,
cjl
Sugar Labs Translation Team Coordinator
___
Localization mailing list
localizat...@lists.laptop.org
http://lists.laptop.org/listinfo/localization
When try to Commit to VCS, an error occurred with following message:
Failed to commit file: [GIT] push of
('/var/lib/pootle/checkouts/glucose/sugar', 'po/zh_CN.po') failed: To
gitori...@git.sugarlabs.org:sugar/mainline.git ! [rejected] master -
master (non-fast-forward) error: failed to push some refs to
'gitori...@git.sugarlabs.org:sugar/mainline.git' To prevent you from
losing history, non-fast-forward updates were rejected Merge the
remote changes before pushing again. See the 'Note about
fast-forwards' section of 'git push --help' for details.
Is it not allowed to commit at this time?
Best,
Xin Wang
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Glucose URGENT
On Thu, Mar 15, 2012 at 7:55 AM, Alan Jhonn Aguiar Schwyn
alan...@hotmail.com wrote:
Failed to commit file: [GIT] push of
('/var/lib/pootle/checkouts/glucose/sugar', 'po/zh_CN.po') failed: To
gitori...@git.sugarlabs.org:sugar/mainline.git ! [rejected] master -
master (non-fast-forward) error: failed to push some refs to
'gitori...@git.sugarlabs.org:sugar/mainline.git' To prevent you from
losing history, non-fast-forward updates were rejected Merge the
remote changes before pushing again. See the 'Note about
fast-forwards' section of 'git push --help' for details.
Is it not allowed to commit at this time?
No is a permissions problems..
First make:
git pull
This download all changes... after, try again the push
It seems that I can not do these things in Pootle's web interface.
Regards!
Alan
Best,
Xin Wang
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Localization] Glucose URGENT
It seems that I can not do these things in Pootle's web interface. I think that you was on a clone of the git.. sorry.. Alan ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] sugar-0.95.5
On Wed, Mar 14, 2012 at 6:40 PM, James Cameron qu...@laptop.org wrote: On Wed, Mar 14, 2012 at 02:58:37PM -0400, Simon Schampijer wrote: == Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.95.5.tar.bz2 == News == The pootle commits hide the interesting commits. I suggest excluding them. My dearest Quozl, *coff* *coff* They may not rank as high in interest as new features to developers, but please consider that every pootle commit will add more learners to our user base than any number of whiz bang features or bug fixes. L10n is the megaphone for the superb work done by our development community, in military jargon it would be described as a force multiplier. Regards. cjl Sugar Labs Translation Team Coordinator ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] sugar-0.95.5
On Wed, Mar 14, 2012 at 10:06:52PM -0400, Chris Leonard wrote: On Wed, Mar 14, 2012 at 6:40 PM, James Cameron qu...@laptop.org wrote: On Wed, Mar 14, 2012 at 02:58:37PM -0400, Simon Schampijer wrote: == Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.95.5.tar.bz2 == News == The pootle commits hide the interesting commits. ?I suggest excluding them. My dearest Quozl, *coff* *coff* They may not rank as high in interest as new features to developers, but please consider that every pootle commit will add more learners to our user base than any number of whiz bang features or bug fixes. L10n is the megaphone for the superb work done by our development community, in military jargon it would be described as a force multiplier. Sort them then. The form they are in does not convey much information, and each line is much like the next. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Colombia] Kiwix for Sugar.
I haven't look at kiwix lately, but does it generate the files require a long step and cpu demanding process that arrange wikimedia + DB + plugins etc. [1] ? Of course those are great news indeed ! considering once the zim file is made it looks nice :-) Hopefully we'll see alternatives as well that can parse directly from wikpedia dump files like the wikipedia dumpreader, but this still lots of work [1] http://openzim.org/File:Schema_ZIM_File_Creation.png On Wed, Mar 14, 2012 at 11:26:59AM -0500, Rafael Ortiz wrote: Hi. I found this on Tomeu's G+, good news. http://blog.wikimedia.org/2012/03/13/offline-reader-available-for-sugar/ Cheers. ___ Colombia mailing list colom...@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/colombia ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [RELEASE] sugar-0.95.5
On Wed, Mar 14, 2012 at 10:38 PM, James Cameron qu...@laptop.org wrote: On Wed, Mar 14, 2012 at 10:06:52PM -0400, Chris Leonard wrote: On Wed, Mar 14, 2012 at 6:40 PM, James Cameron qu...@laptop.org wrote: On Wed, Mar 14, 2012 at 02:58:37PM -0400, Simon Schampijer wrote: == Source == http://download.sugarlabs.org/sources/sucrose/glucose/sugar/sugar-0.95.5.tar.bz2 == News == The pootle commits hide the interesting commits. ?I suggest excluding them. My dearest Quozl, *coff* *coff* They may not rank as high in interest as new features to developers, but please consider that every pootle commit will add more learners to our user base than any number of whiz bang features or bug fixes. L10n is the megaphone for the superb work done by our development community, in military jargon it would be described as a force multiplier. Sort them then. The form they are in does not convey much information, and each line is much like the next. Fair enough. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Harmonic Sugar distribuition
Hi all! There is a private email thread about how distribution might be organized within the heterogeneous systems that can be potentially used for Sugar installations. The background is, how such distribution should be formed. In my mind, such system is doomed to be based on community oriented solutions. So, I decided to share my thoughts publicly to discuss them. The system described below, should be finally implemented in Peru pilot [1] program (for sure, it will take several years and will start with pretty basic solutions). But, it shouldn't be treated as a local, for Peru, solution. It is a pilot for harmonic system to share various types of content (including activities) within the Sugar community. It will be useful to clearly separate the content to provide: (1) System components Highly depends on hardware, packages that are provided, mostly, by someone else, i.e., upstream. (2) Sucrose Sugar itself and the minimal startup kit of activities to start exploring the rest of accessible content (3) Favorited activities and content The majority of activities and content that people in the field will use. They are, at least, filtered by people (not upstream creators) who stamped them as stable and good, from edu pov, to start using as-is. (4) Universe activities and content The rest of content in the community. Might be new versions of (3) that are not yet favorited, new activities that might be included to (3), various kinds of experiments that, most likely, will not be included to (3). Common solutions: * (1) is entirely from upstream; GNU/Linux official repositories with system packages for regular desktops and system package (not sugar) for XO laptops from OLPC (as a hardware provider, not software); repositories should be LTS, systems in the field can't be updated too often * (2) is formed as singular project on OBS[2] (not OBS project per usecase) for every supported (for a long time, i.e., LTS as well) Sugar release; this OBS project is being built into a bunch of repositories with packages, basing on needs in the field, bunch of distros and arches; in other words, all people in the field, regardless their platform, use the same packages (but built for different platforms); in other words, something like Sweets Distribution[3] * (4) is basing on Sugar Network[4], as universal system for sharing various types of content that assumes not only online environments (not all users in the field have decent Internet connection); content creators, upload their creatures (activities, articles, books, etc) into Sugar Network; all these majority of content is accessible for all Sugar Network participants; more over, Sugar Network covers the full life cycle for this content: support for activities, feedback from users, sharing ideas/problems/opinions, sharing Journal objects created within uploaded activities, etc; * the previous point will make situation really messy; for that reason, (3) will take place; Sugar Network editors might pickup some content to make sure its quality is good enough for as-is usage; editing might be organized on several levels, i.e., particular deployment might deicide to apply some post-filters to the global Sugar Network content; such filtering might various from leaving it as-is to white and black lists; Some details: * (3) might occur not only in passive mode by staring some content, but also with: * reuse Sugar Network collaborative features to work with upstream creators to improve the quality * upload to Sugar Network improved versions of the content and make it favorited (if upstream is irresponsive) * (4) with Sugar Network will cover Activity Library (ASLO) features; it was made with intension, ASLO is limited in cases like: * no decent support for binary activities * no way to upload Journal objects created by activities * bad integration with Sugar Learning Environment (people need to open browse and login/register) * no way to support people's experiments, it handles only singular activity from original authors using Sugar Network doesn't exclude ASLO, the only thing, the focus should be switched form mirroring ASLO on Sugar Network to mirroring Sugar Network on ASLO * for activities, (4) means that users having (1) and (2), can start some Sugar Network client, findout on of (3) or (4) activities and click it to launch; in 100% for (3) and sometimes for (4), system will downlad prebuilt binaries, on OBS, to launch on client side; some times, for (4), will be downloaded sources to built on client side [1] http://wiki.sugarlabs.org/go/Deployment_Team/Peru/Puno [2] http://wiki.sugarlabs.org/go/Platform_Team/Open_Build_System [3] http://wiki.sugarlabs.org/go/Community/Distributions/Sweets_Distribution [4] http://wiki.sugarlabs.org/go/Sugar_Network -- Aleksey ___
