Re: [Sugar-devel] [ASLO] Release Read ETexts-19
On Sun, Mar 14, 2010 at 08:19:40PM -0500, James Simmons wrote: Aleksey, Dragging the entry to the Journal icon works beautifully, but believe it or not I was unaware it existed. I've been using Sugar since the first G1G1 and never knew about it. I did manage to find the menu, though. It's visible when you open the Journal contents, as shown in the attached screenshot from F10. I agree drag and drop is better than the menu, now that I know about it. Maybe a kid could figure it out, but I couldn't. I'm not arguing what is the preferable method to copy objects to/from journal, I just can't get what you mean by menu option to copy usb files to the Journal. I just recheck source code history and didn't find any mention of such code. There is only Send to submenu to copy entry via network. James Simmons I had to test these on SoaS and I discovered that the menu options to copy something from a USB thumb drive or SD card to the Journal are missing and apparently have been missing from some time. The only way to copy something from USB to the thumb drive now is to use the clipboard. but afaik we didn't have such menu option except Copy object could be dragged to journal or activated in place I really, REALLY don't like this. When I copy an Activity or a book from thumb drive to Journal using this method I don't get the file name as the Journal entry title. Instead, I just get a description based on the MIME type. This is really, really bad. Maybe the original fine name wasn't the best possible title for a Journal entry but at least you had some idea of what the Journal entry was and you could easily change it. Now every book is just text clipping and every Activity is Sugar Activity bundle, plus getting these lousy results is more work than just doing a straight copy to the Journal. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [DESIGN] Width of the TitleEntry widget
Hi James, On 15 Mar 2010, at 10:25, James Cameron wrote: Was not able to see the HIG grid constants defined anywhere in sugar-toolkit or sugar-base. Can you advise, Tomeu? Not sure if it's what you're after, but I was using this to set the size of a secondary toolbar (height) at one point: from sugar.graphics import style self.set_size_request(-1, style.GRID_CELL_SIZE) Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ANNOUNCE] 0.88 Hard Code Freeze in place
Dear Sugar Community, we are entering Hard Code Freeze with the 15th of march [1]! This means [2]: No source code changes can be made without approval from the release-team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two members of the team. The Hard Code Freeze will end at the 29th of march and will lead us directly to the Final 0.88 release at the 31th of march. Translation and documentation can continue during the Hard Code Freeze. In behalf of the sugar community, Your Release Team [1] Schedule: http://wiki.sugarlabs.org/go/0.88/Roadmap [2] http://wiki.sugarlabs.org/go/Development_Team/Release#Hard_code_freeze ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ANNOUNCE] 0.88 Hard Code Freeze in place
I assume that this is Sucrose only, as Fructose is in limbo? -walter On Mon, Mar 15, 2010 at 10:16 AM, Simon Schampijer si...@schampijer.de wrote: Dear Sugar Community, we are entering Hard Code Freeze with the 15th of march [1]! This means [2]: No source code changes can be made without approval from the release-team. Only critical fixes will be considered. To request approval send mail to sugar-devel@lists.sugarlabs.org, including the patch and a detailed description of the changes, the benefits and the risks. Approval will have to be granted by two members of the team. The Hard Code Freeze will end at the 29th of march and will lead us directly to the Final 0.88 release at the 31th of march. Translation and documentation can continue during the Hard Code Freeze. In behalf of the sugar community, Your Release Team [1] Schedule: http://wiki.sugarlabs.org/go/0.88/Roadmap [2] http://wiki.sugarlabs.org/go/Development_Team/Release#Hard_code_freeze ___ 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] [ANNOUNCE] 0.88 Hard Code Freeze in place
On 03/15/2010 03:46 PM, Walter Bender wrote: I assume that this is Sucrose only, as Fructose is in limbo? -walter Ideally, you should be in a similar situation in your development cycle at this moment in time. Doing stabilizing work and preparing for a final release. Of course Sugar activities are not restricted to the Sucrose development cycle, but what would be Sugar without activities...? Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Read ETexts-19
Aleksey, I tried to attach a screenshot of just what this menu looks like in .82. I can see it in gmail but maybe it was stripped from the email going to the mailing list. I'll describe how to find this menu in .82. First, you have to open the Journal entry so you see the screen that has the metadata, screen shot, etc. It is not available through the normal hover menu in the Journal listing. If you move your mouse pointer over the Copy icon in this view a menu will drop down and will show Copy, Copy To Journal, plus other options for copying to the SD card, etc. It's a pretty well hidden menu but you can find it. I probably found it because I had to go into the Journal entry screen to find another useful menu, Start With. I have a lot of experience with this menu because I constantly used it for opening Read Etexts. If you just clicked on the Journal entry for a Zip file containing text it could open in ETtoys or View Slides by mistake. The Copy menu item and icon are the least useful methods of copying something to and from the Journal but they are the only ones that are really visible. I like the change to the hover menu for the Journal entry list that added Start With and its submenu listing all the Activities you could use to Resume that Journal entry. I'd suggest something similar for Copy, with Copy to Clipboard being the last option in the list. Another thing you could do is make drag and drop easier to discover by making the Journal a bit more like Midnight Commander. Normally, with no USB or SD inserted, the Journal looks like it does now. Insert either and an icon appears at the bottom of the screen, just like it does now. Click on that icon and you get an mc-like look, with the Journal entries in a left pane and the USB entries in a right pane. The USB entries would show that they are organized into subdirectories. No attempt would be made to make them look like Journal entries. You could do copies by dragging from one pane to the other, which would be more natural than dragging to an icon at the bottom of the screen (but that would still work). James Simmons I'm not arguing what is the preferable method to copy objects to/from journal, I just can't get what you mean by menu option to copy usb files to the Journal. I just recheck source code history and didn't find any mention of such code. There is only Send to submenu to copy entry via network. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Read ETexts-19
On Mon, Mar 15, 2010 at 10:20:49AM -0500, James Simmons wrote: Aleksey, I tried to attach a screenshot of just what this menu looks like in .82. I can see it in gmail but maybe it was stripped from the email going to the mailing list. I'll describe how to find this menu in .82. First, you have to open the Journal entry so you see the screen that has the metadata, screen shot, etc. It is not available through the normal hover menu in the Journal listing. If you move your mouse pointer over the Copy icon in this view a menu will drop down and will show Copy, Copy To Journal, plus other options for copying to the SD card, etc. It's a pretty well hidden menu but you can find it. I probably found it because I had to go into the Journal entry screen to find another useful menu, Start With. I have a lot of experience with this menu because I constantly used it for opening Read Etexts. If you just clicked on the Journal entry for a Zip file containing text it could open in ETtoys or View Slides by mistake. Got it, I guess the main reason to have Copy to Journal only there was keep sugar all time surprising :) I think it could be considered as regression and pushed to 0.88 http://bugs.sugarlabs.org/ticket/1831 The Copy menu item and icon are the least useful methods of copying something to and from the Journal but they are the only ones that are really visible. I like the change to the hover menu for the Journal entry list that added Start With and its submenu listing all the Activities you could use to Resume that Journal entry. I'd suggest something similar for Copy, with Copy to Clipboard being the last option in the list. http://bugs.sugarlabs.org/ticket/1832 from coding POV it should be trivial, the question is only designers' view Another thing you could do is make drag and drop easier to discover by making the Journal a bit more like Midnight Commander. Normally, with no USB or SD inserted, the Journal looks like it does now. Insert either and an icon appears at the bottom of the screen, just like it does now. Click on that icon and you get an mc-like look, with the Journal entries in a left pane and the USB entries in a right pane. The USB entries would show that they are organized into subdirectories. No attempt would be made to make them look like Journal entries. You could do copies by dragging from one pane to the other, which would be more natural than dragging to an icon at the bottom of the screen (but that would still work). This how-journal-should-look-like is pretty arguable question, in my mind the right answer is having several journals(journal like) activities that will cover all possible use cases. I'm working on Library-2 which should be regular Journal (in browsing sense) with sharing features and several views like list/thumbs/full. Would be useful if people will start coding their own variants and we even shouldn't choose right one for new default (in core) Journal, people will use more appropriate for their workflows. James Simmons I'm not arguing what is the preferable method to copy objects to/from journal, I just can't get what you mean by menu option to copy usb files to the Journal. I just recheck source code history and didn't find any mention of such code. There is only Send to submenu to copy entry via network. -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Read ETexts-19
Aleksey, I find the idea of multiple Journal Activities appealing, and I think I could write Sugar Commander myself, except that it would only work for copying from the external media into the Journal, not from the Journal to the media. James Simmons Would be useful if people will start coding their own variants and we even shouldn't choose right one for new default (in core) Journal, people will use more appropriate for their workflows. James Simmons ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Read ETexts-19
I find the idea of multiple Journal Activities appealing, and I think I could write Sugar Commander myself, except that it would only work for copying from the external media into the Journal, not from the Journal to the media. I like this thread. This is a consistent demand from teachers in Uruguay. Some time ago I created LeerPendrive [0], which allows the user to browse the usb drive with a directory structure and copy the files to the clipboard. (From the clipboard they can easily copy them to the journal.) In spite of being very simple, it has been very used. It is a pity that because it is just an activity you can't copy both ways. I like the idea of integrating something like this in the sugar core so you can do exactly that. Regards, Gabriel [0] http://drupal.ceibaljam.org/sites/default/files/LeerPendrive-1.xo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Hard code freeze exception request
Hi all,
http://bugs.sugarlabs.org/ticket/1831
Revert copy to Journal palette item in journal details view.
Could be considered as regression since 0.82 has this feature.
--
Aleksey
From 36574b3e86069f86595e27c54f74e0fd439c4c33 Mon Sep 17 00:00:00 2001
From: Aleksey Lim alsr...@member.fsf.org
Date: Mon, 15 Mar 2010 18:33:24 +
Subject: Revert copy to Journal palette item in journal details view #1831
diff --git a/src/jarabe/journal/journaltoolbox.py
b/src/jarabe/journal/journaltoolbox.py
index fe05657..54be2f8 100644
--- a/src/jarabe/journal/journaltoolbox.py
+++ b/src/jarabe/journal/journaltoolbox.py
@@ -37,6 +37,7 @@ from sugar.graphics.xocolor import XoColor
from sugar.graphics import iconentry
from sugar.graphics import style
from sugar import mime
+from sugar import profile
from jarabe.model import bundleregistry
from jarabe.journal import misc
@@ -396,8 +397,8 @@ class EntryToolbar(gtk.Toolbar):
def _resume_menu_item_activate_cb(self, menu_item, service_name):
misc.resume(self._metadata, service_name)
-def _copy_menu_item_activate_cb(self, menu_item, mount):
-model.copy(self._metadata, mount.get_root().get_path())
+def _copy_menu_item_activate_cb(self, menu_item, mount_point):
+model.copy(self._metadata, mount_point)
def _refresh_copy_palette(self):
palette = self._copy.get_palette()
@@ -406,6 +407,15 @@ class EntryToolbar(gtk.Toolbar):
palette.menu.remove(menu_item)
menu_item.destroy()
+journal_item = MenuItem(_('Journal'))
+journal_item.set_image(Icon(
+icon_name='activity-journal',
+xo_color=profile.get_color(),
+icon_size=gtk.ICON_SIZE_MENU))
+journal_item.connect('activate', self._copy_menu_item_activate_cb, '/')
+journal_item.show()
+palette.menu.append(journal_item)
+
volume_monitor = gio.volume_monitor_get()
for mount in volume_monitor.get_mounts():
if self._metadata['mountpoint'] == mount.get_root().get_path():
@@ -418,7 +428,7 @@ class EntryToolbar(gtk.Toolbar):
menu_item.connect('activate',
self._copy_menu_item_activate_cb,
- mount)
+ mount.get_root().get_path())
palette.menu.append(menu_item)
menu_item.show()
--
1.6.5.3
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [ASLO] Release Read ETexts-19
On Mon, Mar 15, 2010 at 02:09:18PM -0500, James Simmons wrote: Gabriel, Actually it would be just as easy to copy the files from USB directly to the Journal and you could use the file name as the Journal entry title. All of my Activities read and write to the Journal. It's easy. If I was going to do Sugar Commander I could copy code from these Activities and hack something together. Aleksey's Library Activity was pretty nice when I tried it. I don't think it addressed USB copying at all but it did give you more options for organizing Journal content. That's another thing that special Journal Activities can do. Ideally such Activities could work with .82 or greater and support both old and new style toolbars, as my three Activities now do. In case of toolbars mess, for last Speak, CartookBuilder and Flipsticks I used code ripped from sugar-toolkit[1] so activities don't contain any ifs and look the same on all sugars. For Library-2, I'm planing to switch to Toolkit[2] service i.e. pure Vala/C based library w/o using sugar-toolkit at all. Toolkit will support 0.82+ and all last sugar-toolkit features i.e. it lets using full functional UI in not only python activities like GCompris. [1] http://git.sugarlabs.org/projects/toolkit/repos/mainline/trees/deprecated [2] http://git.sugarlabs.org/projects/toolkit/repos/mainline/trees/master James Simmons On Mon, Mar 15, 2010 at 12:58 PM, Gabriel Eirea gei...@gmail.com wrote: I find the idea of multiple Journal Activities appealing, and I think I could write Sugar Commander myself, except that it would only work for copying from the external media into the Journal, not from the Journal to the media. I like this thread. This is a consistent demand from teachers in Uruguay. Some time ago I created LeerPendrive [0], which allows the user to browse the usb drive with a directory structure and copy the files to the clipboard. (From the clipboard they can easily copy them to the journal.) In spite of being very simple, it has been very used. It is a pity that because it is just an activity you can't copy both ways. I like the idea of integrating something like this in the sugar core so you can do exactly that. Regards, Gabriel [0] http://drupal.ceibaljam.org/sites/default/files/LeerPendrive-1.xo -- Aleksey ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [IAEP] Children want Sugar 0.84, for the wrong reason
On Mon, 2010-03-15 at 10:46 -0500, Martin Langhoff wrote: On Sun, Mar 14, 2010 at 1:17 AM, Bernie Innocenti ber...@codewiz.org wrote: Me too, but it's not as bad as it seems: the techies use a simple shell script to backup and restore the journal (and scratch data) across So no XS in place? The repair lab is not nearby any of the schools. Downstreams that go to deployment (OLPC!) want to wait until a release is reasonably well tested and stabilised. We have a chicken-and-egg problem: deployments have to participate in testing (and development), otherwise no bugs will ever be fixed. Stability is a classic justification for longer release cycles The thing is: stabilisation takes time. These users are not programmers, nor geeks. They are not the Fedora hard-core gimme the latest even if broken. They are teachers and children in a school. I don't mess with my editor or my version control system often. emacs updates have messed up my life, so I don't do them in the middle of a project. Similarly, teachers won't want frequent updates, or updates that are broken (in Sugar core, or in activity compatibility!). Letting volunteer children and teachers test the software has been incredibly productive. I wish I could have started one month earlier, so there would have been enough time to fix most problems before schools reopened in LatAm. A few trainers who were asked to test new builds much explanation complained for the annoyances without providing enough information for a bug report. Considering that most of them were exposed to computers for the first time in their lives just a couple of months ago, it's no wonder they were unable to distinguish between hardware and software problems. I filed a few real bugs last week, and this week I'll spend a few full days side by side with the trainers to see what issues are still bothering them. That is only true if the dev team only cares about the hardcore geeks that want the latest and greatest. If the dev team cares about end users, then it's not abandonware. Which dev team? There are many: Sugar Labs, OLPC, Fedora, and all the other upstream projects we depend upon. Now I have a problem with udev which is unlikely to be fixed by upstream. The maintainer *does* care about end users, but he'd rather spend his time supporting the current user base than the legacy Fedora 11 which is soon going end-of-life. Same goes for the activities developers: maintaining compatibility with 3-4 releases of Sugar is prohibitive. Backporting bugfixes is also very expensive in terms of time and not something that volunteers are likely to do spontaneously. OLPC allocated developers to maintain the Sugar 0.84 and related activities, but it would save time if we could stay closer the latest Fedora and the latest Sugar, at least at release time. However, the most efficient use of our scarce resources would be to reduce version diversity across downstream distributors in order to share the burden of maintaining all them. Agreed. One path is to release less often. Or to mark certain releases LTS. I've been suffering with RHEL for a while and I'm sure Ubuntu LTS has the same problem: no support for new hardware, ancient versions of software which don't interact well with the rest of the world... I think it would work well if one could freeze the whole universe at the time of the LTS release. Yep. You could make it a major / minor pair. So you only have one LTS per year. Developer releases can happen more often. One year of slack between development and user release would be ideal. By LTS, I thought you meant 5 years :-) -- // 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] [IAEP] Children want Sugar 0.84, for the wrong reason
On Mon, Mar 15, 2010 at 3:41 PM, Bernie Innocenti ber...@codewiz.org wrote: So no XS in place? The repair lab is not nearby any of the schools. Ah - ok. Thanks for clarifying. Downstreams that go to deployment (OLPC!) want to wait until a release is reasonably well tested and stabilised. We have a chicken-and-egg problem: deployments have to participate in testing (and development), otherwise no bugs will ever be fixed. Agreed. You can do what you are doing (run a school on newish sw, get a tight feedback bugfix loop) when someone like you is there. Letting volunteer children and teachers test the software has been incredibly productive. Yes -- but we gotta remember that it's productive (specially for Sugar) because you are there. You can turn their frustration into valuable info (and bugfixes). Without you, it's just frustration. I wish I could have started one month earlier, so there would have been enough time to fix most problems before schools reopened in LatAm. That's a good idea -- try to work in a school with latest Sugar late in the previous school year, to incorporate stuff for the wider deployment in the over-summer-holidas upgrade. (And actually we have a late-starting deployment in La Rioja, which is on-time to take advantage of that work.) I filed a few real bugs last week, and this week I'll spend a few full days side by side with the trainers to see what issues are still bothering them. That's fantastic. Which dev team? That's truly a good question. I'll say the teams closest to the deployments. Distant upstreams (kernel, udev, Fedora) don't care directly about our end users. OLPC/SLers are passionate about children learning. Yep. You could make it a major / minor pair. So you only have one LTS per year. One year of slack between development and user release would be ideal. Yep - that and combine it with working with a few schools on recent releases, with a developer on-site -- like you, Simon and others are doing. In practice, it probably means we'll be answering questions about any release for about 1.5 to 2 years after the release date. By LTS, I thought you meant 5 years :-) N. I'm not so crazy. But we have to fit in the school's 1-year-cycle, have time to stabilise, etc. Small deployments have more flexibility, and when someone like you is literally on site you can go wild... (take advantage of that!) but for the thousands of other schools an LTS cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- School Server Architect - ask interesting questions - don't get distracted with shiny stuff - working code first - http://wiki.laptop.org/go/User:Martinlanghoff ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Silly 0.88 question
Apologies for the daft question, I was about to build new .xo bundles for some of the activities I'm involved with, even though I don't necessarily have much else to include other than updated translations (big thank you to all translators!). Do I, with my 'activity developer' hat on, sit around until 0.88 officially goes golden master? When should I take time out to do a fresh activity build for including new translations? Is there a 'translation freeze' so I know when to hang about for? Last chance translation saloon and all that... Regards, --Gary ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [ASLO] Release Plot-1
Activity Homepage: http://activities.sugarlabs.org/addon/4287 Sugar Platform: 0.82 - 0.88 Download Now: http://activities.sugarlabs.org/downloads/file/26833/plot-1.xo Release notes: Plot equations with the Plot activity. Enter the equation in the equation bar, modify the x-axis limits, press Go and see it plotted below. Sugar Labs Activities http://activities.sugarlabs.org ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
