[Sugar-devel] Sugar docs
Hi, is this [1] the latest version of the Sugar docs? What is the current process for updates (e.g. the upcoming 0.96). Is there someone working on that end? There were questions here at the GNOME doc hackfest [2] what Sugar is doing for documentation and I am not sure if I am fully up to date. Regards, Simon [1] http://en.flossmanuals.net/sugar/ [2] https://live.gnome.org/Hackfests/BrnoDocs2012 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] GTK+ 3 theming: recent changes
Hi, there have been recent work on theming in GTK+. From the raleigh theme (the default theme that gets used if you did not apply a theme or loading failed) some default settings have been removed (like default background color and a default padding) [1][2]. As well the a11y-base.css [3] has been added which is a good resource for a very basic theme. For example the .spinbutton .button:first-child last-child can be of interest. Regards, Simon [1] http://git.gnome.org/browse/gtk+/commit/?id=6b04c0f828090a9cfb32ee4ab88a387db1f04736 [2] http://git.gnome.org/browse/gtk+/commit/?id=4dd9a73c8ae5254361e746a3013e952e0f72d6a3 [3] http://git.gnome.org/browse/gnome-themes-standard/tree/themes/a11y-base.css ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar docs
Hi Simon, Simon Schampijer si...@schampijer.de writes: is this [1] the latest version of the Sugar docs? What is the current process for updates (e.g. the upcoming 0.96). Is there someone working on that end? There were questions here at the GNOME doc hackfest [2] what Sugar is doing for documentation and I am not sure if I am fully up to date. At the SugarCamp in Paris, I brievely mentioned readthedocs: http://readthedocs.org/ Florent Pigout told me about this service, which looks quite nice. Maybe the Sugar community could use something like this instead of FlossManuals? FM may be suitable for end-users docs but not that much for developers docs. Best, -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar docs
On Mon, Feb 20, 2012 at 10:08 AM, Bastien b...@laptop.org wrote: Hi Simon, Simon Schampijer si...@schampijer.de writes: is this [1] the latest version of the Sugar docs? What is the current process for updates (e.g. the upcoming 0.96). Is there someone working on that end? There were questions here at the GNOME doc hackfest [2] what Sugar is doing for documentation and I am not sure if I am fully up to date. At the SugarCamp in Paris, I brievely mentioned readthedocs: http://readthedocs.org/ Florent Pigout told me about this service, which looks quite nice. Maybe the Sugar community could use something like this instead of FlossManuals? FM may be suitable for end-users docs but not that much for developers docs. Best, Regarding this, one major feedback that I have from new sugar devs is the lack of proper documentation about the Collab stack. Improving this is critical. Thanks and cheers. -- Bastien ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar docs
On Mon, 2012-02-20 at 11:10 -0500, Rafael Ortiz wrote: snip Regarding this, one major feedback that I have from new sugar devs is the lack of proper documentation about the Collab stack. Improving this is critical. +1 Jerry ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar v2] sl#2890, au#694: Changing to more user-friendly message.
Excerpts from Ajay Garg's message of 2012-02-20 06:57:33 +0100: Earlier, the Registration failed message seemed more like a threat. The new message sounds more like an information-conveying one. [...] I don't see any improvement over the previous patch [1] that would address the concerns I had back then (and others raised again in this thread). Sascha [1] https://patchwork.sugarlabs.org/patch/1039/ -- http://sascha.silbe.org/ http://www.infra-silbe.de/ signature.asc Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Backup / Restore Activities: some impressions
Hi Sascha, I had previously mentioned looking at the combination of your Backup (v5) and Restore (v4) Activities in order to facilitate the upgrades of the XOs at the Austrian pilot project. While time constraints unfortunately kept me from going ahead with the OS upgrades of all the children's XOs I did spend quite a lot of time experimenting with the two Activities and using them to pull Journal backups of the XOs for usage analysis, doing upgrades between builds 767 and 883, etc. In general the only real problem I ran into was on a machine whose name contained a ß which resulted in a slightly confusing error message telling me that the backup couldn't be created. One other issue which I found is that the Restore Activity seems to copy over the Journal backup from external media such as a USB drive to the internal flash memory before actually going ahead with the restore. This led to situations where I wasn't able to restore a 205MB backup on a machine which had 350MB of free disk space (after installing build 883) because I would have needed at least 410MB of free space. One possible enhancement that I can think of is adding a list of the installed Activities into a separate text file within the backup (which I now did manually). Aside from being useful for analysis purposes (which Activities did the users install independently vs. what the teacher had recommended, etc.) it would also help speed up the restore process by documenting which Activities the users had previously installed (and will likely need to be able to run the prior Journal entries). Otherwise the Activities seemed to work really well in the scenarios I tested such as going from builds 767 to 883 and carrying over several hundred Journal entries. Thanks for the great work! :-) Cheers, Christoph -- Christoph Derndorfer volunteer, OLPC (Austria) [www.olpc.at] editor, OLPC News [www.olpcnews.com] contributor, TechnikBasteln [www.technikbasteln.net] e-mail: christ...@derndorfer.eu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse and the move to WebKit
On Fri, Feb 17, 2012 at 5:07 PM, Jonas Smedegaard d...@jones.dk wrote: On 12-02-17 at 05:33am, Luke Kenneth Casson Leighton wrote: better news: i've just confirmed that: a) the removal of js_push_context and pop context was a spurious error, those functions are now restored, confirmed as compiling and existing (untested) b) the usual critical pyjamas-desktop tests, Helloworld, JSONRPCExample, KitchenSink and Mail all have the exact same behaviour as they used to, way back before the xpcom API breakage [where we all had to wait for todd whiteman to update pyxpcom] this is really really good news because it means that the people who have been keeping an eye on the debian packaging of hulahop and have been going arse! it's fecked! quite a lot will now be happy that it all works, and i am confident that within a few weeks/months people will be able to do apt-get install pyjamas-desktop python-hulahop again and have it all work. This is indeed quite exciting. Looking at your patch now and hopefully able to release a working Hulahop for Debian. ok. right, update: * hulahop works perfectly with xulrunner 9.0 * hulahop compiles with no modifications for xulrunner 10.0.0 but segfaults (two bugs) * hulahop _and_ xpcom require updates (PRBool-bool) for xulrunner 10.0.2 but segfaults (two bugs) * hulahop and xpcom with xulrunner 11 i haven't yet investigated the first bug is solved by compiling with --disable-jemalloc the second bug is related to window focus, and appears to either be solved for later versions ( 10.0.2) or is still under investigation: with the disconnect between the various trees and releases it's hard to tell without assistance from the mozilla team which patches are current, relevant etc. bottom line is: if you can live with xulrunner 9, it works perfectly, and is quite recent. and it's a lot better than webkit1. i really cannot stress enough how much webkitgtk with gobject introspection looks ok from the outside but is actually fundamentally flawed at the design level. you are entirely free to completely ignore this advice and entirely free to do whatever is most useful to you. l. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Browse and the move to WebKit
http://trac.webkit.org/wiki/WebKit2 ok: one of the issues that i ran into on the original (flawed) webkit-gobject development work, as well as the ports of pythonwebkit to gtk and directfb, was quite how integrated the whole thing had to be. there are now something like *eight* separate language bindings to webkit (including at least two javascript ones), each of which is in a separate state of development and even present *different* versions of the same underlying DOM API. it would appear that webkit2 has injected bundles which is a stupid way of saying you can install a shared library dynamically into webkit using dlopen. basically this means that it will at some point be able to - *without* having any dependency or *any* interaction with the webkit team - add language bindings and other features to webkit. i strongly, strongly, strongly advise the OLPC team to WAIT until such time as such code has been written, before proceeding with the use of webkit in OLPC. of course you are entirely free to do whatever you find to be most useful to you, choosing instead to learn for yourselves why webkit1's gobject introspection bindings are fundamentally flawed and spending significant time doing so. l. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
