Re: [Sugar-devel] [ASLO] Release Browse-122
Browse-122 does not run on Ubuntu, because there is still no way to get hulahop in an Ubuntu package. Added to http://wiki.sugarlabs.org/go/BugSquad/Upstreaming_bugs#Ubuntu_11.4_Natty_Narwhal On Sat, May 28, 2011 4:54 am, Peter Robinson wrote: > On Sat, May 28, 2011 at 12:27 AM, Sugar Labs Activities > wrote: >> Activity Homepage: >> http://activities.sugarlabs.org/addon/4024 >> >> Sugar Platform: >> 0.82 - 0.92 >> >> Download Now: >> http://activities.sugarlabs.org/downloads/file/27390/browse-122.xo >> >> Release notes: > > Any chance we could have release notes and a tar file? > > Peter > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://wiki.sugarlabs.org/go/Replacing_Textbooks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Browse-122
Browse-122 does not run on Ubuntu, because there is still no way to get hulahop in an Ubuntu package. Added to http://wiki.sugarlabs.org/go/BugSquad/Upstreaming_bugs#Ubuntu_11.4_Natty_Narwhal On Sat, May 28, 2011 4:54 am, Peter Robinson wrote: > On Sat, May 28, 2011 at 12:27 AM, Sugar Labs Activities > wrote: >> Activity Homepage: >> http://activities.sugarlabs.org/addon/4024 >> >> Sugar Platform: >> 0.82 - 0.92 >> >> Download Now: >> http://activities.sugarlabs.org/downloads/file/27390/browse-122.xo >> >> Release notes: > > Any chance we could have release notes and a tar file? > > Peter > ___ > Sugar-devel mailing list > Sugar-devel@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel > -- Edward Mokurai (默雷/धर्ममेघशब्दगर्ज/دھرممیگھشبدگر ج) Cherlin Silent Thunder is my name, and Children are my nation. The Cosmos is my dwelling place, the Truth my destination. http://wiki.sugarlabs.org/go/Replacing_Textbooks ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Non-maintainer uploads of activities
On Sat, 2011-05-28 at 16:46 +0200, Sascha Silbe wrote: > I would like to propose adopting the Debian Non-Maintainer-Upload (NMU) > process [1] for Fructose. Individual activity authors would also be > encouraged to allow their activities to be NMU'ed following this policy. > The sections I'd consider applicable to Sugar Labs are 5.11.1, 5.11.2 > (read debian/changelog as Release Notes) and 5.11.4. Since the version > number rules are different in Sugar, the NMU should append ".1" instead > of "+nmu1" (e.g. "123.1" for an NMU based on the maintainer release > "123"). > > A few key points: > - NMUs are only to be done for bug fixes > - all bugs that get fixed by the NMU must have been reported in the BTS > [2] > - the maintainer must have been given sufficient time to act (rule of > thumb: 2-10 days depending on the severity of the bug that gets fixed) > > The Infrastructure Team [3] would be authorised to manage permissions > on git.sl.o and a.sl.o as needed for the NMU to happen. > > Since Sugar Labs lacks an equivalent of the Debian New Maintainer > process [4], I would like to add a requirement that the uploader has > successfully gone through review for a Sucrose (Glucose + Fructose) > package at least once and their patch been included in mainline. Note: > Patch author and uploader can be different persons. Very good idea, +1 from me. -- _ // Bernie Innocenti \X/ http://codewiz.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Tablet support
On Mon, May 23, 2011 at 4:22 PM, Sridhar Dhanapalan wrote: > On 7 March 2011 15:14, Peter Robinson wrote: >> Hi Wade, >> >> On Sun, Mar 6, 2011 at 2:27 PM, Wade Brainerd wrote: >>> Hi all, >>> >>> Chris Marshall, Ping Cheng (of Wacom) and myself have started work on a >>> project to add graphics tablet (such as Wacom Bamboo) to Sugar. >>> >>> Our goal is to submit patches over the next six months adding a wacom >>> driver, a control panel extension, and activity support to Sugar. >>> >>> We're targeting both XO and XO 1.5, currently planning to support 10.1.3 >>> and future builds. >>> >>> Progress reports will be posted to the project wiki page at >>> http://wiki.laptop.org/go/Projects/Tablet_Support. >> >> There should already be a driver for them as there's a driver for >> wacom tablets already included in Fedora, which the OS for the XO is >> based upon. In terms of changes to that you'll need to work with the >> upstream Fedora team to ensure changes to that go upstream first. I >> believe Peter Hutterer is doing quite a bit of work on the wacom >> drivers upstream at xorg at the moment so it might be worthwhile >> aligning with him to minimise duplication and ensure that its easy to >> get your work into future XO releases. > > Any news on where we are with this? This is an outline of what gnome is doing for tablet support. https://live.gnome.org/Design/SystemSettings/Tablet I'm not sure how much of the work can be reused, or be contributed to as part of their project to save on duplication. Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar] Add copy-to option in the Journal
Excerpts from Simon Schampijer's message of Wed May 25 00:53:36 +0200 2011: > This will be part of replacing the keep button. The discussion is taking place > at: http://lists.sugarlabs.org/archive/sugar-devel/2011-May/031316.html > There are mockups and the implementation details. I like the general idea. Unlike in the original mock-up, I wouldn't colour the "Copy To" menu item itself. For consistency all "Copy To" menus should include the storage devices (like you suggested). But those are for the Design Team to decide. [src/jarabe/journal/journaltoolbox.py] [...] > volume_monitor = gio.volume_monitor_get() > +icon_theme = gtk.icon_theme_get_default() > for mount in volume_monitor.get_mounts(): [...] We should add support for replacing the menu to sugar.graphics.palette.Palette (taking care of (dis)connecting item-inserted from/to self.__menu_item_inserted_cb) and just use CopyMenu instead of duplicating its functionality. [src/jarabe/journal/model.py] > @@ -616,6 +616,8 @@ def copy(metadata, mount_point): > """ > metadata = get(metadata['uid']) > file_path = get_file(metadata['uid']) > +if file_path is None: > +file_path = '' I guess this part has been obsoleted by your volume-error work. [src/jarabe/journal/palettes.py] > +class CopyMenu(gtk.Menu): [...] > +def __init__(self, metadata): [...] > +client = gconf.client_get_default() > +color = XoColor(client.get_string('/desktop/sugar/user/color')) > + > +clipboard_menu = ClipboardMenu(self._metadata) > +clipboard_menu.set_image(Icon(icon_name='transfer-from', > + xo_color=color, > + icon_size=gtk.ICON_SIZE_MENU)) Since the image is always the same, we can set it in ClipboardMenu.__init__() and get rid of the repetitions (we have multiple users of ClipboardMenu). Also the name confused me at first, we should rename it to ClipboardMenuItem. [...] > +journal_menu = VolumeMenu(self._metadata, _('Journal'), '/') > +journal_menu.set_image(Icon(icon_name='activity-journal', > +xo_color=color, > +icon_size=gtk.ICON_SIZE_MENU)) Dito (icon, VolumeMenuItem). > +volume_monitor = gio.volume_monitor_get() > +icon_theme = gtk.icon_theme_get_default() > +for mount in volume_monitor.get_mounts(): > +if self._metadata['mountpoint'] == mount.get_root().get_path(): > +continue > +volume_menu = VolumeMenu(self._metadata, mount.get_name(), > + mount.get_root().get_path()) minor indentation mismatch > +class VolumeMenu(MenuItem): [...] > +def __copy_to_volume_cb(self, menu_item, mount_point): [...] > +try: > +model.copy(self._metadata, mount_point) > +except IOError, e: > +logging.exception('Error while copying the entry. %s', > e.strerror) There's no need to include e.strerror in the message since the full Traceback is included in the log. > +self.emit('volume-error', > + _('Error while copying the entry. %s') % e.strerror, > + _('Error')) Maybe: _('Error while copying the entry: %s') % (e.strerror, ), > +class ClipboardMenu(MenuItem): [...] > +def __copy_to_clipboard_cb(self, menu_item): > +file_path = model.get_file(self._metadata['uid']) > +if not file_path or not os.path.exists(file_path): > +logging.warn('Entries without a file cannot be copied.') > +self.emit('volume-error', > + _('Entries without a file cannot be copied.'), > + _('Warning')) I wonder whether we should say "without content" instead of "without a file". Same for your recent patch [1] for OLPC#10798 [2]. Otherwise the patch looks good to me already. Nice work! Sascha [1] https://patchwork.sugarlabs.org/patch/793/ [2] https://dev.laptop.org/ticket/10798 -- 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] [PATCH sugar-toolkit] Only show joined buddies on sharer side, part of OLPC#10578
Excerpts from Simon Schampijer's message of Mon May 23 17:43:45 +0200 2011: > This is correct yes. Bad wording, better would be: "Show joined buddies > on both sides, part of OLPC #10578". OK, with that change: Acked-By: Sascha Silbe 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] [ASLO] Release Browse-122
On Sat, May 28, 2011 at 3:54 AM, Peter Robinson wrote: > On Sat, May 28, 2011 at 12:27 AM, Sugar Labs Activities > wrote: > > Activity Homepage: > > http://activities.sugarlabs.org/addon/4024 > > > > Sugar Platform: > > 0.82 - 0.92 > > > > Download Now: > > http://activities.sugarlabs.org/downloads/file/27390/browse-122.xo > > > > Release notes: > > Any chance we could have release notes and a tar file? > > Release notes Fall back to old style toolbars in old sugar . From: Sebastian Silva Based on patch by Wade from 2009: http://git.sugarlabs.org/~wadeb/browse/backwards-compatibility/commit/584939d3bc217b9463703e9a903caadf80c50d00 Tar file: http://download.sugarlabs.org/sources/sucrose/fructose/Browse/Browse-122.tar.bz2 Peter > ___ > 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 sugar] Raise alert when trying to send an entry without an associated file OLPC #10798
Excerpts from Simon Schampijer's message of Wed May 25 18:30:45 +0200 2011: > We raise the same error when we try to copy an entry without an > associated file to an external device. Acked-By: Sascha Silbe Thanks for the patch! Do you know if there has been any progress on transferring (all) metadata between systems (SL#2473 [1])? It's too bad the most convenient way to transfer Journal entries is crippled... Sascha [1] https://bugs.sugarlabs.org/ticket/2473 -- 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] [ASLO] Release Terminal-32
On Sat, May 28, 2011 at 3:58 AM, Peter Robinson wrote: > On Sat, May 28, 2011 at 2:14 AM, Sugar Labs Activities > wrote: > > Activity Homepage: > > http://activities.sugarlabs.org/addon/4043 > > > > Sugar Platform: > > 0.82 - 0.92 > > > > Download Now: > > http://activities.sugarlabs.org/downloads/file/27391/terminal-32.xo > > > > Release notes: > > * New Icon and fix for activity.info deprecations > > Bugs Fixed: SL#1492, SL#2172 > > Could we have a tar file release please? > > Tar file at: http://download.sugarlabs.org/sources/sucrose/fructose/Terminal/Terminal-32.tar.bz2 > Peter > ___ > 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 sugar] Convert nick to a str, follow up on OLPC #10735
Excerpts from Simon Schampijer's message of Wed May 25 17:41:13 +0200 2011: [src/jarabe/frame/activitiestray.py] > @@ -545,7 +545,7 @@ class IncomingTransferPalette(BaseTransferPalette): > > self.file_transfer.connect('notify::state', self.__notify_state_cb) > > -nick = self.file_transfer.buddy.props.nick > +nick = str(self.file_transfer.buddy.props.nick) > self.props.secondary_text = _('Transfer from %s') % (nick,) If we'd care about non-UTF-8 locales, this should read something like: nick = unicode(self.file_transfer.buddy.props.nick, 'utf-8') text = _('Transfer from %s') % (nick, ) self.props.secondary_text = text.encode('utf-8') with gettext.ugettext as _. However there's a lot more that will break in Sugar for non-UTF-8 locales, so for now: Acked-By: Sascha Silbe 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] [PATCH sugar] Display title in palette of shared activity OLPC #10676
Excerpts from Simon Schampijer's message of Wed May 25 15:57:34 +0200 2011: > The patch does display the activity name as primary text > and the session title as secondary text. This is coherent > with the palette of an activity in the frame. Looks nice and simple but seems to be more complicated in practice: We don't follow changes to the activity title because the palette gets created just once in ActivityView.__init__(). Since I don't see an easy way to make the palette on-demand, we need to add a new signal 'name-updated' to jarabe.model.neighborhood.ActivityModel() and listen to it in jarabe.desktop.meshbox.ActivityView(). 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] [PATCH sugar-toolkit] Handle DBUS tubes in the activity telepathy client, part of OLPC #10738
Excerpts from Simon Schampijer's message of Mon May 23 13:14:51 +0200 2011: > On 04/16/2011 01:05 PM, Sascha Silbe wrote: > > Excerpts from Simon Schampijer's message of Thu Apr 14 19:43:05 +0200 2011: > > > >> This adds the handling of DBUS tube channels to the > >> 'HandlerChannelFilter' in activity's telepathy client. > > > > It would be nice to have some rationale for the change. Why didn't we do > > this before and in what way is the new design better? Are there any > > compatibility issues for activities that don't use sugar-toolkit (e.g. > > because they're not written in Python)? > > I discussed these changes in detail with Tomeu and he was happy about them. Good to know, but doesn't answer my questions. What impact do these changes have on e.g. EToys? [telepathy.interfaces import] > Not relevant for the patch and the rest of the code in this area has the > same style. OK. [other changes] Thanks! 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] [PATCH sugar] Fix invitations from a non sugar client (empathy), part of OLPC #10814
Excerpts from Simon Schampijer's message of Mon May 23 14:44:47 +0200 2011: > >> +def join(self): > >> +logging.error('PrivateInvite.join handler %r', self._handler) > >> + > >> +registry = bundleregistry.get_registry() > >> +bundle_id = self.get_bundle_id() > >> +bundle = registry.get_bundle(bundle_id) > >> +if bundle is None: > >> +self._call_handle_with() > > > > What exactly does the latter part do? Reject the invitation? Or pass it > > on to a non-Sugar application? > > http://telepathy.freedesktop.org/spec/Channel_Dispatch_Operation.html#Method:HandleWith The only code path I could find that involves PrivateInvite.join() is: Invites._dispatch_non_sugar_invitation() Invites._add_private_invite(handler=CLIENT + '.org.laptop.Chat') (Invitation added to Frame, user accepts invitation) InviteButton.__clicked_cb() InviteButton._launch() PrivateInvite.join() Since handler is the constant mentioned above, BaseInvite.get_bundle_id() always returns 'org.laptop.Chat' when called in PrivateInvite.join(). That means the if-then part of PrivateInvite.join() is dead code. Sascha [1] https://bugs.sugarlabs.org/ticket/1750 -- 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] Non-maintainer uploads of activities
Hi! I would like to propose adopting the Debian Non-Maintainer-Upload (NMU) process [1] for Fructose. Individual activity authors would also be encouraged to allow their activities to be NMU'ed following this policy. The sections I'd consider applicable to Sugar Labs are 5.11.1, 5.11.2 (read debian/changelog as Release Notes) and 5.11.4. Since the version number rules are different in Sugar, the NMU should append ".1" instead of "+nmu1" (e.g. "123.1" for an NMU based on the maintainer release "123"). A few key points: - NMUs are only to be done for bug fixes - all bugs that get fixed by the NMU must have been reported in the BTS [2] - the maintainer must have been given sufficient time to act (rule of thumb: 2-10 days depending on the severity of the bug that gets fixed) The Infrastructure Team [3] would be authorised to manage permissions on git.sl.o and a.sl.o as needed for the NMU to happen. Since Sugar Labs lacks an equivalent of the Debian New Maintainer process [4], I would like to add a requirement that the uploader has successfully gone through review for a Sucrose (Glucose + Fructose) package at least once and their patch been included in mainline. Note: Patch author and uploader can be different persons. Sascha [1] http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu [2] https://bugs.sugarlabs.org/ [3] https://wiki.sugarlabs.org/go/Infrastructure_Team [4] http://www.debian.org/devel/join/newmaint -- 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] Should or should not i use PyGTK >= 2.4 widget ?
On Sat, May 28, 2011 at 5:04 AM, laurent bernabe wrote: > Thank you for your answers. > But i am not sure i can do my task just with an ObjectChooser. And i need > your advices for the strategy i should adopt : > >- I want my application to "save a graph" by writing the coordinates in >a text file => i am conviced that for this tasks, i should use the folder >data of the activity >- i want my application to "load a graph" from a previously recorded >graph >- but i also want the users to share other graphs each others : more >precisely, for users who don't have internet access (or for later systems >restores, maybe after a crash, for example) to be able to import files from >a usb key > > So, what is the best strategy in order to do these tasks and remain conform > to Sugar best practices ? > In general, using the Journal for these sorts of tasks is best practice in Sugar. You can set a file path with your data associated with your activity's datastore instance. That file can contain anything you want. It is typical to have a method that overrides the builtin write_file method -- called whenever the activity is either removed from the foreground or the activity exits -- from which you save data. def write_file(self, file_path): ''' Write the project to the Journal. ''' ... You can also set the mime type for this file, so as giving a hint as to what activities can subsequently open it. Lots of examples of this out there. -walter > Regards > > > 2011/5/27 Bert Freudenberg > >> Step 1: search wiki for ObjectChooser. >> Step 2: find http://wiki.sugarlabs.org/go/Activity_Team/Object_Chooser >> Step 3: there is no step 3 >> >> - Bert - >> >> On 27.05.2011, at 17:49, laurent bernabe wrote: >> >> > Thank you. >> > >> > I've been on Sugar Almanach page in order to find ObjectChooser class, >> but i did not manage. >> > (i've been here : http://wiki.sugarlabs.org/go/Development_Team/Almanac) >> > Where should i look ? >> > >> > Regards >> > >> > 2011/5/27 Gonzalo Odiard >> > If you use a FileChooserDialog, you don't have integration with the >> Journal. >> > You must use ObjectChooser. >> > >> > Gonzalo >> > >> > On Fri, May 27, 2011 at 11:56 AM, laurent bernabe < >> laurent.bern...@gmail.com> wrote: >> > Hello, >> > >> > i would like to use the FileChooserDialog in my application, which the >> PyGTK reference says it can be used with PyGTK >= 2.4. >> > Therefore, i wonder whereas oldest OLPC has already a PyGTK >= 2.4 >> version. >> > So, is it all right ? >> > >> > Regards >> > > > ___ > 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
Re: [Sugar-devel] Should or should not i use PyGTK >= 2.4 widget ?
Thank you for your answers. But i am not sure i can do my task just with an ObjectChooser. And i need your advices for the strategy i should adopt : - I want my application to "save a graph" by writing the coordinates in a text file => i am conviced that for this tasks, i should use the folder data of the activity - i want my application to "load a graph" from a previously recorded graph - but i also want the users to share other graphs each others : more precisely, for users who don't have internet access (or for later systems restores, maybe after a crash, for example) to be able to import files from a usb key So, what is the best strategy in order to do these tasks and remain conform to Sugar best practices ? Regards 2011/5/27 Bert Freudenberg > Step 1: search wiki for ObjectChooser. > Step 2: find http://wiki.sugarlabs.org/go/Activity_Team/Object_Chooser > Step 3: there is no step 3 > > - Bert - > > On 27.05.2011, at 17:49, laurent bernabe wrote: > > > Thank you. > > > > I've been on Sugar Almanach page in order to find ObjectChooser class, > but i did not manage. > > (i've been here : http://wiki.sugarlabs.org/go/Development_Team/Almanac) > > Where should i look ? > > > > Regards > > > > 2011/5/27 Gonzalo Odiard > > If you use a FileChooserDialog, you don't have integration with the > Journal. > > You must use ObjectChooser. > > > > Gonzalo > > > > On Fri, May 27, 2011 at 11:56 AM, laurent bernabe < > laurent.bern...@gmail.com> wrote: > > Hello, > > > > i would like to use the FileChooserDialog in my application, which the > PyGTK reference says it can be used with PyGTK >= 2.4. > > Therefore, i wonder whereas oldest OLPC has already a PyGTK >= 2.4 > version. > > So, is it all right ? > > > > Regards > ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Terminal-32
On Sat, May 28, 2011 at 2:14 AM, Sugar Labs Activities wrote: > Activity Homepage: > http://activities.sugarlabs.org/addon/4043 > > Sugar Platform: > 0.82 - 0.92 > > Download Now: > http://activities.sugarlabs.org/downloads/file/27391/terminal-32.xo > > Release notes: > * New Icon and fix for activity.info deprecations > Bugs Fixed: SL#1492, SL#2172 Could we have a tar file release please? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Browse-122
On Sat, May 28, 2011 at 12:27 AM, Sugar Labs Activities wrote: > Activity Homepage: > http://activities.sugarlabs.org/addon/4024 > > Sugar Platform: > 0.82 - 0.92 > > Download Now: > http://activities.sugarlabs.org/downloads/file/27390/browse-122.xo > > Release notes: Any chance we could have release notes and a tar file? Peter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel