Re: [Sugar-devel] SL Bug #2063
On 10 October 2010 20:14, Mukul Gupta mu...@seeta.in wrote: With reference to SL Bug # 2063 which deals with bringing some kind of notification alert whenever an unhandled python exception occurs, I had a few doubts. There are two approaches that I can think of. Neither of these sounds sensible. What's wrong with the obvious solution of popping up a dialog when the exception occurs? Technically the exceptions are not unhandled, if they were unhandled then sugar would crash. I guess we're referring to exceptions that are not handled gracefully and instead fall back to a catch-all handler which does not have the knowledge to act on them. Daniel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Possible copyright infringement in activities.sl.o
On Sat, Oct 9, 2010 at 15:09, Walter Bender walter.ben...@gmail.com wrote: On Sat, Oct 9, 2010 at 8:28 AM, Gabriel Eirea gei...@gmail.com wrote: Well, we have the same problem at ceibaljam.org. The thing is, these games are being uploaded by 13-yr old kids. They discovered how to package activities in two ways: 1) using Pippy's export as .xo function. They download games from pygame.org and copy them at the right place in one of Pippy's generated xo files. 2) using Flavio's flash wrapper (http://ceibaljam.org/drupal/sites/default/files/JAMactivityFlash.activity.xo). This simply requires putting swf files in a folder and zipping the xo file. I think it is a very interesting result, but I agree it is difficult to make them understand about licenses and such. We had to take down many projects from ceibaljam.org because of this. I contacted them and tried to explain the situation. ¿Anyone has any suggestion on how to proceed such that we don't discourage them to hack further? Maybe we should encourage them to set up their own hosting site and in the process establish their own guidelines for what they consider publishable. Having to be personally responsible for establishing such guidelines will be a great opportunity for them to learn. (In my experience it is often the case that when the children are in the position of establishing the rules, they end up with a very conservative framework.) Sounds like a good idea, Google sites could work? Regards, Tomeu -walter Regards, Gabriel 2010/10/9 Tim McNamara paperl...@timmcnamara.co.nz: Hi all, This morning, I tested juegos_flash-2. It's just a sample of free (no cost) flash games from the Internet. I don't think Sugar Labs is be allowed to distribute them. Apart from these legal concerns, I also have some ethical ones. The package includes a game that teaches users how to mix cocktails. Another one of the activities is called Smack your ex. Here are my raw notes from the session: ## juegos_flash-2 - coloured icon - flash would wouldn't render the chess board at the start - seems to be a compilation of non-free flash games from various sites - gnash gave me English menus, everything else in Spanish - Penales - All rights reserved Flashfooty.com FTW - games failed to load after 20 secs - Penales2 - Games1.com Ad ?? - in English - selecting a team didn't seem to do anything - EncontrarObjectos - failed to load in 20 secs on XO-1.5 - Bar - Welcome to our pre-party cocktail mixing game for cocktail connoisseurs... or not as the case may be! - omg, it's actually a game about alcohol consumption - kinda cute, in it's own way. Provides instructions along the way, which is what I had expected from spirolaterals - Cocinarpizza - seemed unresponsive to the XO's mousepad - Ajedrez - argh, flashing chess game again - Futbal - ran very slowly - when missing a goal, the text is undefined - Tesoro - loaded well, a little slow on XO-1.5 - teacher seemed to be silent - Pes2002 - heavily screen flickering (gave up after 20sec) - Bolos - failed to load once Play was clicked - QueHariasConTuEx - from whackyourex.com - game does what it says Regards, Tim ___ 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 -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ 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] Status of Read activity (was: Re: Read Activity on Fedora 14 / SoaS v4)
On Sat, Oct 9, 2010 at 15:01, Sascha Silbe sascha-ml-reply-to-201...@silbe.org wrote: Excerpts from Lucian Branescu's message of Tue Sep 28 22:34:01 +0200 2010: Epub support is not complete, you can see epubs, but none of the toolbars work. [...] FWIW, I'd much rather see a working, but stripped-down Read upstream and in all distros than a working, stripped-down one in Fedora and a theoretically complete, but totally broken one everywhere else. Totally agreed, it's fine to regress in some features if that is needed in order to keep supporting the core features. Also, my work was on a somewhat old Read. I was hoping Read's maintainer would use my branch to port mainline, with whatever design for the epub view the maintainer considered a good idea. Who is the Read maintainer these days? AUTHORS still says Sayamindu, but AIUI he stopped working on Sugar stuff. He still intends to keep involved as much as his studies allow, we lost all contact for some weeks because of a technical issue. That said, I think to remember he was looking for someone to take over maintenance of Read. Regards, Tomeu Sascha -- http://sascha.silbe.org/ http://www.infra-silbe.de/ ___ 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] SL Bug #2063
On Mon, Oct 11, 2010 at 09:57, Daniel Drake d...@laptop.org wrote: On 10 October 2010 20:14, Mukul Gupta mu...@seeta.in wrote: With reference to SL Bug # 2063 which deals with bringing some kind of notification alert whenever an unhandled python exception occurs, I had a few doubts. There are two approaches that I can think of. Neither of these sounds sensible. What's wrong with the obvious solution of popping up a dialog when the exception occurs? Technically the exceptions are not unhandled, if they were unhandled then sugar would crash. I guess we're referring to exceptions that are not handled gracefully and instead fall back to a catch-all handler which does not have the knowledge to act on them. This is what abrt does with python (and other) processes, maybe we could reuse it or at least steal some of the ideas: https://fedorahosted.org/abrt/ Regards, Tomeu Daniel ___ 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
[Sugar-devel] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/collab/
Hi, would be nice to add support for annotations in Write now that Abiword supports it. Regards, Tomeu -- Forwarded message -- From: J.M. Maurer u...@uwog.net Date: Sat, Oct 9, 2010 at 17:30 Subject: Re: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/collab/core/session/xp plugins/opendocument plugins/opendocument/exp/xp plugins/opendocument/imp/xp src/af/gr/xp src/text/fmt/xp src/text/ptbl/xp src/wp/impexp/xp test/wp To: abiword-...@abisource.com Hi All! With this merge of Ben Martin's awesome work, AbiWord trunk (what will become AbiWord 2.9.0, the first 2.9 development release) has gained an awesome new feature: support for RDF. For those unfamiliar with RDF, you can read all about it on Wikipedia: http://en.wikipedia.org/wiki/Resource_Description_Framework It defines a metadata standard that AbiWord now supports. This means you can annotate pieces of content with generic metadata. For example you could attach contact data to a person who's name is mentioned in a text document. The use-cases are of course endless, so feel free to come up with cool use-cases, write patches, and we will gladly integrate them into AbiWord (or let you integrate them). A sample document containing RDF is attached. If you build AbiWord with debug support (--enable-debug) then you will find some fun RDF debugging menu items in the Collaborate menu (make sure to compile with --enable-plugins=collab). There is no particular reason why this in the Collaborate menu, it just had to go somewhere temporarily. There is full RDF support in AbiWord's internal model to hold the metadata. This work also supports reading and writing the metadata to AbiWord's native file format .abw and to OpenDocument .odt documents. Adding metadata to a document that is collaboratively being worked on will automatically synchronize the metadata as well. Surely there are certain bugs that need to be hashed out, but that's to be expected in a development release :) Cheers! Marc On Sat, 2010-10-09 at 17:06 +0200, c...@abisource.com wrote: Author: uwog Date: 2010-10-09 17:06:33 +0200 (Sat, 09 Oct 2010) New Revision: 29358 Added: abiword/trunk/plugins/opendocument/exp/xp/ODe_RDFWriter.cpp [snip] abiword/trunk/src/wp/impexp/xp/ie_imp_XML.h Log: svn merge -r29073:29323 svn+ssh://svn.abisource.com/svnroot/abiword/branches/monkeyiqrdf/ . ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SL Bug #2063
Tomeu and Daniel, On Mon, Oct 11, 2010 at 1:50 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Mon, Oct 11, 2010 at 09:57, Daniel Drake d...@laptop.org wrote: On 10 October 2010 20:14, Mukul Gupta mu...@seeta.in wrote: With reference to SL Bug # 2063 which deals with bringing some kind of notification alert whenever an unhandled python exception occurs, I had a few doubts. There are two approaches that I can think of. Neither of these sounds sensible. What's wrong with the obvious solution of popping up a dialog when the exception occurs? Technically the exceptions are not unhandled, if they were unhandled then sugar would crash. I guess we're referring to exceptions that are not handled gracefully and instead fall back to a catch-all handler which does not have the knowledge to act on them. This is what abrt does with python (and other) processes, maybe we could reuse it or at least steal some of the ideas: https://fedorahosted.org/abrt/ Thank you for the feedback and pointers. Appreciate it. We'll discuss the approach shared by you this afternoon. Regards, Manu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Possible copyright infringement in activities.sl.o
Tomeu, On Mon, Oct 11, 2010 at 1:40 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Sat, Oct 9, 2010 at 15:09, Walter Bender walter.ben...@gmail.com wrote: On Sat, Oct 9, 2010 at 8:28 AM, Gabriel Eirea gei...@gmail.com wrote: Well, we have the same problem at ceibaljam.org. The thing is, these games are being uploaded by 13-yr old kids. They discovered how to package activities in two ways: 1) using Pippy's export as .xo function. They download games from pygame.org and copy them at the right place in one of Pippy's generated xo files. 2) using Flavio's flash wrapper ( http://ceibaljam.org/drupal/sites/default/files/JAMactivityFlash.activity.xo ). This simply requires putting swf files in a folder and zipping the xo file. I think it is a very interesting result, but I agree it is difficult to make them understand about licenses and such. We had to take down many projects from ceibaljam.org because of this. I contacted them and tried to explain the situation. ¿Anyone has any suggestion on how to proceed such that we don't discourage them to hack further? Maybe we should encourage them to set up their own hosting site and in the process establish their own guidelines for what they consider publishable. Having to be personally responsible for establishing such guidelines will be a great opportunity for them to learn. (In my experience it is often the case that when the children are in the position of establishing the rules, they end up with a very conservative framework.) Sounds like a good idea, Google sites could work? +1 Manu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Add 'transient' property to Invoker #1742
Meaning that the palette will be disposed when it pops down.
---
src/sugar/graphics/palette.py |1 +
src/sugar/graphics/palettewindow.py | 20 +---
2 files changed, 18 insertions(+), 3 deletions(-)
diff --git a/src/sugar/graphics/palette.py b/src/sugar/graphics/palette.py
index d4632eb..d4f844c 100644
--- a/src/sugar/graphics/palette.py
+++ b/src/sugar/graphics/palette.py
@@ -158,6 +158,7 @@ class Palette(PaletteWindow):
self.popdown(immediate=True)
# Break the reference cycle. It looks like the gc is not able to free
# it, possibly because gtk.Menu memory handling is very special.
+self.menu.disconnect_by_func(self.__menu_item_inserted_cb)
self.menu = None
def __show_cb(self, widget):
diff --git a/src/sugar/graphics/palettewindow.py
b/src/sugar/graphics/palettewindow.py
index 22131c2..3c74662 100644
--- a/src/sugar/graphics/palettewindow.py
+++ b/src/sugar/graphics/palettewindow.py
@@ -179,6 +179,7 @@ class PaletteWindow(gtk.Window):
def __destroy_cb(self, palette):
self.set_group_id(None)
+self._mouse_detector.disconnect_by_func(self._mouse_slow_cb)
def set_invoker(self, invoker):
for hid in self._invoker_hids[:]:
@@ -457,6 +458,7 @@ class Invoker(gobject.GObject):
self._cursor_x = -1
self._cursor_y = -1
self._palette = None
+self._transient = False
def attach(self, parent):
self.parent = parent
@@ -639,18 +641,30 @@ class Invoker(gobject.GObject):
def set_palette(self, palette):
if self._palette is not None:
self._palette.popdown(immediate=True)
-
-if self._palette:
self._palette.props.invoker = None
+self._palette.destroy()
self._palette = palette
-if self._palette:
+if self._palette is not None:
self._palette.props.invoker = self
+self._palette.connect('popdown', self.__palette_popdown_cb)
palette = gobject.property(
type=object, setter=set_palette, getter=get_palette)
+def get_transient(self):
+return self._transient
+
+def set_transient(self, transient):
+self._transient = transient
+
+transient = gobject.property(type=object, setter=set_transient,
+ getter=get_transient)
+
+def __palette_popdown_cb(self, palette):
+if self.props.transient:
+self.set_palette(None)
class WidgetInvoker(Invoker):
--
1.7.2.3
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Make sure the buddy palette is disposed after popdown #1742
---
src/jarabe/view/buddyicon.py |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/src/jarabe/view/buddyicon.py b/src/jarabe/view/buddyicon.py
index 37b9167..15385bd 100644
--- a/src/jarabe/view/buddyicon.py
+++ b/src/jarabe/view/buddyicon.py
@@ -28,6 +28,8 @@ class BuddyIcon(CanvasIcon):
self._buddy.connect('notify::present', self.__buddy_notify_present_cb)
self._buddy.connect('notify::color', self.__buddy_notify_color_cb)
+self.palette_invoker.transient = True
+
self._update_color()
def create_palette(self):
--
1.7.2.3
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH] Add 'transient' property to Invoker #1742
Excerpts from Tomeu Vizoso's message of Mon Oct 11 11:34:37 +0200 2010: Meaning that the palette will be disposed when it pops down. I don't know how all this palette magic works, mainly because there's no documentation on it and it involves non-trivial interactions and cross-references between at least three different classes that have no inheritance relationship (even more if you do count the subclasses). So I can't really review your patch; however it would be nice if you could document the new attribute you're adding. Sascha -- 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
Re: [Sugar-devel] Possible copyright infringement in activities.sl.o
On Sat, Oct 9, 2010 at 8:28 AM, Gabriel Eirea gei...@gmail.com wrote: Well, we have the same problem at ceibaljam.org. The thing is, these games are being uploaded by 13-yr old kids. Is anyone in touch with them? [snip] -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [FEATURE] Journal_Sort --- cleanup for release
Hi Andrés, you might have missed that call. On 08/30/2010 08:44 AM, Simon Schampijer wrote: Hi Andrés, your Feature [1] has found it's way into the 0.90 release, thank you for getting this far! This is just great! The following items need to be done until the release at the end of the month (ordered by priority): * Instructions for testing: Please add detailed instructions on how to test your Feature (e.g. update with an existing DS etc). Can you add testing instructions to: http://wiki.sugarlabs.org/go/Features/Journal_Sort#How_To_Test ? * Bug fixing: Please watch out for bugs that have been introduced by your Feature. Can you have a look at: http://bugs.sugarlabs.org/ticket/2365 ? * Testing: As we do not have a very wide community of testers (yet) I would like to ask you to help in the testing efforts. It would be still very valuable if you could help here. Testing for example an update from an old to a new DS would be very valuable. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ANNOUNCE] Sucrose 0.90.1 Tarballs Due
Dear Sucrose Maintainers, we will have our first bug fix release in the 0.91 development cycle October the 15th [1]. For more info on the current schedule see as well the thread at [2]. Please provide the Sucrose 0.90.1 tarballs by Wednesday night (13th of October) and announce them as explained at [3]. Thanks, Simon [1] http://wiki.sugarlabs.org/go/0.90/Roadmap#Schedule [2] http://lists.sugarlabs.org/archive/sugar-devel/2010-October/027547.html [3] http://sugarlabs.org/go/Development_Team/Release#Module_release ___ 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] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col
Hi Tomeu, On 11 Oct 2010, at 09:25, Tomeu Vizoso to...@sugarlabs.org wrote: Hi, would be nice to add support for annotations in Write now that Abiword supports it. True, but only if you promise that the Write UI will get easier to use and not more difficult ;) I think we're falling towards featureitus while not managing complexity. Same thing is happening to Calculate. FWIW, in the Calculate case, I've been considering the need for a really simple calculator activity called Sums, with a very minimal feature set**. Perhaps we could do the same for Write and have a minimal feature set activity called Note (or Text if you don't mind that modern verb usage)? It would just be a simpler wrapper over the Abiword libs. Still not sure this is the right way to go to keep Sugar usable for our younger learners (where I think Sugar is most ideally placed), as having multiple Activities for the same activity does introduce additional maintenance, and testing load. ** Ideally we should try harder to better layer complexity in the Write, Calculate, et al UIs so that you need to drill down to the more complex features while the common/novice features are exposed early at the top level — but it seams there's only so far you can take this (Write and Calculate being on the cusp of this cliff edge). Regards, --Gary Regards, Tomeu -- Forwarded message -- From: J.M. Maurer u...@uwog.net Date: Sat, Oct 9, 2010 at 17:30 Subject: Re: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/collab/core/session/xp plugins/opendocument plugins/opendocument/exp/xp plugins/opendocument/imp/xp src/af/gr/xp src/text/fmt/xp src/text/ptbl/xp src/wp/impexp/xp test/wp To: abiword-...@abisource.com Hi All! With this merge of Ben Martin's awesome work, AbiWord trunk (what will become AbiWord 2.9.0, the first 2.9 development release) has gained an awesome new feature: support for RDF. For those unfamiliar with RDF, you can read all about it on Wikipedia: http://en.wikipedia.org/wiki/Resource_Description_Framework It defines a metadata standard that AbiWord now supports. This means you can annotate pieces of content with generic metadata. For example you could attach contact data to a person who's name is mentioned in a text document. The use-cases are of course endless, so feel free to come up with cool use-cases, write patches, and we will gladly integrate them into AbiWord (or let you integrate them). A sample document containing RDF is attached. If you build AbiWord with debug support (--enable-debug) then you will find some fun RDF debugging menu items in the Collaborate menu (make sure to compile with --enable-plugins=collab). There is no particular reason why this in the Collaborate menu, it just had to go somewhere temporarily. There is full RDF support in AbiWord's internal model to hold the metadata. This work also supports reading and writing the metadata to AbiWord's native file format .abw and to OpenDocument .odt documents. Adding metadata to a document that is collaboratively being worked on will automatically synchronize the metadata as well. Surely there are certain bugs that need to be hashed out, but that's to be expected in a development release :) Cheers! Marc On Sat, 2010-10-09 at 17:06 +0200, c...@abisource.com wrote: Author: uwog Date: 2010-10-09 17:06:33 +0200 (Sat, 09 Oct 2010) New Revision: 29358 Added: abiword/trunk/plugins/opendocument/exp/xp/ODe_RDFWriter.cpp [snip] abiword/trunk/src/wp/impexp/xp/ie_imp_XML.h Log: svn merge -r29073:29323 svn+ssh://svn.abisource.com/svnroot/abiword/branches/monkeyiqrdf/ . ___ 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] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col
On Mon, Oct 11, 2010 at 8:51 AM, Gary Martin garycmar...@googlemail.com wrote: Hi Tomeu, On 11 Oct 2010, at 09:25, Tomeu Vizoso to...@sugarlabs.org wrote: Hi, would be nice to add support for annotations in Write now that Abiword supports it. True, but only if you promise that the Write UI will get easier to use and not more difficult ;) I think we're falling towards featureitus while not managing complexity. Same thing is happening to Calculate. And Turtle Art, for that matter. I am working on a very stripped down version, Tortugita, which is more in the spirit of the original goals. That said, I think the family of activities approach taken by TamTam is a nice way to give the learner headroom as they advance in terms of skills and ambitions. regards. -walter FWIW, in the Calculate case, I've been considering the need for a really simple calculator activity called Sums, with a very minimal feature set**. Perhaps we could do the same for Write and have a minimal feature set activity called Note (or Text if you don't mind that modern verb usage)? It would just be a simpler wrapper over the Abiword libs. Still not sure this is the right way to go to keep Sugar usable for our younger learners (where I think Sugar is most ideally placed), as having multiple Activities for the same activity does introduce additional maintenance, and testing load. ** Ideally we should try harder to better layer complexity in the Write, Calculate, et al UIs so that you need to drill down to the more complex features while the common/novice features are exposed early at the top level — but it seams there's only so far you can take this (Write and Calculate being on the cusp of this cliff edge). Regards, --Gary Regards, Tomeu -- Forwarded message -- From: J.M. Maurer u...@uwog.net Date: Sat, Oct 9, 2010 at 17:30 Subject: Re: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/collab/core/session/xp plugins/opendocument plugins/opendocument/exp/xp plugins/opendocument/imp/xp src/af/gr/xp src/text/fmt/xp src/text/ptbl/xp src/wp/impexp/xp test/wp To: abiword-...@abisource.com Hi All! With this merge of Ben Martin's awesome work, AbiWord trunk (what will become AbiWord 2.9.0, the first 2.9 development release) has gained an awesome new feature: support for RDF. For those unfamiliar with RDF, you can read all about it on Wikipedia: http://en.wikipedia.org/wiki/Resource_Description_Framework It defines a metadata standard that AbiWord now supports. This means you can annotate pieces of content with generic metadata. For example you could attach contact data to a person who's name is mentioned in a text document. The use-cases are of course endless, so feel free to come up with cool use-cases, write patches, and we will gladly integrate them into AbiWord (or let you integrate them). A sample document containing RDF is attached. If you build AbiWord with debug support (--enable-debug) then you will find some fun RDF debugging menu items in the Collaborate menu (make sure to compile with --enable-plugins=collab). There is no particular reason why this in the Collaborate menu, it just had to go somewhere temporarily. There is full RDF support in AbiWord's internal model to hold the metadata. This work also supports reading and writing the metadata to AbiWord's native file format .abw and to OpenDocument .odt documents. Adding metadata to a document that is collaboratively being worked on will automatically synchronize the metadata as well. Surely there are certain bugs that need to be hashed out, but that's to be expected in a development release :) Cheers! Marc On Sat, 2010-10-09 at 17:06 +0200, c...@abisource.com wrote: Author: uwog Date: 2010-10-09 17:06:33 +0200 (Sat, 09 Oct 2010) New Revision: 29358 Added: abiword/trunk/plugins/opendocument/exp/xp/ODe_RDFWriter.cpp [snip] abiword/trunk/src/wp/impexp/xp/ie_imp_XML.h Log: svn merge -r29073:29323 svn+ssh://svn.abisource.com/svnroot/abiword/branches/monkeyiqrdf/ . ___ 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 -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] A little change to www.sugarlabs.org
Who can make a little change to the page www.sugarlabs.org? The links in the upper right zone (wiki / download / activities / donate) have a target=_blank attribute, and don't open in Browse. Regards Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] A little change to www.sugarlabs.org
On Mon, Oct 11, 2010 at 16:21, Gonzalo Odiard gonz...@laptop.org wrote: Who can make a little change to the page www.sugarlabs.org? The links in the upper right zone (wiki / download / activities / donate) have a target=_blank attribute, and don't open in Browse. Note that this has been reported before without much success, maybe now we'll manage to change it. At least in not-ancient versions of Browse, popups open as new tabs. Regards, Tomeu Regards Gonzalo ___ 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] [PATCH v4 sugar] Time out on registration process to prevent indefinite UI hang (SL#2289)
On 09/21/2010 02:46 AM, James Cameron wrote: On Mon, Sep 20, 2010 at 08:15:59PM +0530, Dipankar Patro wrote: Registration with the school server is currently done synchronously. To prevent the UI from hanging indefinitely, if the school server is reachable but unresponsive, we add an explicit timeout. --- src/jarabe/desktop/schoolserver.py | 27 --- 1 files changed, 24 insertions(+), 3 deletions(-) v2 was Reviewed-By: Sascha Silbesascha-pgp at silbe.org v3 was Reviewed-By: Sascha Silbesascha-pgp at silbe.org v3-v4: Rebased on current mainline/master Reviewed-By: James Cameronqu...@laptop.org This one has been ack'ed right? I can find no commit. As we have discovered those two bugs maybe we should land it in 0.90.1 and of course master? http://bugs.sugarlabs.org/ticket/2432 http://bugs.sugarlabs.org/ticket/2289 Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Bug update on ticket no 2080 (Pulsing icon delayed by 5 seconds)
Team, Wish to share on the observations that I gathered on the basis of my discussion with Bernie last evening. It seems that the delay that occurs before the start of the pulsing icon is due to the zoom animation failing to render . We arrived at the idea of using a technique commonly applied in video games i.e. Frame Dropping, where we drop frames in order to maintain the frame rate. Using this idea, I have prepared a patch for SL 2080, and have tried it on my XO-1.5, where it seems to work better. I have tried to skip the animation to the last frame if the fps drops below the defaults fps of 20 , for a smooth animation to occur. Wish if the patch could be reviewed on an XO-1. If I am making mistakes or missing on any key aspect, please share feedback bluntly. Appreciate your support. Thank you. Regards, Anurag ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH v4 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
When we click on the icon of an activity we see a pulsing icon of that activity before the activity starts and usually there is a time delay between the clicking of the icon and appearance of the pulsing icon , where tha amount of delay differs by the complexity of the icon i.e. more complex the icon is larger is the delay. So here we tried to reduce that delay if not completely obliterate it , by making the duration of the first 5 pulses larger and during these 5 times the icon will only be zoomed in and not zoomed out so as to reduce the frame calculation load on the processor, Hence reducing the delay. --- src/sugar/graphics/animator.py |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) v1-v2 corrected layout according to pep-8 format v2-v3 removed increment operation of variable i in the for loop v3-v4 added the concept of frame skipping diff --git a/src/sugar/graphics/animator.py b/src/sugar/graphics/animator.py index 8fb298b..e3a3503 100644 --- a/src/sugar/graphics/animator.py +++ b/src/sugar/graphics/animator.py @@ -136,7 +136,7 @@ class Animation(object): start = self.start change = self.end - self.start -if t == duration: +if fps 20: # last frame frame = self.end else: -- 1.7.2.3 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v4 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
On Tue, 2010-10-12 at 05:42 +0530, Anurag Chowdhury wrote: diff --git a/src/sugar/graphics/animator.py b/src/sugar/graphics/animator.py index 8fb298b..e3a3503 100644 --- a/src/sugar/graphics/animator.py +++ b/src/sugar/graphics/animator.py @@ -136,7 +136,7 @@ class Animation(object): start = self.start change = self.end - self.start -if t == duration: +if fps 20: # last frame frame = self.end Ugh. 1) Where does this magic number 20 come from? 2) Isn't fps the *desired* frame-rate set by client code when creating the Animator instance? 3) The variable fps isn't even available within the Animator.do_frame(). Are you familiar with variable scoping OOP languages? 4) The patch isn't *adding* the check, it's *replacing* the existing check to terminate the animation normally. 5) Finally, have you executed Sugar at least once with the patch applied to check that it fixes the bug without introducing new problems? Because of (3), it will simply cause an exception. Even if it worked, it would make Sugar skip all animations at 20fps and turn all the others into infinite loops, which is hardly the desired effect. I recommend switching to an easier bug. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Sugar Command - ruins the JOURNAL
If the kid types sugar command it erases the journal (after resetting the XO). A child contact us for that problem. is it possible to recovery the old Journal? A child contacted us for this problem http://www.mediagala.com/rap/foro/viewtopic.php?f=8t=586, he typed the command sugar in TERMINAL If I type sugar command it appears TWO JOURNALS, but when I reset the XO the old JOurnal disappear We are using XO-1 , sugar 0.82 Paolo Benini Montevideo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] SL Bug #2063
Team, I had a discussion with Aleksey this morning at IRC on the feedback recommended yesterday. Thank you Daniel and Tomeu. Appreciate your ideas and pointers. We brainstormed on how the implementation of this functionality could be done, and found that whenever any uncaught exception is raised, the interpreter calls the sys.excepthook(type,value,traceback). Wish to have the feedback on whether excepthook implementation would be helpful to our use-case both short-term and long-term. Also, it would be wonderful if feedback could be shared on its implementation in the context of Sugar, or otherwise. Looking forward to hearing from you. Regards, Mukul Gupta On Mon, Oct 11, 2010 at 2:14 PM, Manusheel Gupta m...@seeta.in wrote: Tomeu and Daniel, On Mon, Oct 11, 2010 at 1:50 PM, Tomeu Vizoso to...@sugarlabs.org wrote: On Mon, Oct 11, 2010 at 09:57, Daniel Drake d...@laptop.org wrote: On 10 October 2010 20:14, Mukul Gupta mu...@seeta.in wrote: With reference to SL Bug # 2063 which deals with bringing some kind of notification alert whenever an unhandled python exception occurs, I had a few doubts. There are two approaches that I can think of. Neither of these sounds sensible. What's wrong with the obvious solution of popping up a dialog when the exception occurs? Technically the exceptions are not unhandled, if they were unhandled then sugar would crash. I guess we're referring to exceptions that are not handled gracefully and instead fall back to a catch-all handler which does not have the knowledge to act on them. This is what abrt does with python (and other) processes, maybe we could reuse it or at least steal some of the ideas: https://fedorahosted.org/abrt/ Thank you for the feedback and pointers. Appreciate it. We'll discuss the approach shared by you this afternoon. Regards, Manu ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Sugar Command - ruins the JOURNAL
On Mon, Oct 11, 2010 at 3:15 PM, nanon...@mediagala.com wrote: If the kid types sugar command it erases the journal (after resetting the XO). A child contact us for that problem. is it possible to recovery the old Journal? A child contacted us for this problem, he typed the command sugar in TERMINAL If I type sugar command it appears TWO JOURNALS, but when I reset the XO the old JOurnal disappear We are using XO-1 , sugar 0.82 Paolo Benini Montevideo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel I just replicated the bug. Pretty nasty. But I think there is a way to recover. From Terminal: cd ~/.sugar/default ls You should see several directories with the name datastore: datastore datastore1234.xx I believe the old datastore is the one with the long numeric name. Try the following: mv datastore datastore.empty mv datastore12xxx34.xx datastore reboot This worked for me... -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Downgrading activities not allowed. (#2164)
From: Shanjit Singh Jajmann shan...@seeta.in
Downgrading an activity is now made possible. When a .xo file of a version
older than the currently installed version is clicked, a downgrading option is
made available, by popping up of a confirmation alert. Depending upton the
choice selected you can downgrade the activity.
---
src/jarabe/journal/journalactivity.py | 31 +++--
src/jarabe/journal/listview.py| 7 ++-
src/jarabe/journal/misc.py| 56 -
src/jarabe/model/bundleregistry.py| 18 +++---
4 files changed, 91 insertions(+), 26 deletions(-)
mode change 100644 = 100755 src/jarabe/journal/journalactivity.py
mode change 100644 = 100755 src/jarabe/journal/misc.py
mode change 100644 = 100755 src/jarabe/model/bundleregistry.py
diff --git a/src/jarabe/journal/journalactivity.py
b/src/jarabe/journal/journalactivity.py
old mode 100644
new mode 100755
index 44cc018..5f9d708
--- a/src/jarabe/journal/journalactivity.py
+++ b/src/jarabe/journal/journalactivity.py
@@ -28,6 +28,7 @@ import os
from sugar.graphics.window import Window
from sugar.graphics.alert import ErrorAlert
+from sugar.graphics.alert import ConfirmationAlert
from sugar.bundle.bundle import ZipExtractException, RegistrationException
from sugar import env
@@ -128,7 +129,7 @@ class JournalActivity(Window):
self.connect('window-state-event', self.__window_state_event_cb)
self.connect('key-press-event', self._key_press_event_cb)
self.connect('focus-in-event', self._focus_in_event_cb)
-
+
model.created.connect(self.__model_created_cb)
model.updated.connect(self.__model_updated_cb)
model.deleted.connect(self.__model_deleted_cb)
@@ -136,7 +137,6 @@ class JournalActivity(Window):
self._dbus_service = JournalActivityDBusService(self)
self.iconify()
-
self._critical_space_alert = None
self._check_available_space()
@@ -145,7 +145,30 @@ class JournalActivity(Window):
alert.connect('response', self.__alert_response_cb)
self.add_alert(alert)
alert.show()
-
+
+def __activity_alert1_cb(self):
+ if misc.check_previous_install() == 1 and misc.return_checked()==0:
+ alert1 = ConfirmationAlert()
+ logging.debug('value of misc is %d',
misc.check_previous_install())
+ alert1.props.title=_('Previous Version Found')
+ alert1.props.msg = _('A previous version of an installed activity
was found. Are you sure you want to continue with installation ?
If Yes click Ok and the
activity icon of the older .xo file in the Journal')
+ alert1.connect('response', self.__alert1_response_cb)
+ self.add_alert(alert1)
+ alert1.show()
+
+def __alert1_response_cb(self, alert1, response_id):
+if response_id is gtk.RESPONSE_OK:
+logging.debug('value of checked initial %d', misc.return_checked())
+logging.debug('Installing previous version')
+self.remove_alert(alert1)
+misc.checked = 1
+logging.debug('value of checked final %d', misc.return_checked())
+
+elif response_id is gtk.RESPONSE_CANCEL:
+logging.debug('Cancelled by user')
+self.remove_alert(alert1)
+
def __alert_response_cb(self, alert, response_id):
self.remove_alert(alert)
@@ -166,6 +189,8 @@ class JournalActivity(Window):
self._list_view = ListView()
self._list_view.connect('detail-clicked', self.__detail_clicked_cb)
self._list_view.connect('clear-clicked', self.__clear_clicked_cb)
+self._list_view.connect('icon-clicked', self.__icon_clicked_cb)
+logging.debug('icon clicked in main')
self._main_view.pack_start(self._list_view)
self._list_view.show()
@@ -195,7 +220,11 @@ class JournalActivity(Window):
keyname = gtk.gdk.keyval_name(event.keyval)
if keyname == 'Escape':
self.show_main_view()
-
+
+def __icon_clicked_cb(self):
+ logging.debug('value of misc is %d',
misc.check_previous_install())
+ self.__activity_alert1_cb()
+
def __detail_clicked_cb(self, list_view, object_id):
self._show_secondary_view(object_id)
diff --git a/src/jarabe/journal/listview.py b/src/jarabe/journal/listview.py
index 3d6281a..4e59ed3 100644
--- a/src/jarabe/journal/listview.py
+++ b/src/jarabe/journal/listview.py
@@ -466,8 +466,12 @@ class ListView(BaseListView):
__gsignals__ = {
'detail-clicked': (gobject.SIGNAL_RUN_FIRST,
gobject.TYPE_NONE,
- ([object]))
+ ([object])),
+'icon-clicked': (gobject.SIGNAL_RUN_FIRST,
+
[Sugar-devel] [Design]: Issue SL 2164 (Downgrading activities not allowed)
Team, I am currently working on issue #2164 ( http://bugs.sugarlabs.org/ticket/2164 ) . Send my revised patch for review a few minutes ago. Wish to thank Aleksey for his feedback and reviews. In reference to Aleksey's comment on my patch yesterday - What about less invasive implementation, ie, instead of changing three files, it could be only popping up an alert in AlreadyInstalledException try..except block, misc.py is a part of Journal and raising an alert from it, sounds reasonable. We have arrived at two approaches towards enabling this feature - 1. Instead of calling misc.resume in Listview and then emitting the signal to JournalActivity. Creating JournalActivty.resume , having the exact same functionality as misc.resume. and calling it from listview.py and implementing alertbox from there. We would then not be calling misc.resume in Listview and emitting the signal to JournalActivity, which happens at this juncture in the code. 2. Replacing misc.resume to JournalActivity.resume everywhere, where ever called.( in all files). Appropriate importing of methods and files will be required to do this. Wish if you could share your recommendations on the above two approaches - Appreciate your support and feedback. Thanks Regards Shan ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v4 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
In my experience, it's easier start resolving tickets in activities than in the plataform. That worked for me: * start writing a new activity: you can do stupid things, while learn python and the interaction with the platform. * try t resolve easy tickets in activities: there are many in http://bugs.sugarlabs.org/ and http://dev.laptop.org/ * next try to solve problems in Sugar. Regards Gonzalo I recommend switching to an easier bug. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ 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 Command - ruins the JOURNAL
/Walter Bender wrote: mv datastore datastore.empty mv datastore12xxx34.xx datastore This worked for me... --/ Thank you very much, Walter, it worked for me too ! Paolo Benini Montevideo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH v4 sugar] Pulsing icon delayed by 5 seconds or so SL#2080
On Mon, 2010-10-11 at 18:23 -0300, Gonzalo Odiard wrote: In my experience, it's easier start resolving tickets in activities than in the plataform. That worked for me: * start writing a new activity: you can do stupid things, while learn python and the interaction with the platform. * try t resolve easy tickets in activities: there are many in http://bugs.sugarlabs.org/ and http://dev.laptop.org/ * next try to solve problems in Sugar. I completely agree with you. -- // Bernie Innocenti - http://codewiz.org/ \X/ Sugar Labs - http://sugarlabs.org/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Dextrose] [PATCH] Downgrading activities not allowed. (#2164)
On Tue, 2010-10-12 at 01:15 +0530, shan...@seeta.in wrote:
@@ -128,7 +129,7 @@ class JournalActivity(Window):
self.connect('window-state-event', self.__window_state_event_cb)
self.connect('key-press-event', self._key_press_event_cb)
self.connect('focus-in-event', self._focus_in_event_cb)
-
+
model.created.connect(self.__model_created_cb)
model.updated.connect(self.__model_updated_cb)
Here (and elsewhere) you're adding some invisible blanks.
@@ -145,7 +145,30 @@ class JournalActivity(Window):
alert.connect('response', self.__alert_response_cb)
self.add_alert(alert)
alert.show()
-
+
+def __activity_alert1_cb(self):
The name alert1 does not suggest much about what this alert is about.
How about version_alert?
+ logging.debug('value of misc is %d',
misc.check_previous_install())
+ alert1.props.title=_('Previous Version Found')
+ alert1.props.msg = _('A previous version of an installed
activity was found. Are you sure you want to continue with installation ?
If Yes click
Ok and the activity icon of the older .xo file in the Journal')
+ alert1.connect('response', self.__alert1_response_cb)
The message to the user isn't very clear: aren't we supposed to complain
only in the case of a downgrade?
+ self.add_alert(alert1)
+ alert1.show()
+
+def __alert1_response_cb(self, alert1, response_id):
+if response_id is gtk.RESPONSE_OK:
+logging.debug('value of checked initial %d',
misc.return_checked())
+logging.debug('Installing previous version')
+self.remove_alert(alert1)
+misc.checked = 1
+logging.debug('value of checked final %d', misc.return_checked())
+
+elif response_id is gtk.RESPONSE_CANCEL:
+logging.debug('Cancelled by user')
+self.remove_alert(alert1)
+
def __alert_response_cb(self, alert, response_id):
self.remove_alert(alert)
Why invoke __activity_alert1_cb synchronously? Since this function isn't
really a callback, you would move its entire body inline here.
@@ -527,6 +531,11 @@ class LyistView(BaseListView):
row = self.tree_view.get_model()[path]
metadata = model.get(row[ListModel.COLUMN_UID])
misc.resume(metadata)
+self.emit('icon-clicked')
Isn't this signal too generic for what we need to accomplish?
icon-clicked would trigger while clicking on *any* item in the Journal,
not just installable bundles, isn't it?
@@ -31,12 +31,16 @@ from sugar import mime
from sugar.bundle.activitybundle import ActivityBundle
from sugar.bundle.contentbundle import ContentBundle
from sugar import util
+from sugar.bundle.bundle import AlreadyInstalledException
from jarabe.view import launcher
from jarabe.model import bundleregistry, shell
from jarabe.journal.journalentrybundle import JournalEntryBundle
from jarabe.journal import model
+checker = 0
+checked = 0
+
Hmm... a global flag is probably going to have unintended effects. Also,
the name is too broad: checked *what*?
Thanks,
--
// Bernie Innocenti - http://codewiz.org/
\X/ Sugar Labs - http://sugarlabs.org/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH v4 sugar] Time out on registration process to prevent indefinite UI hang (SL#2289)
On Mon, Oct 11, 2010 at 08:39:12PM +0200, Simon Schampijer wrote: On 09/21/2010 02:46 AM, James Cameron wrote: On Mon, Sep 20, 2010 at 08:15:59PM +0530, Dipankar Patro wrote: Registration with the school server is currently done synchronously. To prevent the UI from hanging indefinitely, if the school server is reachable but unresponsive, we add an explicit timeout. --- src/jarabe/desktop/schoolserver.py | 27 --- 1 files changed, 24 insertions(+), 3 deletions(-) v2 was Reviewed-By: Sascha Silbesascha-pgp at silbe.org v3 was Reviewed-By: Sascha Silbesascha-pgp at silbe.org v3-v4: Rebased on current mainline/master Reviewed-By: James Cameronqu...@laptop.org This one has been ack'ed right? I can find no commit. I see no ack. I see no commit. http://patchwork.sugarlabs.org/patch/260/ has the two reviewed-by tags. As we have discovered those two bugs maybe we should land it in 0.90.1 and of course master? I see no significant reason why this should not be fixed for 0.90.1. Insignificant reasons are use of undocumented internals and the way that the port argument to TimeoutHTTP is checked without obvious reason. -- 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] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col
** Ideally we should try harder to better layer complexity in the Write, Calculate, et al UIs so that you need to drill down to the more complex features while the common/novice features are exposed early at the top level — but it seams there's only so far you can take this (Write and Calculate being on the cusp of this cliff edge). Maybe this question would be better on IAEP or SUR because its about pedagogy more than technology? More features just for features sake is not a good idea, Sugar is an educational tool not an office productivity tool, not all new office features need to be included. I would like to hear from teachers on this question. They might, for example, like annotation in a paperless classroom as a way of marking essays. I agree, we should try harder to layer complexity, in line with the goal of low entry and high ceiling. I think that children handle complexity and incomplete information much better than adults so its not necessary to give them cut down versions of Activities. As long as they can ignore features that they do not need and still get unobstructed access to the simplified features they are happy. Adults however are more likely to get stressed if presented with too many features. I looked at Calculate again. I am happy with the features. You can still do 9+1=10 by ignoring the extra features. None of the menus obscure simple calculator operation. If you select hexadecimal then 9+1=0xa but quitting and resuming reverts to decimal operation so it seems experimenting is likely to be harmless to simple calculator use. I share some responsibility for encouraging feature creep on TurtleArt. Maybe complexity could be layered better but I dont thinks it needs a version with it disabled. The goal should be that basic blocks, repeat, forward, right, are the ones most obviously presented to the learner and no amount of random clicking should make them not discoverable. Maybe the pallettes can be reordered to emphasise beginner blocks. With write, the goal would be to emphasise the beginner tools and deemphasise the advanced features, and make recovery from random clicking easy. Tony ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col
I think the main point of the annotation feature for Write will be allow teachers to correct children's writing. They can simply highlight a region and put in their correction or suggestion. Children can see the correction along with their original text. In abiword we do this with a dialog and a popup textbox but we've disabled dialogs in Write. I'd be interested in receiving suggestions for how to do this UI for Write and if it is wanted at all. Cheers Martin On Tue, Oct 12, 2010 at 10:33 AM, fors...@ozonline.com.au wrote: ** Ideally we should try harder to better layer complexity in the Write, Calculate, et al UIs so that you need to drill down to the more complex features while the common/novice features are exposed early at the top level — but it seams there's only so far you can take this (Write and Calculate being on the cusp of this cliff edge). Maybe this question would be better on IAEP or SUR because its about pedagogy more than technology? More features just for features sake is not a good idea, Sugar is an educational tool not an office productivity tool, not all new office features need to be included. I would like to hear from teachers on this question. They might, for example, like annotation in a paperless classroom as a way of marking essays. I agree, we should try harder to layer complexity, in line with the goal of low entry and high ceiling. I think that children handle complexity and incomplete information much better than adults so its not necessary to give them cut down versions of Activities. As long as they can ignore features that they do not need and still get unobstructed access to the simplified features they are happy. Adults however are more likely to get stressed if presented with too many features. I looked at Calculate again. I am happy with the features. You can still do 9+1=10 by ignoring the extra features. None of the menus obscure simple calculator operation. If you select hexadecimal then 9+1=0xa but quitting and resuming reverts to decimal operation so it seems experimenting is likely to be harmless to simple calculator use. I share some responsibility for encouraging feature creep on TurtleArt. Maybe complexity could be layered better but I dont thinks it needs a version with it disabled. The goal should be that basic blocks, repeat, forward, right, are the ones most obviously presented to the learner and no amount of random clicking should make them not discoverable. Maybe the pallettes can be reordered to emphasise beginner blocks. With write, the goal would be to emphasise the beginner tools and deemphasise the advanced features, and make recovery from random clicking easy. Tony ___ 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] [PATCH] Downgrading activities not allowed. (#2164)
Nak. See detailed comments below.
On Tue, Oct 12, 2010 at 01:15:34AM +0530, shan...@seeta.in wrote:
From: Shanjit Singh Jajmann shan...@seeta.in
Downgrading an activity is now made possible. When a .xo file of a version
older than the currently installed version is clicked, a downgrading option
is made available, by popping up of a confirmation alert. Depending upton the
choice selected you can downgrade the activity.
Please text wrap these subsequent lines of your commit message.
mode change 100644 = 100755 src/jarabe/journal/journalactivity.py
mode change 100644 = 100755 src/jarabe/journal/misc.py
mode change 100644 = 100755 src/jarabe/model/bundleregistry.py
You are incorrectly changing file modes. Please restore the file modes
before you commit.
@@ -128,7 +129,7 @@ class JournalActivity(Window):
self.connect('window-state-event', self.__window_state_event_cb)
self.connect('key-press-event', self._key_press_event_cb)
self.connect('focus-in-event', self._focus_in_event_cb)
-
+
Please remove this gratuitous whitespace change from your patch.
@@ -145,7 +145,30 @@ class JournalActivity(Window):
alert.connect('response', self.__alert_response_cb)
self.add_alert(alert)
alert.show()
-
+
+def __activity_alert1_cb(self):
Please use a method name that describes the action to be taken. As
Bernie pointed out, the name you used did not explain the reason for the
alert.
+ if misc.check_previous_install() == 1 and misc.return_checked()==0:
+ alert1 = ConfirmationAlert()
+ logging.debug('value of misc is %d',
misc.check_previous_install())
+ alert1.props.title=_('Previous Version Found')
+ alert1.props.msg = _('A previous version of an installed
activity was found. Are you sure you want to continue with installation ?
If Yes click
Ok and the activity icon of the older .xo file in the Journal')
The message you have written is ambiguous and could be read in either of
two ways; that the user has clicked on a newer version, or that the user
has clicked on an older version.
+def __alert1_response_cb(self, alert1, response_id):
+if response_id is gtk.RESPONSE_OK:
+logging.debug('value of checked initial %d',
misc.return_checked())
+logging.debug('Installing previous version')
+self.remove_alert(alert1)
+misc.checked = 1
+logging.debug('value of checked final %d', misc.return_checked())
+
+elif response_id is gtk.RESPONSE_CANCEL:
+logging.debug('Cancelled by user')
+self.remove_alert(alert1)
The logging is useful to you at this stage of development, but you
should assess whether it is useful to other developers. Perhaps some of
these and later logging calls should be removed.
@@ -148,31 +152,53 @@ def get_activities(metadata):
[...]
def resume(metadata, bundle_id=None):
registry = bundleregistry.get_registry()
-
+global checker
+global checked
I agree with Bernie ... there seems to be no justification for using
globals in this situation.
--
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] [Design]: Issue SL 2164 (Downgrading activities not allowed)
On Tue, Oct 12, 2010 at 01:17:07AM +0530, Shanjit Singh Jajmann wrote: Send (sic) my revised patch for review a few minutes ago. Wish to thank Aleksey for his feedback and reviews. http://patchwork.sugarlabs.org/patch/309/ is the patchwork thread on your revised patch. There have been two reviews since. In reference to Aleksey's comment on my patch yesterday - Please in future reply to the comment directly, so that the thread is maintained. I didn't take this new message of yours into consideration when I reviewed just now, because it wasn't linked. http://patchwork.sugarlabs.org/patch/296/ is the patchwork thread to which Aleksey responded. I've marked that patch superseded. -- 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] Sugar Command - ruins the JOURNAL
Tested on 0.84, the journal is not ruined. -- 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] Sugar Command - ruins the JOURNAL
Tested on 0.84, the journal is not ruined. Tested on 0.90 the journal is not ruined ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] add restart option configurable via gconf (#1206)
Nepal requested reordering and removal of restart, which was patched for
them in 0.82 and implemented in 0.84.
Paraguay and Uruguay detected the change in 0.84 and requested the
restart option be restored.
This patch restores the restart option as a configurable option, using
the gconf key /desktop/sugar/show_restart, default true.
Refer to http://bugs.sugarlabs.org/ticket/1206 for discussion.
---
data/sugar.schemas.in| 12
src/jarabe/view/buddymenu.py |6 ++
2 files changed, 18 insertions(+), 0 deletions(-)
diff --git a/data/sugar.schemas.in b/data/sugar.schemas.in
index cfa7edf..474753b 100644
--- a/data/sugar.schemas.in
+++ b/data/sugar.schemas.in
@@ -192,6 +192,18 @@
/schema
schema
+ key/schemas/desktop/sugar/show_restart/key
+ applyto/desktop/sugar/show_restart/applyto
+ ownersugar/owner
+ typebool/type
+ defaulttrue/default
+ locale name=C
+shortShow Restart/short
+longIf TRUE, Sugar will show a Restart option./long
+ /locale
+/schema
+
+schema
key/schemas/desktop/sugar/peripherals/keyboard/layouts/key
applyto/desktop/sugar/peripherals/keyboard/layouts/applyto
ownersugar/owner
diff --git a/src/jarabe/view/buddymenu.py b/src/jarabe/view/buddymenu.py
index 0ba6cc1..8ea2598 100644
--- a/src/jarabe/view/buddymenu.py
+++ b/src/jarabe/view/buddymenu.py
@@ -86,6 +86,12 @@ class BuddyMenu(Palette):
client = gconf.client_get_default()
+if client.get_bool('/desktop/sugar/show_restart'):
+item = MenuItem(_('Restart'), 'system-restart')
+item.connect('activate', self.__reboot_activate_cb)
+self.menu.append(item)
+item.show()
+
if client.get_bool('/desktop/sugar/show_logout'):
item = MenuItem(_('Logout'), 'system-logout')
item.connect('activate', self.__logout_activate_cb)
--
1.7.1
--
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] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col
Hi Martin, On 12 Oct 2010, at 00:51, Martin Sevior msev...@gmail.com wrote: I think the main point of the annotation feature for Write will be allow teachers to correct children's writing. They can simply highlight a region and put in their correction or suggestion. Children can see the correction along with their original text. In abiword we do this with a dialog and a popup textbox but we've disabled dialogs in Write. I'd be interested in receiving suggestions for how to do this UI for Write and if it is wanted at all. Do you have any screen shots available showing the new Abiword annotation features in action? I couldn't see any in the online documentation. Regards, --Gary Cheers Martin On Tue, Oct 12, 2010 at 10:33 AM, fors...@ozonline.com.au wrote: ** Ideally we should try harder to better layer complexity in the Write, Calculate, et al UIs so that you need to drill down to the more complex features while the common/novice features are exposed early at the top level — but it seams there's only so far you can take this (Write and Calculate being on the cusp of this cliff edge). Maybe this question would be better on IAEP or SUR because its about pedagogy more than technology? More features just for features sake is not a good idea, Sugar is an educational tool not an office productivity tool, not all new office features need to be included. I would like to hear from teachers on this question. They might, for example, like annotation in a paperless classroom as a way of marking essays. I agree, we should try harder to layer complexity, in line with the goal of low entry and high ceiling. I think that children handle complexity and incomplete information much better than adults so its not necessary to give them cut down versions of Activities. As long as they can ignore features that they do not need and still get unobstructed access to the simplified features they are happy. Adults however are more likely to get stressed if presented with too many features. I looked at Calculate again. I am happy with the features. You can still do 9+1=10 by ignoring the extra features. None of the menus obscure simple calculator operation. If you select hexadecimal then 9+1=0xa but quitting and resuming reverts to decimal operation so it seems experimenting is likely to be harmless to simple calculator use. I share some responsibility for encouraging feature creep on TurtleArt. Maybe complexity could be layered better but I dont thinks it needs a version with it disabled. The goal should be that basic blocks, repeat, forward, right, are the ones most obviously presented to the learner and no amount of random clicking should make them not discoverable. Maybe the pallettes can be reordered to emphasise beginner blocks. With write, the goal would be to emphasise the beginner tools and deemphasise the advanced features, and make recovery from random clicking easy. Tony ___ 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] annotation support in abiword (was Fwd: uwog - r29358 - in abiword/trunk: . plugins/collab/backends/service/xp plugins/collab/core/packet/xp plugins/collab/core/plugin/xp plugins/col
Hi Gary, OK I just made a screenshot. You can download it from this location. http://www.abisource.com/~msevior/AnnotationSS.jpg The popup appears when you hover the mouse over the purple dotted line which shows that region of text has an annotation. Sorry the gimp removes the mouse marker when it takes the screenshot. The whole UI has more features. You place an annotation by selecting text and choosing annotation from either the tools menu or from the right click contaxt menu. If you right click on the annotated region you can pop up the annotation dialog which allows you alter the annotation or replace the current text with the content of the annotation. To really see how the UI works though it is best to actually try it. Most recent versions of linux carry abiword 2.8. Even Ubtuntu! If you run windows you can download it from here. http://www.abisource.com/download/ Cheers Martin PS. Yes I use AbiWord all the time in day job :-) On Tue, Oct 12, 2010 at 12:19 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Martin, On 12 Oct 2010, at 00:51, Martin Sevior msev...@gmail.com wrote: I think the main point of the annotation feature for Write will be allow teachers to correct children's writing. They can simply highlight a region and put in their correction or suggestion. Children can see the correction along with their original text. In abiword we do this with a dialog and a popup textbox but we've disabled dialogs in Write. I'd be interested in receiving suggestions for how to do this UI for Write and if it is wanted at all. Do you have any screen shots available showing the new Abiword annotation features in action? I couldn't see any in the online documentation. Regards, --Gary Cheers Martin On Tue, Oct 12, 2010 at 10:33 AM, fors...@ozonline.com.au wrote: ** Ideally we should try harder to better layer complexity in the Write, Calculate, et al UIs so that you need to drill down to the more complex features while the common/novice features are exposed early at the top level — but it seams there's only so far you can take this (Write and Calculate being on the cusp of this cliff edge). Maybe this question would be better on IAEP or SUR because its about pedagogy more than technology? More features just for features sake is not a good idea, Sugar is an educational tool not an office productivity tool, not all new office features need to be included. I would like to hear from teachers on this question. They might, for example, like annotation in a paperless classroom as a way of marking essays. I agree, we should try harder to layer complexity, in line with the goal of low entry and high ceiling. I think that children handle complexity and incomplete information much better than adults so its not necessary to give them cut down versions of Activities. As long as they can ignore features that they do not need and still get unobstructed access to the simplified features they are happy. Adults however are more likely to get stressed if presented with too many features. I looked at Calculate again. I am happy with the features. You can still do 9+1=10 by ignoring the extra features. None of the menus obscure simple calculator operation. If you select hexadecimal then 9+1=0xa but quitting and resuming reverts to decimal operation so it seems experimenting is likely to be harmless to simple calculator use. I share some responsibility for encouraging feature creep on TurtleArt. Maybe complexity could be layered better but I dont thinks it needs a version with it disabled. The goal should be that basic blocks, repeat, forward, right, are the ones most obviously presented to the learner and no amount of random clicking should make them not discoverable. Maybe the pallettes can be reordered to emphasise beginner blocks. With write, the goal would be to emphasise the beginner tools and deemphasise the advanced features, and make recovery from random clicking easy. Tony ___ 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
