[Sugar-devel] A better participation
Regards. I've been developing a sugar activity for 5 months[1], now it's public and avaible for dowloads. I would like to involve with more participation into the community. I'm just a teenager student, but I can learn. What do you suggest me to do? How can I join to your community? [1]http://wiki.sugarlabs.org/go/Calendario -- GNU/Linux User # 480207 http://yadervblog.drupalgardens.com/ https://fedoraproject.org/wiki/User:Yaderv * ¡Desde abajo y a la izquierda!* ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] A better participation
On Wed, Feb 09, 2011 at 03:07:31AM -0600, Yader Velásquez wrote: I would like to involve with more participation into the community. I'm just a teenager student, but I can learn. What do you suggest me to do? Just what you did: introduce yourself, maybe write some code, let people know you're around, read sugar-devel mailing list. I'm sure others will have more detailed suggestions, but you have already done more than many. Welcome. Martin pgpMdiCnI8DCn.pgp Description: PGP signature ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Design] Control Panel - improve space usage
On 9 Feb 2011, at 04:34, James Cameron qu...@laptop.org wrote: On Tue, Feb 08, 2011 at 09:52:56PM -0500, Simon Schampijer wrote: The search currently does grey out icons that does not match the search criteria. In the IconView/ListStore the normal way to filter the view is by displaying only the icons that match the criteria. Would that be an acceptable change in behavior here - other ideas? No, not acceptable to me. Marking the icons insensitive is justified because the quantity and relative position of the icons never change. I don't like how the icons cannot be selected if they don't match a search. This is an overload of search results and button sensitivity. Marking the results some other way, such as by change to icon stroke brightness, is acceptable. I think the search is without purpose. It only searches icon text. One can't use it, for instance, to find color, radio or discard network history. I wish the search either did not exist, or searched also configuration items inside icons. +1 all good stuff, particularly search dimming icons rather than hiding so that lay out remains stable. FWIW Apple made a hidden dictionary of search terms for their preferences, so a Windows user (for example) could search for terms they were used to in their control panel, perhaps we could do the same? --Gary -- James Cameron http://quozl.linux.org.au/ ___ 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] [Design] Control Panel - improve space usage
On 02/08/2011 11:34 PM, James Cameron wrote: On Tue, Feb 08, 2011 at 09:52:56PM -0500, Simon Schampijer wrote: The search currently does grey out icons that does not match the search criteria. In the IconView/ListStore the normal way to filter the view is by displaying only the icons that match the criteria. Would that be an acceptable change in behavior here - other ideas? No, not acceptable to me. Marking the icons insensitive is justified because the quantity and relative position of the icons never change. Keeping the position is a benefit, yes. Reducing the number of items shown in a search is what we do as well in the Journal and in the activity list, so it would be consistent to that. And greying out the items is what we do in the neighborhood view. I don't like how the icons cannot be selected if they don't match a search. This is an overload of search results and button sensitivity. Marking the results some other way, such as by change to icon stroke brightness, is acceptable. I would make sure to match either the behavior in the neighborhood view or the Journal/activity view. I think the search is without purpose. It only searches icon text. One can't use it, for instance, to find color, radio or discard network history. I wish the search either did not exist, or searched also configuration items inside icons. It actually does that - you can specify key words for each control panel section which are matched in a search. Regards, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] A better participation
On 02/09/2011 05:57 AM, Martin Dengler wrote: On Wed, Feb 09, 2011 at 03:07:31AM -0600, Yader Velásquez wrote: I would like to involve with more participation into the community. I'm just a teenager student, but I can learn. What do you suggest me to do? Just what you did: introduce yourself, maybe write some code, let people know you're around, read sugar-devel mailing list. I'm sure others will have more detailed suggestions, but you have already done more than many. Welcome. Martin Hi Yader, I was about to say the same. You did well in introducing yourself. Besides using the mailing list a good chance to get in touch with other developers is using the #sugar channel on freenode. If you want feedback on particular areas of your code use the mailing list, for questions about the User Interface just add the [DESIGN] tag into the subject line to make it easier for the design people to filter for those questions. Welcome, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] A better participation
2011/2/9 Simon Schampijer si...@schampijer.de On 02/09/2011 05:57 AM, Martin Dengler wrote: On Wed, Feb 09, 2011 at 03:07:31AM -0600, Yader Velásquez wrote: I would like to involve with more participation into the community. I'm just a teenager student, but I can learn. What do you suggest me to do? Just what you did: introduce yourself, maybe write some code, let people know you're around, read sugar-devel mailing list. I'm sure others will have more detailed suggestions, but you have already done more than many. Welcome. Martin Hi Yader, I was about to say the same. You did well in introducing yourself. Besides using the mailing list a good chance to get in touch with other developers is using the #sugar channel on freenode. If you want feedback on particular areas of your code use the mailing list, for questions about the User Interface just add the [DESIGN] tag into the subject line to make it easier for the design people to filter for those questions. Welcome, Simon ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Welcome always good to have more help -- *Saludos Ing. Kevin Mauricio Benavides Castro Soporte Técnico | Proyecto XO *Gang member of the International Support * === * ** ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] Activity crashes when using libsugarize.so
If a newcomer to Sugar follows the instructions at http://wiki.sugarlabs.org/go/Running_Linux_Applications_Under_Sugar to use Albert Calahan's libsugarize.so from a precompiled binary, lots of funny things happen. X.org crashes with BadWindow at apparently random times -- some of the crashes can be tracked down to specific conditions, like opening the activity right after Sugar has started. The solution is to grab the src and recompile. That .so is likely old. I added a rough note in the wiki indicating that a build from src is needed, but the overall page needs a reorg. Posting here to feed google, increase awareness, and in case anyone has the time motivation to tidyup the wiki... cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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
Re: [Sugar-devel] Activity crashes when using libsugarize.so
Last year I experimented with sugarize and stored the files required in a local repo: copied from: http://www.catmoran.com/olpc/#sugxterm--- http://people.sugarlabs.org/Tgillard/sugarize/ where I have a repo of the required files: http://people.sugarlabs.org/Tgillard/sugarize/libsugarize.so Icons: http://people.sugarlabs.org/Tgillard/sugarize/plain.svg http://people.sugarlabs.org/Tgillard/sugarize/l.svg http://people.sugarlabs.org/Tgillard/sugarize/ff.svg Look at http://people.sugarlabs.org/Tgillard/sugarize/wiki-sugarize.txt which explains the processes and paths I found that seemed to work. Tom Gilliard satellit http://www.catmoran.com/olpc/#sugxterm--- Today: When the folks at sugerlabs.org asked if they could copy my cheat sheet to their wiki, I told them they could under a few conditions. One of those conditions was that they host the files on their own server, specifically because I wasn't planning to keep hosting them much longer. Unfortunately, it seems that they didn't keep up their end of the bargain. If I happen to find a copy of the original files (doubtful, I don't have the OLPCs anymore) I'll post the source here. If that happens, make copies because this domain is going away when the current registration expires! I copied these files on: 23-Feb-2010 (with permission) Martin Langhoff wrote: If a newcomer to Sugar follows the instructions at http://wiki.sugarlabs.org/go/Running_Linux_Applications_Under_Sugar to use Albert Calahan's libsugarize.so from a precompiled binary, lots of funny things happen. X.org crashes with BadWindow at apparently random times -- some of the crashes can be tracked down to specific conditions, like opening the activity right after Sugar has started. The solution is to grab the src and recompile. That .so is likely old. I added a rough note in the wiki indicating that a build from src is needed, but the overall page needs a reorg. Posting here to feed google, increase awareness, and in case anyone has the time motivation to tidyup the wiki... cheers, m ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] time for a design meeting?
There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. regards. -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] time for a design meeting?
Absolutely--Sunday should work for me. Let me know what time you'd like to meet... Christian On Wed, Feb 9, 2011 at 11:20 AM, Walter Bender walter.ben...@gmail.comwrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Activity crashes when using libsugarize.so
On Wed, Feb 9, 2011 at 11:08 AM, Thomas C Gilliard satel...@bendbroadband.com wrote: Last year I experimented with sugarize and stored the files required in a local repo: Right. Could you please change your notes to recommend that people... - download libsugarize.c and compile it on the target OS instead of downloading yours? - use the shell version of sugarize instead of the C version? The libsugarize.so issue is the main one. It probably only works reliably on the specific Fedora version it was built on. cheers, m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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
Re: [Sugar-devel] Activity crashes when using libsugarize.so
On Wed, Feb 9, 2011 at 11:45 AM, Jon Nettleton jon.nettle...@gmail.com wrote: Any reason not to package both of these into an rpm and provide it in the OLPC repos? Missing: a maintainer who knows and understands that it does, a maintainer that has time to do maintain it. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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
Re: [Sugar-devel] Activity crashes when using libsugarize.so
I just wrote this up on the wiki : http://wiki.sugarlabs.org/go/Category_talk:Live_USB#Sugarize_an_application_for_use_in_a_SoaS_USB I do not know where libsugarize.c is stored. Hopefully it will be made available to us. I modified the wget paths to reflect the present repo. (I have not tested it, yet) As I remember it worked for liveusb-creator on soas-v2 and v3 but made 2 icons on the sugar frame. Thus it was only partially successful. (Icon on F3 ring worked though.) Tom Gilliard satellit on IRC freenode #sugar Martin Langhoff wrote: On Wed, Feb 9, 2011 at 11:08 AM, Thomas C Gilliard satel...@bendbroadband.com wrote: Last year I experimented with sugarize and stored the files required in a local repo: Right. Could you please change your notes to recommend that people... - download libsugarize.c and compile it on the target OS instead of downloading yours? - use the shell version of sugarize instead of the C version? The libsugarize.so issue is the main one. It probably only works reliably on the specific Fedora version it was built on. cheers, m ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] time for a design meeting?
Hi Walter, On 9 Feb 2011, at 16:20, Walter Bender walter.ben...@gmail.com wrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. Yes I think I can make Sunday as well, let me know a good time for you. --Gary regards. -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] Activity crashes when using libsugarize.so
On Wed, Feb 9, 2011 at 12:27 PM, Thomas C Gilliard satel...@bendbroadband.com wrote: I do not know where libsugarize.c is stored. Just follow the link in my email. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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
Re: [Sugar-devel] Activity crashes when using libsugarize.so
On Wed, Feb 9, 2011 at 10:17 AM, Martin Langhoff martin.langh...@gmail.com wrote: The solution is to grab the src and recompile. That .so is likely old. Actually, not so much of a solution. Still getting some crashes. May be related to the program misbehaving. grr. m -- martin.langh...@gmail.com mar...@laptop.org -- Software Architect - OLPC - 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] [ANNOUNCE] 0.92 schedule update
Hi, today I met with Sascha to talk about our upcoming 0.92 release. Originally the schedule followed a 6 months cycle [1]. Since we did not work much on Features for this cycle we decided to only do a bugfix release, due the 18th of February. Since there are some bigger changes in the code (pep8 fixes) we still will call it 0.92. Bugfix release (point releases 0.92.1, 0.92.2...) are possible after that date. The following items that infect the release were discussed as well: * Don't hide Register menu item upon successful registration (currently in master d9d25a926a88a30cdbb76d3620e66b1daaab4fd0) Introduction: The reset registration to the school server has a long history [2][3]. The patch that landed in master is based on a request from a deployment (re-register after an XS crash), other use cases are to connect to another school server (different school). Another deployment recently requested to hide the item altogether because they're apparently doing the registration automatically in some way. To consider in the design discussion is as well the lack of feedback when registering [4]. Todo: We should describe the use cases and then find a good way of fixing this issue. This would be best handled by an email discussion streamlined in a Feature page [5]. * Dynamically set number of control panel columns (currently in master ecae03a35a505c4212271e415e618a1c5d271b3e) Introduction: The patch from Anish does address an long standing issue that 'Icons should be placed on the screen without having to scroll if there is enough space' described in [6]. It does not handle wrapping of the text if this exceeds the (2.5 * Cell size) which is reserved for an Icon. Anish bumped into an issue with that which is filed as [7]. Todo: 1. file a bug on the GTK bug tracker with m_anish's test case. 2. prepare a patch to replace the current code with gtk.IconView based code and see whether it's impacted as well. (if 2. works, we can merge it in 0.92. Otherwise we need to block on upstream for a fix (or get someone to fix it). * Journal Entry Sharing Introduction: That Feature is presented in [8]. Sascha requested some minor additions before merging into mainline. Todo: a) remove the metadata if there is not an associated file (e.g. file has been deleted), so any file that gets written with the same name in the future doesn't get associated with stale metadata. Files are often named Untitled.odt etc., so it might be a rather common case. b) delete metadata if it gets corrupted (don't delete the actual file) c) remove preview if mtime does not match (e.g. Peter saves his Write entry to a storage device, he opens it in OpenOffice on his mother's computer and his mother corrects some errors --- the preview will be outdated), this might not be a too big issue - input on the design team on this welcome. * Cpu and memory resource indicator to frame (currently in master e014bc401195a9b096e44d33d7f6135f7ae0c1c6) Introduction: This patch is controversial because of the design (e.g. [9]). The need to indicate system status is agreed on. It should go through another iteration before landing. Todo: a) for 0.92 revert the patch b) create a Feature page that does describe the idea etc (include all the links to previous discussions) c) and then get the discussion going * Design meeting We would like to reestablish the design meetings as those are important for more detailed design discussions. Stay tuned on hopefully soonish updates on this. Regards, Simon [1] 0.92 tentative schedule: http://wiki.sugarlabs.org/go/0.92/Roadmap#Schedule [2] Reset registration form school server (long term): http://dev.laptop.org/ticket/7765 [3] Reset registration form school server (0.84): http://dev.laptop.org/ticket/9725 [4] Feedback when register with school server: http://dev.laptop.org/ticket/10678 [5] Feature Policy: http://wiki.sugarlabs.org/go/Features/Policy [6] Control Panel - improve space usage: http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029827.html [7] Pygtk bug: http://www.mail-archive.com/pygtk@daa.com.au/msg19397.html [8] Journal Entry Sharing: http://wiki.sugarlabs.org/go/Features/Journal_Entry_Sharing [9] What should system mood really mean?: http://lists.sugarlabs.org/archive/sugar-devel/2010-September/026929.html ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] closing an activity immediately
If I wanted to stop an activity as soon as it was initiated, how would I do that? The code below hangs with a grey screen. Why would I want to do this? I am trying to understand how the sugar code base works. This seems like a good exercise for understanding how sugar activities start and stop. Yes, this would be a bad user experience. class NotTodayActivity( activity.Activity ): def __init__( self, handle ): activity.Activity.__init__( self, handle ) self._auto_shut_down = False if not self.should_this_activity_run_today( ): self._auto_shut_down = True logger.debug( goin' down ) self.close( ) return def write_file( self, file_path ): logger.debug( write_file... ) if self._auto_shut_down: return def should_this_activity_run_today( self ): #todo: details go here return False ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] time for a design meeting?
How about 12 EST (17UTC) in #sugar-meeting? -walter On Wed, Feb 9, 2011 at 12:38 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Walter, On 9 Feb 2011, at 16:20, Walter Bender walter.ben...@gmail.com wrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. Yes I think I can make Sunday as well, let me know a good time for you. --Gary regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- 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] time for a design meeting?
I think I can make that work, but is any earlier a possibility? Say around 11 EST? Christian On Wed, Feb 9, 2011 at 2:08 PM, Walter Bender walter.ben...@gmail.comwrote: How about 12 EST (17UTC) in #sugar-meeting? -walter On Wed, Feb 9, 2011 at 12:38 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Walter, On 9 Feb 2011, at 16:20, Walter Bender walter.ben...@gmail.com wrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. Yes I think I can make Sunday as well, let me know a good time for you. --Gary regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] refactoring of Homeview layouts to simplify Spiral option
Sorry about the resend but I think I may finally have git send-email properly configured and I didn't want Bernie to have to open my attachment from yesterday :) -walter ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] refactoring of Homeview layouts to simplify Spiral option
---
src/jarabe/desktop/favoriteslayout.py | 233 -
1 files changed, 145 insertions(+), 88 deletions(-)
diff --git a/src/jarabe/desktop/favoriteslayout.py
b/src/jarabe/desktop/favoriteslayout.py
index 360c147..22f729c 100644
--- a/src/jarabe/desktop/favoriteslayout.py
+++ b/src/jarabe/desktop/favoriteslayout.py
@@ -29,17 +29,10 @@ from sugar.graphics import style
from jarabe.model import bundleregistry
from jarabe.desktop.grid import Grid
-
_logger = logging.getLogger('FavoritesLayout')
_CELL_SIZE = 4
_BASE_SCALE = 1000
-_INTERMEDIATE_B = (style.STANDARD_ICON_SIZE + style.SMALL_ICON_SIZE) / 2
-_INTERMEDIATE_A = (style.STANDARD_ICON_SIZE + _INTERMEDIATE_B) / 2
-_INTERMEDIATE_C = (_INTERMEDIATE_B + style.SMALL_ICON_SIZE) / 2
-_ICON_SIZES = [style.MEDIUM_ICON_SIZE, style.STANDARD_ICON_SIZE,
- _INTERMEDIATE_A, _INTERMEDIATE_B, _INTERMEDIATE_C,
- style.SMALL_ICON_SIZE]
class FavoritesLayout(gobject.GObject, hippo.CanvasLayout):
@@ -178,7 +171,7 @@ class RandomLayout(FavoritesLayout):
def do_allocate(self, x, y, width, height, req_width, req_height,
origin_changed):
for child in self.box.get_layout_children():
-# We need to always get requests to not confuse hippo
+# We need to always get requests to not confuse hippo.
min_w_, child_width = child.get_width_request()
min_h_, child_height = child.get_height_request(child_width)
@@ -197,19 +190,24 @@ _MINIMUM_RADIUS = style.XLARGE_ICON_SIZE / 2 +
style.DEFAULT_SPACING + \
style.STANDARD_ICON_SIZE * 2
_MAXIMUM_RADIUS = (gtk.gdk.screen_height() - style.GRID_CELL_SIZE) / 2 - \
style.STANDARD_ICON_SIZE - style.DEFAULT_SPACING
-_ICON_SPACING_FACTORS = [1.5, 1.4, 1.3, 1.2, 1.1, 1.0]
-_SPIRAL_SPACING_FACTORS = [1.5, 1.5, 1.5, 1.4, 1.3, 1.2]
-_MIMIMUM_RADIUS_ENCROACHMENT = 0.75
-_INITIAL_ANGLE = math.pi
+_INTERMEDIATE_C = (style.STANDARD_ICON_SIZE + style.SMALL_ICON_SIZE) / 2
+_INTERMEDIATE_A = (style.STANDARD_ICON_SIZE * 2 + _INTERMEDIATE_C) / 3
+_INTERMEDIATE_E = (_INTERMEDIATE_C + style.SMALL_ICON_SIZE * 2) / 3
+_INTERMEDIATE_B = (_INTERMEDIATE_A + _INTERMEDIATE_C) / 2
+_INTERMEDIATE_D = (_INTERMEDIATE_C + _INTERMEDIATE_E) / 2
+_ICON_SIZES = [style.MEDIUM_ICON_SIZE, style.STANDARD_ICON_SIZE,
+ _INTERMEDIATE_A, _INTERMEDIATE_B, _INTERMEDIATE_C,
+ _INTERMEDIATE_D, _INTERMEDIATE_E, style.SMALL_ICON_SIZE]
+_ICON_SPACING_FACTORS = [1.5, 1.4, 1.3, 1.2, 1.15, 1.1, 1.05, 1.0]
-class RingLayout(FavoritesLayout):
-Lay out icons in a ring or spiral around the XO man.
+class BasicRingLayout(FavoritesLayout):
+Lay out icons in a ring around the XO man.
-__gtype_name__ = 'RingLayout'
+__gtype_name__ = 'BasicRingLayout'
icon_name = 'view-radial'
Name of icon used in home view dropdown palette.
-key = 'ring-layout'
+key = 'basic-ring-layout'
String used in profile to represent this view.
# TRANS: label for the ring layout in the favorites view
palette_name = _('Ring')
@@ -218,7 +216,6 @@ class RingLayout(FavoritesLayout):
def __init__(self):
FavoritesLayout.__init__(self)
self._locked_children = {}
-self._spiral_mode = False
def append(self, icon, locked=False):
FavoritesLayout.append(self, icon, locked)
@@ -239,8 +236,8 @@ class RingLayout(FavoritesLayout):
self._locked_children[child] = (x, y)
def _calculate_radius_and_icon_size(self, children_count):
- Adjust the ring or spiral radius and icon size as needed.
-self._spiral_mode = False
+ Adjust the ring radius and icon size as needed.
+# Begin by increasing the radius.
distance = style.MEDIUM_ICON_SIZE + style.DEFAULT_SPACING * \
_ICON_SPACING_FACTORS[_ICON_SIZES.index(style.MEDIUM_ICON_SIZE)]
radius = max(children_count * distance / (2 * math.pi),
@@ -248,13 +245,118 @@ class RingLayout(FavoritesLayout):
if radius _MAXIMUM_RADIUS:
return radius, style.MEDIUM_ICON_SIZE
-distance = style.STANDARD_ICON_SIZE + style.DEFAULT_SPACING * \
-_ICON_SPACING_FACTORS[_ICON_SIZES.index(style.STANDARD_ICON_SIZE)]
+# Continue by shrinking the icon size to STANDARD_ICON_SIZE.
+radius = _MAXIMUM_RADIUS
+distance = radius * (2 * math.pi) / children_count
+icon_size = int(distance - style.DEFAULT_SPACING * \
+_ICON_SPACING_FACTORS[_ICON_SIZES.index(style.STANDARD_ICON_SIZE)])
+if icon_size = style.STANDARD_ICON_SIZE:
+return radius, icon_size
+
+# Continue by shrinking the icon size to SMALL_ICON_SIZE.
+icon_size = max(int(distance - style.DEFAULT_SPACING * \
+_ICON_SPACING_FACTORS[_ICON_SIZES.index(
+style.SMALL_ICON_SIZE)]), style.SMALL_ICON_SIZE)
+return radius, icon_size
+
+
Re: [Sugar-devel] time for a design meeting?
On Wed, Feb 9, 2011 at 2:32 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I think I can make that work, but is any earlier a possibility? Say around 11 EST? Works for me. Any time after about 10am should be good for me as long as my travel connections work at all as scheduled. -walter Christian On Wed, Feb 9, 2011 at 2:08 PM, Walter Bender walter.ben...@gmail.com wrote: How about 12 EST (17UTC) in #sugar-meeting? -walter On Wed, Feb 9, 2011 at 12:38 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Walter, On 9 Feb 2011, at 16:20, Walter Bender walter.ben...@gmail.com wrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. Yes I think I can make Sunday as well, let me know a good time for you. --Gary regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ -- 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.92 schedule update
Presumably there will be a chance to introduce some bug fixes, new features in Fructose activities as well for this release? -walter On Wed, Feb 9, 2011 at 1:35 PM, Simon Schampijer si...@schampijer.de wrote: Hi, today I met with Sascha to talk about our upcoming 0.92 release. Originally the schedule followed a 6 months cycle [1]. Since we did not work much on Features for this cycle we decided to only do a bugfix release, due the 18th of February. Since there are some bigger changes in the code (pep8 fixes) we still will call it 0.92. Bugfix release (point releases 0.92.1, 0.92.2...) are possible after that date. The following items that infect the release were discussed as well: * Don't hide Register menu item upon successful registration (currently in master d9d25a926a88a30cdbb76d3620e66b1daaab4fd0) Introduction: The reset registration to the school server has a long history [2][3]. The patch that landed in master is based on a request from a deployment (re-register after an XS crash), other use cases are to connect to another school server (different school). Another deployment recently requested to hide the item altogether because they're apparently doing the registration automatically in some way. To consider in the design discussion is as well the lack of feedback when registering [4]. Todo: We should describe the use cases and then find a good way of fixing this issue. This would be best handled by an email discussion streamlined in a Feature page [5]. * Dynamically set number of control panel columns (currently in master ecae03a35a505c4212271e415e618a1c5d271b3e) Introduction: The patch from Anish does address an long standing issue that 'Icons should be placed on the screen without having to scroll if there is enough space' described in [6]. It does not handle wrapping of the text if this exceeds the (2.5 * Cell size) which is reserved for an Icon. Anish bumped into an issue with that which is filed as [7]. Todo: 1. file a bug on the GTK bug tracker with m_anish's test case. 2. prepare a patch to replace the current code with gtk.IconView based code and see whether it's impacted as well. (if 2. works, we can merge it in 0.92. Otherwise we need to block on upstream for a fix (or get someone to fix it). * Journal Entry Sharing Introduction: That Feature is presented in [8]. Sascha requested some minor additions before merging into mainline. Todo: a) remove the metadata if there is not an associated file (e.g. file has been deleted), so any file that gets written with the same name in the future doesn't get associated with stale metadata. Files are often named Untitled.odt etc., so it might be a rather common case. b) delete metadata if it gets corrupted (don't delete the actual file) c) remove preview if mtime does not match (e.g. Peter saves his Write entry to a storage device, he opens it in OpenOffice on his mother's computer and his mother corrects some errors --- the preview will be outdated), this might not be a too big issue - input on the design team on this welcome. * Cpu and memory resource indicator to frame (currently in master e014bc401195a9b096e44d33d7f6135f7ae0c1c6) Introduction: This patch is controversial because of the design (e.g. [9]). The need to indicate system status is agreed on. It should go through another iteration before landing. Todo: a) for 0.92 revert the patch b) create a Feature page that does describe the idea etc (include all the links to previous discussions) c) and then get the discussion going * Design meeting We would like to reestablish the design meetings as those are important for more detailed design discussions. Stay tuned on hopefully soonish updates on this. Regards, Simon [1] 0.92 tentative schedule: http://wiki.sugarlabs.org/go/0.92/Roadmap#Schedule [2] Reset registration form school server (long term): http://dev.laptop.org/ticket/7765 [3] Reset registration form school server (0.84): http://dev.laptop.org/ticket/9725 [4] Feedback when register with school server: http://dev.laptop.org/ticket/10678 [5] Feature Policy: http://wiki.sugarlabs.org/go/Features/Policy [6] Control Panel - improve space usage: http://lists.sugarlabs.org/archive/sugar-devel/2011-February/029827.html [7] Pygtk bug: http://www.mail-archive.com/pygtk@daa.com.au/msg19397.html [8] Journal Entry Sharing: http://wiki.sugarlabs.org/go/Features/Journal_Entry_Sharing [9] What should system mood really mean?: http://lists.sugarlabs.org/archive/sugar-devel/2010-September/026929.html ___ 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] closing an activity immediately
Excerpts from Erik Blankinship's message of Wed Feb 09 19:55:12 +0100 2011: class NotTodayActivity( activity.Activity ): def __init__( self, handle ): activity.Activity.__init__( self, handle ) self._auto_shut_down = False if not self.should_this_activity_run_today( ): self._auto_shut_down = True logger.debug( goin' down ) self.close( ) return There's a whole lot of stuff being run after Activity.__init__() before the activity is actually started (take a look at the source [1]). I haven't looked into it closely, but I suspect that your early self.close() hangs because the widgets are not set up yet. Sascha [1] http://git.sugarlabs.org/sugar-toolkit/mainline/blobs/master/src/sugar/activity/activity.py -- 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] [PATCH sugar] Do not allow empty default nicks
The problem might occure if long user name not empty but the first field
if empty.
---
src/jarabe/intro/window.py |9 -
1 files changed, 4 insertions(+), 5 deletions(-)
diff --git a/src/jarabe/intro/window.py b/src/jarabe/intro/window.py
index 3b34d23..143440d 100644
--- a/src/jarabe/intro/window.py
+++ b/src/jarabe/intro/window.py
@@ -168,12 +168,11 @@ class _IntroBox(hippo.CanvasBox):
if default_nick == 'system':
pwd_entry = pwd.getpwuid(os.getuid())
if pwd_entry.pw_gecos:
-nick = pwd_entry.pw_gecos.split(',')[0]
-self._name_page.set_name(nick)
+default_nick = pwd_entry.pw_gecos.split(',')[0] or \
+pwd_entry.pw_name
else:
-self._name_page.set_name(pwd_entry.pw_name)
-else:
-self._name_page.set_name(default_nick)
+default_nick = pwd_entry.pw_name
+self._name_page.set_name(default_nick)
self._setup_page()
--
1.7.3.4
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] A better participation
On Wed, Feb 09, 2011 at 03:07:31AM -0600, Yader Vel?squez wrote: How can I join to your community? You _have_ joined the community. Welcome. If there's any place you think you are not involved, and would like to be, let us know. -- 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] time for a design meeting?
On 9 Feb 2011, at 19:55, Walter Bender walter.ben...@gmail.com wrote: On Wed, Feb 9, 2011 at 2:32 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I think I can make that work, but is any earlier a possibility? Say around 11 EST? Works for me. Any time after about 10am should be good for me as long as my travel connections work at all as scheduled. Sounds good, catch you Sunday. --Gary -walter Christian On Wed, Feb 9, 2011 at 2:08 PM, Walter Bender walter.ben...@gmail.com wrote: How about 12 EST (17UTC) in #sugar-meeting? -walter On Wed, Feb 9, 2011 at 12:38 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Walter, On 9 Feb 2011, at 16:20, Walter Bender walter.ben...@gmail.com wrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. Yes I think I can make Sunday as well, let me know a good time for you. --Gary regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ -- 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] time for a design meeting?
Great, talk to you Sunday at 11 EST! Christian On Wed, Feb 9, 2011 at 9:55 PM, Gary Martin garycmar...@googlemail.comwrote: On 9 Feb 2011, at 19:55, Walter Bender walter.ben...@gmail.com wrote: On Wed, Feb 9, 2011 at 2:32 PM, Christian Marc Schmidt christianm...@gmail.com wrote: I think I can make that work, but is any earlier a possibility? Say around 11 EST? Works for me. Any time after about 10am should be good for me as long as my travel connections work at all as scheduled. Sounds good, catch you Sunday. --Gary -walter Christian On Wed, Feb 9, 2011 at 2:08 PM, Walter Bender walter.ben...@gmail.com wrote: How about 12 EST (17UTC) in #sugar-meeting? -walter On Wed, Feb 9, 2011 at 12:38 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Walter, On 9 Feb 2011, at 16:20, Walter Bender walter.ben...@gmail.com wrote: There are a few design roadblocks in the race to 0.92 that could use some input from the design team. Any chance we could have a meeting some time soon? I could probably get on line from Lima on Sunday some time if that works. Yes I think I can make Sunday as well, let me know a good time for you. --Gary regards. -walter -- Walter Bender Sugar Labs http://www.sugarlabs.org -- Walter Bender Sugar Labs http://www.sugarlabs.org -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ -- Walter Bender Sugar Labs http://www.sugarlabs.org -- anyth...@christianmarcschmidt.com 917/ 575 0013 http://www.christianmarcschmidt.com http://www.linkedin.com/in/christianmarcschmidt http://twitter.com/cms_ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] closing an activity immediately
On Feb 9, 2011, at 7:55 PM, Erik Blankinship wrote: If I wanted to stop an activity as soon as it was initiated, how would I do that? The code below hangs with a grey screen. Why would I want to do this? I am trying to understand how the sugar code base works. This seems like a good exercise for understanding how sugar activities start and stop. Actually this would be a great feature in my opinion. To me it happened often enough that an activity got started accidentally while dragging and dropping images from the journal to a USB Stick, for example. Being able to stop it immediately would be a great user experience. FWIW, the Mac offers this behavior as well. Applications can be Force Quit during start up. Yes, this would be a bad user experience. class NotTodayActivity( activity.Activity ): def __init__( self, handle ): activity.Activity.__init__( self, handle ) self._auto_shut_down = False if not self.should_this_activity_run_today( ): self._auto_shut_down = True logger.debug( goin' down ) self.close( ) return def write_file( self, file_path ): logger.debug( write_file... ) if self._auto_shut_down: return def should_this_activity_run_today( self ): #todo: details go here return False ___ 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] closing an activity immediately
On Thu, Feb 10, 2011 at 08:14:08AM +0100, tom.staub...@fhtw-berlin.de wrote: Actually this would be a great feature in my opinion. To me it happened often enough that an activity got started accidentally while dragging and dropping images from the journal to a USB Stick, for example. Being able to stop it immediately would be a great user experience. I agree. ESC during the startup animation. -- James Cameron http://quozl.linux.org.au/ ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
