[Sugar-devel] [PATCH sugar-artwork] Enforce white background on intro screen
As part of the hippocanvas removal process, we can move intro window theming details into the theme. The intro window has a white background for itself and its children. --- gtk/theme/gtkrc.em |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/gtk/theme/gtkrc.em b/gtk/theme/gtkrc.em index 7f180a7..0811548 100644 --- a/gtk/theme/gtkrc.em +++ b/gtk/theme/gtkrc.em @@ -770,6 +770,8 @@ widget_class *SugarAlert* style black-bg-child widget_class *SugarSectionView style white-bg widget_class *SugarSectionView* style white-bg-child +widget_class *SugarIntroWindow style white-bg +widget_class *SugarIntroWindow* style white-bg-child # The notebook is very high, so that everything is overriden # Only the color of the tab labels needs to be modified inside the -- 1.7.6 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH] Remove hippo from the intro screens
Switch to standard GTK containers. Specific coloring details have been
moved to the theme at the same time.
Based on earlier work by Raul Gutierrez and Walter Bender.
---
src/jarabe/intro/colorpicker.py | 24
src/jarabe/intro/window.py | 122 ++-
2 files changed, 69 insertions(+), 77 deletions(-)
For correct visual appearance, depends on patch:
[PATCH sugar-artwork] Enforce white background on intro screen
diff --git a/src/jarabe/intro/colorpicker.py b/src/jarabe/intro/colorpicker.py
index 997199b..75c15c1 100644
--- a/src/jarabe/intro/colorpicker.py
+++ b/src/jarabe/intro/colorpicker.py
@@ -14,27 +14,27 @@
# along with this program; if not, write to the Free Software
# Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA
-import hippo
+import gtk
-from sugar.graphics.icon import CanvasIcon
+from sugar.graphics.icon import Icon
from sugar.graphics import style
from sugar.graphics.xocolor import XoColor
-class ColorPicker(hippo.CanvasBox, hippo.CanvasItem):
-def __init__(self, **kwargs):
-hippo.CanvasBox.__init__(self, **kwargs)
-self.props.orientation = hippo.ORIENTATION_HORIZONTAL
+class ColorPicker(gtk.EventBox):
+def __init__(self):
+gtk.EventBox.__init__(self)
self._xo_color = None
-self._xo = CanvasIcon(size=style.XLARGE_ICON_SIZE,
- icon_name='computer-xo')
+self._xo = Icon(pixel_size=style.XLARGE_ICON_SIZE,
+icon_name='computer-xo')
self._set_random_colors()
-self._xo.connect('activated', self._xo_activated_cb)
-self.append(self._xo)
+self.connect('button-press-event', self._button_press_cb)
+self.add(self._xo)
-def _xo_activated_cb(self, item):
-self._set_random_colors()
+def _button_press_cb(self, widget, event):
+if event.button == 1 and event.type == gtk.gdk.BUTTON_PRESS:
+self._set_random_colors()
def get_color(self):
return self._xo_color
diff --git a/src/jarabe/intro/window.py b/src/jarabe/intro/window.py
index df19fbf..f7937b1 100644
--- a/src/jarabe/intro/window.py
+++ b/src/jarabe/intro/window.py
@@ -22,12 +22,10 @@ import pwd
import gtk
import gobject
-import hippo
from sugar import env
from sugar.graphics import style
from sugar.graphics.icon import Icon
-from sugar.graphics.entry import CanvasEntry
from sugar.graphics.xocolor import XoColor
from jarabe.intro import colorpicker
@@ -57,13 +55,13 @@ def create_profile(name, color=None):
logging.error('Keypair exists, skip generation.')
-class _Page(hippo.CanvasBox):
+class _Page(gtk.VBox):
__gproperties__ = {
'valid': (bool, None, None, False, gobject.PARAM_READABLE),
}
-def __init__(self, **kwargs):
-hippo.CanvasBox.__init__(self, **kwargs)
+def __init__(self):
+gtk.VBox.__init__(self)
self.valid = False
def set_valid(self, valid):
@@ -80,27 +78,23 @@ class _Page(hippo.CanvasBox):
class _NamePage(_Page):
def __init__(self, intro):
-_Page.__init__(self, xalign=hippo.ALIGNMENT_CENTER,
- background_color=_BACKGROUND_COLOR.get_int(),
- spacing=style.DEFAULT_SPACING,
- orientation=hippo.ORIENTATION_HORIZONTAL,)
-
+_Page.__init__(self)
self._intro = intro
-label = hippo.CanvasText(text=_('Name:'))
-self.append(label)
-
-self._entry = CanvasEntry(box_width=style.zoom(300))
-self._entry.set_background(_BACKGROUND_COLOR.get_html())
-self._entry.connect('notify::text', self._text_changed_cb)
+alignment = gtk.Alignment(0.5, 0.5, 0, 0)
+self.pack_start(alignment, expand=True, fill=True)
-widget = self._entry.props.widget
-widget.set_max_length(45)
+hbox = gtk.HBox(spacing=style.DEFAULT_SPACING)
+alignment.add(hbox)
-self.append(self._entry)
+label = gtk.Label(_('Name:'))
+hbox.pack_start(label, expand=False)
-if gtk.widget_get_default_direction() == gtk.TEXT_DIR_RTL:
-self.reverse()
+self._entry = gtk.Entry()
+self._entry.connect('notify::text', self._text_changed_cb)
+self._entry.set_size_request(style.zoom(300), -1)
+self._entry.set_max_length(45)
+hbox.pack_start(self._entry, expand=False)
def _text_changed_cb(self, entry, pspec):
valid = len(entry.props.text.strip()) 0
@@ -113,22 +107,21 @@ class _NamePage(_Page):
self._entry.props.text = new_name
def activate(self):
-self._entry.props.widget.grab_focus()
+self._entry.grab_focus()
class _ColorPage(_Page):
-def __init__(self, **kwargs):
-_Page.__init__(self, xalign=hippo.ALIGNMENT_CENTER,
- background_color=_BACKGROUND_COLOR.get_int(),
-
[Sugar-devel] [PATCH sugar-toolkit] Don't put event box in toplevel window
From: Simon Schampijer si...@schampijer.de
Remove an unnecessary toplevel widget.
This event box was originally added by Marco to make it easier
to take screenshot of the canvas area only (7f731457c2) but we're
unsure why this is, and it doesn't seem to be needed for our current
screenshot-taking mechanism. Screenshots continue to work fine after
removing this.
---
src/sugar/graphics/window.py | 13 +
1 files changed, 5 insertions(+), 8 deletions(-)
diff --git a/src/sugar/graphics/window.py b/src/sugar/graphics/window.py
index b269efc..dbac464 100644
--- a/src/sugar/graphics/window.py
+++ b/src/sugar/graphics/window.py
@@ -103,12 +103,9 @@ class Window(gtk.Window):
self.__vbox.pack_start(self.__hbox)
self.__hbox.show()
-self._event_box = gtk.EventBox()
-self.__hbox.pack_start(self._event_box)
-self._event_box.show()
-self._event_box.add_events(gtk.gdk.POINTER_MOTION_HINT_MASK
- | gtk.gdk.POINTER_MOTION_MASK)
-self._event_box.connect('motion-notify-event', self.__motion_notify_cb)
+self.add_events(gtk.gdk.POINTER_MOTION_HINT_MASK
+| gtk.gdk.POINTER_MOTION_MASK)
+self.connect('motion-notify-event', self.__motion_notify_cb)
self.add(self.__vbox)
self.__vbox.show()
@@ -173,10 +170,10 @@ class Window(gtk.Window):
def set_canvas(self, canvas):
if self._canvas:
-self._event_box.remove(self._canvas)
+self.__hbox.remove(self._canvas)
if canvas:
-self._event_box.add(canvas)
+self.__hbox.pack_start(canvas)
self._canvas = canvas
self.__vbox.set_focus_child(self._canvas)
--
1.7.6
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar-artwork] Enforce white background on intro screen
On Sat, Sep 17, 2011 at 7:27 AM, Daniel Drake d...@laptop.org wrote: As part of the hippocanvas removal process, we can move intro window theming details into the theme. The intro window has a white background for itself and its children. --- gtk/theme/gtkrc.em | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/gtk/theme/gtkrc.em b/gtk/theme/gtkrc.em index 7f180a7..0811548 100644 --- a/gtk/theme/gtkrc.em +++ b/gtk/theme/gtkrc.em @@ -770,6 +770,8 @@ widget_class *SugarAlert* style black-bg-child widget_class *SugarSectionView style white-bg widget_class *SugarSectionView* style white-bg-child +widget_class *SugarIntroWindow style white-bg +widget_class *SugarIntroWindow* style white-bg-child # The notebook is very high, so that everything is overriden # Only the color of the tab labels needs to be modified inside the -- 1.7.6 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Cool. I had been looking into adding the much-asked-for feature to let kids set background images and always bumped up against hippo. That was one of my early motivations for embarking down the no-hippo path. -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] [PATCH] Remove hippo from the intro screens
On 17 September 2011 12:30, Daniel Drake d...@laptop.org wrote: Switch to standard GTK containers. Specific coloring details have been moved to the theme at the same time. Based on earlier work by Raul Gutierrez and Walter Bender. --- src/jarabe/intro/colorpicker.py | 24 src/jarabe/intro/window.py | 122 ++- 2 files changed, 69 insertions(+), 77 deletions(-) For correct visual appearance, depends on patch: [PATCH sugar-artwork] Enforce white background on intro screen This looks good to me. Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [PATCH sugar-artwork] Enforce white background on intro screen
Looks good to me. On 17 September 2011 12:27, Daniel Drake d...@laptop.org wrote: As part of the hippocanvas removal process, we can move intro window theming details into the theme. The intro window has a white background for itself and its children. --- gtk/theme/gtkrc.em | 2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/gtk/theme/gtkrc.em b/gtk/theme/gtkrc.em index 7f180a7..0811548 100644 --- a/gtk/theme/gtkrc.em +++ b/gtk/theme/gtkrc.em @@ -770,6 +770,8 @@ widget_class *SugarAlert* style black-bg-child widget_class *SugarSectionView style white-bg widget_class *SugarSectionView* style white-bg-child +widget_class *SugarIntroWindow style white-bg +widget_class *SugarIntroWindow* style white-bg-child # The notebook is very high, so that everything is overriden # Only the color of the tab labels needs to be modified inside the -- 1.7.6 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] TurtleArt localizaion: Send speeds the robot.
Hi all, The French localizers have a question regarding the TurtleArt activity. We want to translate the string Send speeds the robot. Could someone provide a contextual explanation of the process involved? I could'nt find where this string occurs in the activity. TIA for your help Rgds Samy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Memorize testing version
On 17 Sep 2011, at 06:21, Gonzalo Odiard wrote: On Fri, Sep 16, 2011 at 11:42 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Gonzalo, On 16 Sep 2011, at 02:14, Gonzalo Odiard wrote: I have uploaded a new version of Memorize [1], with the changes we discussed in irc today, and a few more fixes. * Auto save of modified games (but no demos) * Alerts with new texts. * Change to equal tiles mode fixes. * Remove hippo dependency. Any feedback is welcomed Just managed to take a quick look tonight. On an XO the Stop button falls off the toolbar into the overflow menu. Couple of suggestions to rectify it: - Use separator.set_size_request(0, -1) on the invisible separator that is used to push the Stop button to the right, otherwise it takes up some space and can trigger an overflow. - We can drop the separator between 'Restart Game' and the 'Equal Pairs' icon Thanks! Just in time to the release :) I needed remove the intermediate separator and do the set_size_request, but we will have problems with other languages. The spanish translation of 'Load demo games' is 'Cargar juegos de demostracion' and two buttons are out :( Damn :-( :-( Keep getting caught out by toolbar text translations. Manuel: Pester/remind me about adding a new HIG recommendation to avoid using text in the toolbars unless there is plenty of free space available, this one has caught us several times already. May be we can use a collection button (with a box, like in abacus or turtle art? Yes, I guess is the option we now have. We will need an icon, or icons for the current 3 demo games. We could use a single icon like TamTam Synth's sound presets (a memorise like document would do), or try for a custom icon for each game like Walter tried for Abacus – if there are good candidates (addition, letters, sounds). Raises an interesting issue regarding disabling of a primary toolbar icon with a secondary palette, or do we just disable the demo game buttons on the secondary palette. Need to watch for corner cases, e.g if the demo game secondary toolbar is already open when a user clicks customize. Perhaps we do not need to disable the demo game selection now that we have the warning message (i.e. allow users to load in different demo games so they can see/edit the cards directly in customise mode)? Some suggested string changes: - 'Click for non equal pairs' should be 'Set non equal pairs' - 'Click for equal pairs' should be 'Set equal pairs' - 'Click for ungrouped game' should be 'Set ungrouped game' - 'Click for grouped game' should be 'Set grouped game' Perfect, applied. Other than that it's looking good! :) I will try to publish one new version tomorrow. May be the Monday we can discuss the demos combo substitution in the Design chat. Sure. Do we still have time before we need to make an official release? Regards, --Gary Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] TurtleArt localizaion: Send speeds the robot.
Hi Walter, Le samedi 17 septembre 2011 à 13:13 -0400, Walter Bender a écrit : On Sat, Sep 17, 2011 at 11:17 AM, samy boutayeb s.bouta...@free.fr wrote: Hi all, The French localizers have a question regarding the TurtleArt activity. We want to translate the string Send speeds the robot. This is a typo. Please translate it as Sends speed to the robot Done committed! BTW, I just noticed that the German and Spanish localizer were smarter as me, and already interpreted the original string correctly. FYI, the TA POT file contains strings for the various plugins and TA derivative projects as well. These strings are aggregated in taextras.py. The string in question is part of the Sumo robotics activity developed in .UY. I'll reconcile the problem with the developers. Great! Thanks for the explanation. Regards Samy thanks. -walter Could someone provide a contextual explanation of the process involved? I could'nt find where this string occurs in the activity. TIA for your help Rgds Samy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH sugar-artwork] Add style for naming alert
Apply a white background to the naming alert window and the entry widget. The textbuffer widgets require a grey background still, as that is used to draw their borders. --- gtk/theme/gtkrc.em |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/gtk/theme/gtkrc.em b/gtk/theme/gtkrc.em index 0811548..98ca7cc 100644 --- a/gtk/theme/gtkrc.em +++ b/gtk/theme/gtkrc.em @@ -773,6 +773,11 @@ widget_class *SugarSectionView* style white-bg-child widget_class *SugarIntroWindow style white-bg widget_class *SugarIntroWindow* style white-bg-child +# Naming alert needs white background for main window and for entry widget, +# but other backgrounds must be left grey as they are used for drawing borders +widget_class *SugarNamingAlert style white-bg +widget_class *SugarNamingAlert*GtkEntry style white-bg-child + # The notebook is very high, so that everything is overriden # Only the color of the tab labels needs to be modified inside the # notebooks in this style (and the widget itself). -- 1.7.6 ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [PATCH sugar-toolkit] Remove hippo from naming alert
Reimplement the favorite icon as a ToggleButton, and use standard
boxes, entrys and textviews for the other aspects.
---
src/sugar/activity/namingalert.py | 227 +++--
1 files changed, 90 insertions(+), 137 deletions(-)
I know there is some discussion around removing this dialog, but to
keep things moving and unblocked on the hippo removal front, here is
a quick port.
For correct visual appearance, depends on:
[PATCH sugar-artwork] Add style for naming alert
diff --git a/src/sugar/activity/namingalert.py
b/src/sugar/activity/namingalert.py
index c3d45df..80d3e14 100644
--- a/src/sugar/activity/namingalert.py
+++ b/src/sugar/activity/namingalert.py
@@ -21,17 +21,13 @@ import os
import gio
import gtk
import gobject
-import hippo
import gconf
from sugar.graphics import style
from sugar.graphics.icon import Icon
from sugar.graphics.xocolor import XoColor
-from sugar.graphics.icon import CanvasIcon
from sugar.graphics.icon import get_icon_file_name
-from sugar.graphics.entry import CanvasEntry
from sugar.graphics.toolbutton import ToolButton
-from sugar.graphics.canvastextview import CanvasTextView
from sugar.bundle.activitybundle import ActivityBundle
@@ -114,45 +110,37 @@ class NamingToolbar(gtk.Toolbar):
self.emit('keep-clicked')
-class FavoriteIcon(CanvasIcon):
+class FavoriteIcon(gtk.ToggleButton):
-def __init__(self, favorite):
-CanvasIcon.__init__(self, icon_name='emblem-favorite',
-box_width=style.GRID_CELL_SIZE * 3 / 5,
-size=style.SMALL_ICON_SIZE)
-self._favorite = None
-self.set_favorite(favorite)
-self.connect('button-release-event', self.__release_event_cb)
-self.connect('motion-notify-event', self.__motion_notify_event_cb)
+def __init__(self):
+gtk.ToggleButton.__init__(self)
+self.set_relief(gtk.RELIEF_NONE)
+self.set_focus_on_click(False)
+
+self._icon = Icon(icon_name='emblem-favorite',
+ pixel_size=style.SMALL_ICON_SIZE)
+self.set_image(self._icon)
-def set_favorite(self, favorite):
-if favorite == self._favorite:
-return
+self.connect('toggled', self.__toggled_cb)
+self.connect('leave-notify-event', self.__leave_notify_event_cb)
+self.connect('enter-notify-event', self.__enter_notify_event_cb)
-self._favorite = favorite
-if favorite:
+def __toggled_cb(self, widget):
+if self.get_active():
client = gconf.client_get_default()
color = XoColor(client.get_string('/desktop/sugar/user/color'))
-self.props.xo_color = color
+self._icon.props.xo_color = color
else:
-self.props.stroke_color = style.COLOR_BUTTON_GREY.get_svg()
-self.props.fill_color = style.COLOR_WHITE.get_svg()
-
-def get_favorite(self):
-return self._favorite
-
-favorite = gobject.property(
-type=bool, default=False, getter=get_favorite, setter=set_favorite)
+self._icon.props.stroke_color = style.COLOR_BUTTON_GREY.get_svg()
+self._icon.props.fill_color = style.COLOR_WHITE.get_svg()
-def __release_event_cb(self, icon, event):
-self.props.favorite = not self.props.favorite
+def __enter_notify_event_cb(self, icon, event):
+if not self.get_active():
+self._icon.props.fill_color = style.COLOR_BUTTON_GREY.get_svg()
-def __motion_notify_event_cb(self, icon, event):
-if not self._favorite:
-if event.detail == hippo.MOTION_DETAIL_ENTER:
-icon.props.fill_color = style.COLOR_BUTTON_GREY.get_svg()
-elif event.detail == hippo.MOTION_DETAIL_LEAVE:
-icon.props.fill_color = style.COLOR_TRANSPARENT.get_svg()
+def __leave_notify_event_cb(self, icon, event):
+if not self.get_active():
+self._icon.props.fill_color = style.COLOR_TRANSPARENT.get_svg()
class NamingAlert(gtk.Window):
@@ -194,71 +182,66 @@ class NamingAlert(gtk.Window):
vbox.pack_start(toolbar, False)
toolbar.show()
-canvas = hippo.Canvas()
-self._root = hippo.CanvasBox()
-self._root.props.background_color = style.COLOR_WHITE.get_int()
-canvas.set_root(self._root)
-vbox.pack_start(canvas)
-canvas.show()
-
body = self._create_body()
-self._root.append(body, hippo.PACK_EXPAND)
+vbox.pack_start(body, expand=True, fill=True)
+body.show()
-widget = self._title.get_property('widget')
-widget.grab_focus()
+self._title.grab_focus()
def _create_body(self):
-body = hippo.CanvasBox()
-body.props.orientation = hippo.ORIENTATION_VERTICAL
-body.props.background_color = style.COLOR_WHITE.get_int()
-body.props.padding_top = style.DEFAULT_SPACING * 3
+body =
Re: [Sugar-devel] [PATCH sugar-toolkit] Remove hippo from naming alert
On 17 Sep 2011, at 18:37, Daniel Drake d...@laptop.org wrote: Reimplement the favorite icon as a ToggleButton, and use standard boxes, entrys and textviews for the other aspects. --- src/sugar/activity/namingalert.py | 227 +++-- 1 files changed, 90 insertions(+), 137 deletions(-) I know there is some discussion around removing this dialog, but to keep things moving and unblocked on the hippo removal front, here is a quick port. For correct visual appearance, depends on: [PATCH sugar-artwork] Add style for naming alert Simon has a patch to drop the alert. If there is consensus I guess it would be easier to just do that, not sure if that's the case though. Marco ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
[Sugar-devel] [Analyze]: what is translatable in Buddy %(path)s. ...
Hi again, In the activity Analyze, I wanted to localize a few mixed strings, where it is difficult to decide where is the translatable text and the untranslatable variable. For instance, in [1]: Calling Buddy %s.GetJoinedActivities() or in [2]: Buddy %(path)s.GetProperties() - %(props)r My guess is that in [1] one should translate Calling and Buddy, and in [2], one should only translate Buddy. could someone confirm what is translatable in those strings? TIA samy ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Analyze]: what is translatable in Buddy %(path)s. ...
On Sat, Sep 17, 2011 at 6:04 PM, samy boutayeb s.bouta...@free.fr wrote: Hi again, In the activity Analyze, I wanted to localize a few mixed strings, where it is difficult to decide where is the translatable text and the untranslatable variable. For instance, in [1]: Calling Buddy %s.GetJoinedActivities() or in [2]: Buddy %(path)s.GetProperties() - %(props)r My guess is that in [1] one should translate Calling and Buddy, and in [2], one should only translate Buddy. could someone confirm what is translatable in those strings? Samy, The context in code is fairly easy to look up in git by using the location string as a reference can often shed some light on strings like this: From the location string: /home/garycmartin/Activities/Analyze.activity/ps_watcher.py:261 Calling Buddy %s.GetJoinedActivities() http://git.sugarlabs.org/analyze/mainline/blobs/master/ps_watcher.py#line261 Buddy %(path)s.GetProperties() - %(props)r http://git.sugarlabs.org/analyze/mainline/blobs/master/ps_watcher.py#line370 I'm not really a Python programmer, but I think your interpretation is correct from the overall context surrounding those lines, take a look and judge for yourself. cjl ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Analyze]: what is translatable in ''Buddy %(path)s. ...''
Hi
The full context for [1] is
self.ps_watcher.log('Calling Buddy %s.GetProperties()', object_path)
in general, everything within the quote marks except %s is translatable but
this appears to be some kind of programming diagnostic message and the
universal language of programming is English
GetProperties() would not be translated because that is the procedure name that
has been called
Do you call procedures in French? Should Buddy be translated? It depends what a
French speaking programmer would find a useful diagnostic message.
Tony
Hi again,
In the activity Analyze, I wanted to localize a few mixed strings, where
it is difficult to decide where is the translatable text and the
untranslatable variable.
For instance, in [1]:
Calling Buddy %s.GetJoinedActivities()
or in [2]:
Buddy %(path)s.GetProperties() - %(props)r
My guess is that in [1] one should translate Calling and Buddy, and
in [2], one should only translate Buddy.
could someone confirm what is translatable in those strings?
TIA
samy
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_
This mail has been virus scanned by Australia On Line
see http://www.australiaonline.net.au/mailscanning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Analyze]: what is translatable in Buddy %(path)s. ...
Hi Samy, On 17 Sep 2011, at 23:04, samy boutayeb s.bouta...@free.fr wrote: Hi again, In the activity Analyze, I wanted to localize a few mixed strings, where it is difficult to decide where is the translatable text and the untranslatable variable. For instance, in [1]: Calling Buddy %s.GetJoinedActivities() or in [2]: Buddy %(path)s.GetProperties() - %(props)r My guess is that in [1] one should translate Calling and Buddy, and in [2], one should only translate Buddy. could someone confirm what is translatable in those strings? Yes you guess is correct. Analyse is an interesting case regarding translation as it does output so much technical text information, hard to know where to start with adding #TRANS comment hints ;) Regards, --Gary TIA samy ___ 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] [Analyze]: what is translatable in ''Buddy %(path)s. ...''
Looking into it further I have looked at the Analyze output and the diagnostic print out had the text from [1] preceded by a line GetBuddies() returned dbus where GetBuddies() is a procedure name in the program which is invariant in different languages On that basis, it makes more sense not to translate 'Buddy' in [1] so its relationship to the previous diagnostic line is more obvious Tony Hi Samy, On 17 Sep 2011, at 23:04, samy boutayeb s.bouta...@free.fr wrote: Hi again, In the activity Analyze, I wanted to localize a few mixed strings, where it is difficult to decide where is the translatable text and the untranslatable variable. For instance, in [1]: Calling Buddy %s.GetJoinedActivities() or in [2]: Buddy %(path)s.GetProperties() - %(props)r My guess is that in [1] one should translate Calling and Buddy, and in [2], one should only translate Buddy. could someone confirm what is translatable in those strings? Yes you guess is correct. Analyse is an interesting case regarding translation as it does output so much technical text information, hard to know where to start with adding #TRANS comment hints ;) Regards, --Gary TIA samy ___ 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 _ This mail has been virus scanned by Australia On Line see http://www.australiaonline.net.au/mailscanning ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Analyze]: what is translatable in ''Buddy %(path)s. ...''
Hi Chris, Gary, Tony
Le dimanche 18 septembre 2011 à 09:17 +1000, fors...@ozonline.com.au a
écrit :
Hi
The full context for [1] is
self.ps_watcher.log('Calling Buddy %s.GetProperties()', object_path)
in general, everything within the quote marks except %s is translatable but
this appears to be some kind of programming diagnostic message and the
universal language of programming is English
GetProperties() would not be translated because that is the procedure name
that has been called
Do you call procedures in French? Should Buddy be translated? It depends what
a French speaking programmer would find a useful diagnostic message.
Yes, that's the point.
Generally speaking, the Analyse activity is a special one, since it's
more likely to be used by maintainers, and, as such, involves a fair
proportion of technical background, including the familiarity with
programming langages. But, at the moment, even kids are encouraged to
learn programming/scripting languages.
This is why the localization of an a activity like Analyse should be
carried out carefully, taking in account those young hackers in order to
support their learning process.
Again, thanks for your hints and explanations.
Rgds
samy
Tony
Hi again,
In the activity Analyze, I wanted to localize a few mixed strings, where
it is difficult to decide where is the translatable text and the
untranslatable variable.
For instance, in [1]:
Calling Buddy %s.GetJoinedActivities()
or in [2]:
Buddy %(path)s.GetProperties() - %(props)r
My guess is that in [1] one should translate Calling and Buddy, and
in [2], one should only translate Buddy.
could someone confirm what is translatable in those strings?
TIA
samy
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_
This mail has been virus scanned by Australia On Line
see http://www.australiaonline.net.au/mailscanning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] [Analyze]: what is translatable in ''Buddy %(path)s. ...''
maybe translate none of the strings that appear in the log window
just translate table headings where it makes sense in the context of a French
speaking programmer?
Hi Chris, Gary, Tony
Le dimanche 18 septembre 2011 Ã 09:17 +1000, fors...@ozonline.com.au a
écrit :
Hi
The full context for [1] is
self.ps_watcher.log('Calling Buddy %s.GetProperties()', object_path)
in general, everything within the quote marks except %s is translatable but
this appears to be some kind of programming diagnostic message and the
universal language of programming is English
GetProperties() would not be translated because that is the procedure name
that has been called
Do you call procedures in French? Should Buddy be translated? It depends
what a French speaking programmer would find a useful diagnostic message.
Yes, that's the point.
Generally speaking, the Analyse activity is a special one, since it's
more likely to be used by maintainers, and, as such, involves a fair
proportion of technical background, including the familiarity with
programming langages. But, at the moment, even kids are encouraged to
learn programming/scripting languages.
This is why the localization of an a activity like Analyse should be
carried out carefully, taking in account those young hackers in order to
support their learning process.
Again, thanks for your hints and explanations.
Rgds
samy
Tony
Hi again,
In the activity Analyze, I wanted to localize a few mixed strings, where
it is difficult to decide where is the translatable text and the
untranslatable variable.
For instance, in [1]:
Calling Buddy %s.GetJoinedActivities()
or in [2]:
Buddy %(path)s.GetProperties() - %(props)r
My guess is that in [1] one should translate Calling and Buddy, and
in [2], one should only translate Buddy.
could someone confirm what is translatable in those strings?
TIA
samy
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_
This mail has been virus scanned by Australia On Line
see http://www.australiaonline.net.au/mailscanning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
_
This mail has been virus scanned by Australia On Line
see http://www.australiaonline.net.au/mailscanning
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Memorize testing version
. Thanks! Just in time to the release :) I needed remove the intermediate separator and do the set_size_request, but we will have problems with other languages. The spanish translation of 'Load demo games' is 'Cargar juegos de demostracion' and two buttons are out :( Damn :-( :-( Keep getting caught out by toolbar text translations. Manuel: Pester/remind me about adding a new HIG recommendation to avoid using text in the toolbars unless there is plenty of free space available, this one has caught us several times already. May be we can use a collection button (with a box, like in abacus or turtle art? Yes, I guess is the option we now have. We will need an icon, or icons for the current 3 demo games. We could use a single icon like TamTam Synth's sound presets (a memorise like document would do), or try for a custom icon for each game like Walter tried for Abacus – if there are good candidates (addition, letters, sounds). Raises an interesting issue regarding disabling of a primary toolbar icon with a secondary palette, or do we just disable the demo game buttons on the secondary palette. Need to watch for corner cases, e.g if the demo game secondary toolbar is already open when a user clicks customize. Perhaps we do not need to disable the demo game selection now that we have the warning message (i.e. allow users to load in different demo games so they can see/edit the cards directly in customise mode)? When I did my proposal, I was worried of the size of the toolbar, and moved all the edition controls to a secondary toolbar. I am not really sure about how to solve all this. I will try to publish one new version tomorrow. May be the Monday we can discuss the demos combo substitution in the Design chat. Sure. Do we still have time before we need to make an official release? No :( We are already late, and asking for a exceptions. Gonzalo ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Please get surf-115.xo nominated and thus visible on ASLO
On Fri, Sep 16, 2011 at 3:48 AM, Peter Robinson pbrobin...@gmail.comwrote: Hi Lucian, On Fri, Sep 16, 2011 at 9:09 AM, Lucian Branescu lucian.brane...@gmail.com wrote: Surf is simply not ready, and broken in many ways. I haven't had time to work on it, or Browse for that matter. Also, a fully working Surf requires moving to pygobject-introspection (in the whole of sugar-toolkit), which might require moving to gtk3 as well. I'm fully aware of the issues with Surf and Browse, what we need is a Surf in its current incarnation that works with sugar 0/93/0.94 as it seems it currently dies on Fedora 16, a working Browser is the only thing currently blocking an entirely working Sugar environment on Fedora 16. So would it be possible for you to review the crash and fix up the issue? Does the aforementioned 106 do that, the current version I have is 115. Peter On 16 September 2011 04:28, Thomas C Gilliard satel...@bendbroadband.com wrote: Rafael Ortiz wrote: On Thu, Sep 15, 2011 at 7:30 AM, Thomas C Gilliard satel...@bendbroadband.com wrote: Please get surf-115.xo Nominated It is an inactive state on ASLO http://activities.sugarlabs.**org//en-US/sugar/ http://activities.sugarlabs.org//en-US/sugar/ and thus can only be listed in experimental listings (not visible to the public) We are using it as main browser in our f15 Soas (Sugar on a Stick) spin as Browse no longer works (xulrunner-1.9 is no longer supported ) References : (archived surf-115.xo; git and .rpm) http://wiki.sugarlabs.org/go/**Sugar_Creation_Kit#surf_**browser http://wiki.sugarlabs.org/go/Sugar_Creation_Kit#surf_browser The maintainer/developer hasn't uploaded latest versions to ASLO. Last one is v6 http://activities.sugarlabs.org/en-US/sugar/downloads/file/25930/surf-106.xo I've just changed it this version to public. I get file not found on this link. : ( Searches on Surf and surf come up empty Tom Gilliard satellit Cheers. Thanks for your help. Tom Gilliard sugarlabs volunteer __**_ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.**org Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/**listinfo/sugar-devel http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel Although the activity is marked as public, the packaged version must be uploaded again to pick up the changes. This is up to dev/maint. Cheers ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
Re: [Sugar-devel] Memorize testing version
2011/9/17 Gary Martin garycmar...@googlemail.com: On 17 Sep 2011, at 06:21, Gonzalo Odiard wrote: On Fri, Sep 16, 2011 at 11:42 PM, Gary Martin garycmar...@googlemail.com wrote: Hi Gonzalo, On 16 Sep 2011, at 02:14, Gonzalo Odiard wrote: I have uploaded a new version of Memorize [1], with the changes we discussed in irc today, and a few more fixes. * Auto save of modified games (but no demos) * Alerts with new texts. * Change to equal tiles mode fixes. * Remove hippo dependency. Any feedback is welcomed Just managed to take a quick look tonight. On an XO the Stop button falls off the toolbar into the overflow menu. Couple of suggestions to rectify it: - Use separator.set_size_request(0, -1) on the invisible separator that is used to push the Stop button to the right, otherwise it takes up some space and can trigger an overflow. - We can drop the separator between 'Restart Game' and the 'Equal Pairs' icon Thanks! Just in time to the release :) I needed remove the intermediate separator and do the set_size_request, but we will have problems with other languages. The spanish translation of 'Load demo games' is 'Cargar juegos de demostracion' and two buttons are out :( Damn :-( :-( Keep getting caught out by toolbar text translations. Manuel: Pester/remind me about adding a new HIG recommendation to avoid using text in the toolbars unless there is plenty of free space available, this one has caught us several times already. Yes Gary, I was also thinking that we should add this advice in Sugar's HIG May be we can use a collection button (with a box, like in abacus or turtle art? Yes, I guess is the option we now have. We will need an icon, or icons for the current 3 demo games. We could use a single icon like TamTam Synth's sound presets (a memorise like document would do), or try for a custom icon for each game like Walter tried for Abacus – if there are good candidates (addition, letters, sounds). As we are already late, I can try to do this change before monday meeting. Gonzalo, if you updated the patches, please send them to me. Raises an interesting issue regarding disabling of a primary toolbar icon with a secondary palette, or do we just disable the demo game buttons on the secondary palette. Need to watch for corner cases, e.g if the demo game secondary toolbar is already open when a user clicks customize. Perhaps we do not need to disable the demo game selection now that we have the warning message (i.e. allow users to load in different demo games so they can see/edit the cards directly in customise mode)? Some suggested string changes: - 'Click for non equal pairs' should be 'Set non equal pairs' - 'Click for equal pairs' should be 'Set equal pairs' - 'Click for ungrouped game' should be 'Set ungrouped game' - 'Click for grouped game' should be 'Set grouped game' Perfect, applied. Other than that it's looking good! :) I will try to publish one new version tomorrow. May be the Monday we can discuss the demos combo substitution in the Design chat. Sure. Do we still have time before we need to make an official release? Regards, --Gary Gonzalo -- .. manuq .. ___ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel
