Re: [Sugar-devel] [PATCH sugar-toolkit] bundlebuilder: add back build_locale functionality to XOPackager SL #3116

2011-09-28 Thread Simon Schampijer

On 09/26/2011 03:00 PM, Sascha Silbe wrote:

Excerpts from Simon Schampijer's message of 2011-09-22 16:18:59 +0200:

Due to the removal of the manifest support we lost as well
the part of the code that does build the locale. This patch
adds that functionality back.


Thanks for the patch!

Acked-By: Sascha Silbesi...@activitycentral.com

Sascha


Pushed to master 29a700b34a8aa2814b8a29fff18921405078fce5 and 
sucrose-0.94 334cddcc80fc698960edb900454a0e7fd01ccfa3 (as it is a 0.94 
regression I think it is appropriate to do).


Regards,
   Simon

PS: forgot to add the Acked-By when commiting
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH sugar-toolkit] bundlebuilder: refactor get_files_git to Packager to avoid code duplication

2011-09-28 Thread Simon Schampijer

On 09/26/2011 03:10 PM, Sascha Silbe wrote:

Excerpts from Simon Schampijer's message of 2011-09-19 19:12:39 +0200:


Follow up patch for b582736375218e8944b3ce3daac667c7910a7e73


Thanks for the patch!

Acked-By: Sascha Silbesi...@activitycentral.com

Sascha



Thanks Daniel and Sascha for the review, pushed as: 
37568a0a7e06146d1a013aceefd1a9d5264d4e83 (on master only).


Regards,
   Simon

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH] Update alpha according to filter after events in neighborhoodview icons - SL #3091

2011-09-28 Thread Gonzalo Odiard
On Mon, Sep 26, 2011 at 9:29 AM, Sascha Silbe si...@activitycentral.comwrote:

 Excerpts from godiard's message of 2011-09-22 21:11:42 +0200:

 [src/jarabe/desktop/networkviews.py]
  @@ -149,6 +149,7 @@ class WirelessNetworkView(CanvasPulsingIcon):
   self._update_state()
   self._update_icon()
   self._update_badge()
  +self._update_color()
 [...]

 Thanks for the patch! However it looks more like a workaround than a
 real fix.

 Why do _all_ AP icons get updated when the state of at most two
 connections changes? Why does the alpha value get reset when the icons
 are updated?


The alpha is reseted when the animation stop.
I do not think this is not the right solution.
All the other properties (icon, color, badge) are uodated,
we added the alpha to display the filter, then we need update alpha too.

Gonzalo



 Neither the patch description nor the ticket nor digging into the source
 answer the above questions.

 Sascha

 --
 http://sascha.silbe.org/
 http://www.infra-silbe.de/




-- 
Gonzalo Odiard
SugarLabs Argentina
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [PATCH sugar] Control Panel About my Computer: show information on XO 1.75 OLPC #11232

2011-09-28 Thread Simon Schampijer
'/ofw' has been removed on the XOs now. We need to refine the
check if the machine is an XO in order to display the
information accordingly.

Follow up patch of b454c1253d95fc62c0cdf9ce34c40397a3c6f49e

Signed-off-by: Simon Schampijer si...@laptop.org
---
 extensions/cpsection/aboutcomputer/model.py |   46 +++
 extensions/cpsection/aboutcomputer/view.py  |4 +-
 2 files changed, 48 insertions(+), 2 deletions(-)

diff --git a/extensions/cpsection/aboutcomputer/model.py 
b/extensions/cpsection/aboutcomputer/model.py
index a02eee6..8cf3abb 100644
--- a/extensions/cpsection/aboutcomputer/model.py
+++ b/extensions/cpsection/aboutcomputer/model.py
@@ -41,6 +41,52 @@ _MODEL = 'openprom/model'
 _logger = logging.getLogger('ControlPanel - AboutComputer')
 _not_available = _('Not available')
 
+XO_1 = '1'
+XO_1_5 = '1.5'
+XO_1_75 = '1.75'
+
+
+def _get_xo_version():
+Gets the version of the XO
+
+There has been three revisions of the XO hardware as
+of today: 1, 1.5, 1.75
+
+Returns: a string indicating the version of the XO or None if
+ the hardware is not an XO
+
+
+xo_version = None
+if os.path.exists('/proc/device-tree/banner-name'):
+content = _read_file('/proc/device-tree/banner-name')
+if re.match(r'OLPC\ [BC][0-9]', content):
+xo_version = XO_1
+elif re.match(r'OLPC\ D[0-9]', content):
+xo_version = XO_1_5
+elif re.match(r'OLPC\ 1[ABC][0-9]', content):
+xo_version = XO_1_75
+elif os.path.exists('/sys/class/dmi/id/product_name'):
+if _read_file('/sys/class/dmi/id/product_name') == 'XO' and \
+os.path.exists('/sys/class/dmi/id/product_version'):
+content = _read_file('/sys/class/dmi/id/product_version')
+if content == '1':
+xo_version = XO_1
+elif content == '1.5':
+xo_version = XO_1_5
+elif os.path.exists('/ofw/banner-name'):
+content = _read_file('/ofw/banner-name')
+if re.match(r'OLPC\ [BC][0-9]', content):
+xo_version = XO_1
+return xo_version
+
+
+def is_xo():
+Checks if the underlying hardware is an XO
+
+Returns: True in the case the underlying hardware is an XO
+
+return _get_xo_version() is not None
+
 
 def get_aboutcomputer():
 msg = 'Serial Number: %s \nBuild Number: %s \nFirmware Number: %s \n' \
diff --git a/extensions/cpsection/aboutcomputer/view.py 
b/extensions/cpsection/aboutcomputer/view.py
index e5f2f32..baddbe2 100644
--- a/extensions/cpsection/aboutcomputer/view.py
+++ b/extensions/cpsection/aboutcomputer/view.py
@@ -47,7 +47,7 @@ class AboutComputer(SectionView):
 scrollwindow.add_with_viewport(self._vbox)
 self._vbox.show()
 
-if os.path.exists('/ofw'):
+if self._model.is_xo():
 self._setup_identity()
 
 self._setup_software()
@@ -127,7 +127,7 @@ class AboutComputer(SectionView):
 box_software.pack_start(box_sugar, expand=False)
 box_sugar.show()
 
-if os.path.exists('/ofw'):
+if self._model.is_xo():
 box_firmware = gtk.HBox(spacing=style.DEFAULT_SPACING)
 label_firmware = gtk.Label(_('Firmware:'))
 label_firmware.set_alignment(1, 0)
-- 
1.7.4.4

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] [DESIGN] Feedback about the changes in Memorize

2011-09-28 Thread Gonzalo Odiard
Dsd used Memorize and provided feedback about it.
I think can be useful, because he was not involved in the design processs.

There are bugs too, and I am working on them, but here I copy the references
to the UI:

*  The first little bit of confusion is what the 'play game' button is for
dsd_ i played the default game, and finished it
 now i want to play again, so i first went to click 'play game'
 maybe that was the wrong guess, but still, it is confusing that that button
doesnt do anything that i can see at this point

* dsd_ playing a bit more, it seems odd that the choice of 4x4 / 5x5 is a
combo,
 but the choice of demo game is a palette
 thats just a minor thing, but i cant (yet) see the reason for having those
ui elements different

* ok, it wasnt obvious to me that play and edit are a combo, especially with
them
right next to the activity icon which is not part of the combo

* dsd_ on the edit mode, it is a bit confusing that the add and update
buttons dont look like buttons
 also, 'update' feels a bit like 'save' which sugar doesnt really have
 feels like instant-update would be more appropriate
gonzalo_ dsd_, this part has not changed
 and really i want try to keep the needed changes at minimum
 we already changed a lot

* dsd_ took me a little while to understand 'Set equal pairs' but i get it
now
 but i'm wondering if something related to identical or matched would be
better terminology than equal

* dsd_ also, i cant quite get my head around if that button and the
grouped game icon at its right is done consistently with other parts of
the sugar UI
 as a button that not only can be on or off, but also changing its icon at
the same time
 so i'm left a bit uneasy as to whether i need to click on the icon to get
the graphical representation it is showing, or if that is the one i already
have
 it may be simpler if the icon did not change
 for example the grouped button could always show 1 1 2 2
 but you'd know if you're grouped or not based on the surrounding highlight
(toggle)
 or that might be worse. not sure

*  after editing the demo game and making my own
 the other collaborator's game doesnt update
 yet it shows that we are still collaborating together
 ah, it is very confused
 the collaborator has the old game (with 16 tiles) and the other laptop has
the modified game (with 4 tiles)
 if i click the tile in row 1, column 2, the equivalent row 1 column 2 tile
turns over on the other laptop as well
 but the tile contents are totally different (since the games are different)

Regards

Gonzalo
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


[Sugar-devel] Hello word

2011-09-28 Thread Héctor Sanchez
Hi,
I am a developer, member and contributor of SugarLabs Argentina and Python
Argentina.

I'll be reading and contributing in my free time, in this mailing list.

greetings!
-- 
Sanchez Héctor
@hectorksanchez
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Hello word

2011-09-28 Thread Martin Abente
Bienvenido! :)

2011/9/28 Héctor Sanchez hectorsanchez@gmail.com

 Hi,
 I am a developer, member and contributor of SugarLabs Argentina and Python
 Argentina.

 I'll be reading and contributing in my free time, in this mailing list.

 greetings!
 --
 Sanchez Héctor
 @hectorksanchez


 ___
 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] Hello word

2011-09-28 Thread Gonzalo Odiard
Hello Hector!
I hope the SugarCamp charged your batteries to participate more!

Gonzalo


2011/9/28 Héctor Sanchez hectorsanchez@gmail.com

 Hi,
 I am a developer, member and contributor of SugarLabs Argentina and Python
 Argentina.

 I'll be reading and contributing in my free time, in this mailing list.

 greetings!
 --
 Sanchez Héctor
 @hectorksanchez


 ___
 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] [ANNOUNCE] Sugar 0.94: go-no-go evaluation

2011-09-28 Thread Simon Schampijer

Hi,

I have been running through the open bugs on the Sugar Labs and OLPC bug 
tracker and found three issues that are regressions to 0.92.


#3091 Filter in neighborhood view: filter does not stay active when an 
icon has been clicked: For this bug we have a patch and it is under 
review. It is a minor issue that can be fixed with a future stable 
update, does not block the release.


#3116 bundlebuilder: 'setup.py build_xo' should build as well the .mo 
files: The patch has been reviewed and is pushed, will be included in 0.94.


#3135 copy to/from Journal sets read only: this issue has been 
introduced recently. If we have no fix by tomorrow, I would suggest to 
revert the commit for now. We should make sure that another patch of a 
patch series is still working (take a photo in record, rename it, close 
record, and then open the photo still).


The other area of regressions to older Sugar versions is collaboration. 
As we have released 0.90 and 0.92 with those regressions I think we 
should go ahead here as well and try to keep on fixing the regressions 
in future stable updates, the schedule [1] does take this into account.


We have a good basis of release notes, those need to be updated and 
polished [2].


Please report if there are any issues that yo have encountered that you 
think worth blocking the release. When you have XO hardware you can test 
easily the latest Sugar version in the latest 11.3.0 development build [3].


Otherwise, we will go ahead and release tomorrow as 'scheduled'.

Regards,
   Simon

PS: thanks a lot to Daniel Drake for the input on the items above.

[1] http://sugarlabs.org/go/0.94/Roadmap#Schedule
[2] http://wiki.sugarlabs.org/go/0.94/Notes
[3] http://build.laptop.org/11.3.0/os7/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH sugar] Control Panel About my Computer: show information on XO 1.75 OLPC #11232

2011-09-28 Thread Walter Bender
On Wed, Sep 28, 2011 at 10:24 AM, Simon Schampijer si...@schampijer.de wrote:
 '/ofw' has been removed on the XOs now. We need to refine the
 check if the machine is an XO in order to display the
 information accordingly.

Can we finally agree to create a toolkit method for this? As an
activity maintainer who needs to occasionally do things differently on
an XO than other HW, it would be really nice to not have to keep
changing my XO detection methods as the system changes under me.

regards.

-walter


 Follow up patch of b454c1253d95fc62c0cdf9ce34c40397a3c6f49e

 Signed-off-by: Simon Schampijer si...@laptop.org
 ---
  extensions/cpsection/aboutcomputer/model.py |   46 
 +++
  extensions/cpsection/aboutcomputer/view.py  |    4 +-
  2 files changed, 48 insertions(+), 2 deletions(-)

 diff --git a/extensions/cpsection/aboutcomputer/model.py 
 b/extensions/cpsection/aboutcomputer/model.py
 index a02eee6..8cf3abb 100644
 --- a/extensions/cpsection/aboutcomputer/model.py
 +++ b/extensions/cpsection/aboutcomputer/model.py
 @@ -41,6 +41,52 @@ _MODEL = 'openprom/model'
  _logger = logging.getLogger('ControlPanel - AboutComputer')
  _not_available = _('Not available')

 +XO_1 = '1'
 +XO_1_5 = '1.5'
 +XO_1_75 = '1.75'
 +
 +
 +def _get_xo_version():
 +    Gets the version of the XO
 +
 +    There has been three revisions of the XO hardware as
 +    of today: 1, 1.5, 1.75
 +
 +    Returns: a string indicating the version of the XO or None if
 +             the hardware is not an XO
 +
 +    
 +    xo_version = None
 +    if os.path.exists('/proc/device-tree/banner-name'):
 +        content = _read_file('/proc/device-tree/banner-name')
 +        if re.match(r'OLPC\ [BC][0-9]', content):
 +            xo_version = XO_1
 +        elif re.match(r'OLPC\ D[0-9]', content):
 +            xo_version = XO_1_5
 +        elif re.match(r'OLPC\ 1[ABC][0-9]', content):
 +            xo_version = XO_1_75
 +    elif os.path.exists('/sys/class/dmi/id/product_name'):
 +        if _read_file('/sys/class/dmi/id/product_name') == 'XO' and \
 +                os.path.exists('/sys/class/dmi/id/product_version'):
 +            content = _read_file('/sys/class/dmi/id/product_version')
 +            if content == '1':
 +                xo_version = XO_1
 +            elif content == '1.5':
 +                xo_version = XO_1_5
 +    elif os.path.exists('/ofw/banner-name'):
 +        content = _read_file('/ofw/banner-name')
 +        if re.match(r'OLPC\ [BC][0-9]', content):
 +            xo_version = XO_1
 +    return xo_version
 +
 +
 +def is_xo():
 +    Checks if the underlying hardware is an XO
 +
 +    Returns: True in the case the underlying hardware is an XO
 +    
 +    return _get_xo_version() is not None
 +

  def get_aboutcomputer():
     msg = 'Serial Number: %s \nBuild Number: %s \nFirmware Number: %s \n' \
 diff --git a/extensions/cpsection/aboutcomputer/view.py 
 b/extensions/cpsection/aboutcomputer/view.py
 index e5f2f32..baddbe2 100644
 --- a/extensions/cpsection/aboutcomputer/view.py
 +++ b/extensions/cpsection/aboutcomputer/view.py
 @@ -47,7 +47,7 @@ class AboutComputer(SectionView):
         scrollwindow.add_with_viewport(self._vbox)
         self._vbox.show()

 -        if os.path.exists('/ofw'):
 +        if self._model.is_xo():
             self._setup_identity()

         self._setup_software()
 @@ -127,7 +127,7 @@ class AboutComputer(SectionView):
         box_software.pack_start(box_sugar, expand=False)
         box_sugar.show()

 -        if os.path.exists('/ofw'):
 +        if self._model.is_xo():
             box_firmware = gtk.HBox(spacing=style.DEFAULT_SPACING)
             label_firmware = gtk.Label(_('Firmware:'))
             label_firmware.set_alignment(1, 0)
 --
 1.7.4.4

 ___
 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] [PATCH sugar] Control Panel About my Computer: show information on XO 1.75 OLPC #11232

2011-09-28 Thread Simon Schampijer

On 09/28/2011 06:24 PM, Walter Bender wrote:

On Wed, Sep 28, 2011 at 10:24 AM, Simon Schampijersi...@schampijer.de  wrote:

'/ofw' has been removed on the XOs now. We need to refine the
check if the machine is an XO in order to display the
information accordingly.


Can we finally agree to create a toolkit method for this? As an
activity maintainer who needs to occasionally do things differently on
an XO than other HW, it would be really nice to not have to keep
changing my XO detection methods as the system changes under me.

regards.

-walter


We discussed this a bit briefly the other day with Gonzalo and Daniel. 
The pro is, that code is not duplicated in activities. The con is, that 
activities should not depend on any hardware and use other methods to 
determine specific hardware (camera detection etc) and maybe there 
should be guidelines about good practices.


Good topic, we should see what makes sense and what we can agree on.

Regards,
   Simon
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH sugar] Control Panel About my Computer: show information on XO 1.75 OLPC #11232

2011-09-28 Thread Walter Bender
On Wed, Sep 28, 2011 at 12:30 PM, Simon Schampijer si...@schampijer.de wrote:
 On 09/28/2011 06:24 PM, Walter Bender wrote:

 On Wed, Sep 28, 2011 at 10:24 AM, Simon Schampijersi...@schampijer.de
  wrote:

 '/ofw' has been removed on the XOs now. We need to refine the
 check if the machine is an XO in order to display the
 information accordingly.

 Can we finally agree to create a toolkit method for this? As an
 activity maintainer who needs to occasionally do things differently on
 an XO than other HW, it would be really nice to not have to keep
 changing my XO detection methods as the system changes under me.

 regards.

 -walter

 We discussed this a bit briefly the other day with Gonzalo and Daniel. The
 pro is, that code is not duplicated in activities. The con is, that
 activities should not depend on any hardware and use other methods to
 determine specific hardware (camera detection etc) and maybe there should be
 guidelines about good practices.

I am sure that most of my problems are related to poor programming
practice, but in every activity I write, I need to set a font scale
differently for the XO than other HW and when I do have, for example,
the proper alsa controls for the microphone-sensor input, I still need
to know which version of the XO hardware I am using to set proper
calibration levels... So I don't see a work-around to not depending on
hardware. Some code snippets to show me the way would be greatly
appreciated (please add links from the Activity Team pages and in the
Almanac).

regards

-walter


 Good topic, we should see what makes sense and what we can agree on.

 Regards,
   Simon




-- 
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] [DESIGN] Feedback about the changes in Memorize

2011-09-28 Thread Gary Martin
On 28 Sep 2011, at 16:59, Gonzalo Odiard wrote:

 Dsd used Memorize and provided feedback about it.
 I think can be useful, because he was not involved in the design processs.

+1 Thanks for re-posting here so it's on record. I'd love to see many more 
folks try to gather such material, particularly from folks in deployments, 
working with our target users! Where do they get stuck, where are they making 
mistakes?

 There are bugs too, and I am working on them, but here I copy the references 
 to the UI:

;)

 *  The first little bit of confusion is what the 'play game' button is for
 dsd_ i played the default game, and finished it
  now i want to play again, so i first went to click 'play game'
  maybe that was the wrong guess, but still, it is confusing that that button 
 doesnt do anything that i can see at this point

Yes I worried about this also (until we had eliminated other UI options for the 
required Memorize mode/canvas change). Sugar design seems to have a 
particularly unconvincing way of displaying a set of related radio buttons, 
there is no joining of button shapes, and the only visible feedback that you 
are using a set of radio buttons is that the surrounding highlight toggles to 
the icon you click on.

Perhaps we can improve things visually by reworking the play and cog icons so 
they are clearly an icon pair, and/or more clearly radio buttons?

Perhaps the hint wording could be changed to 'Play game mode' and 'Edit game 
mode'?

Perhaps the 'Restart game' icon should move so that it is just after the first 
separator, nearer the 'Play game' radio button?

More scary option... What if we overloaded the 'Play game' radio button to 
reset the game if clicked on while already playing a game? We could remove the 
'Restart game' button.

 * dsd_ playing a bit more, it seems odd that the choice of 4x4 / 5x5 is a 
 combo,
  but the choice of demo game is a palette
  thats just a minor thing, but i cant (yet) see the reason for having those 
 ui elements different

The demo game widget used to be a text combo, just like the 4x4, 5x5 etc 
widget, but the text Load demo games needs to be localised and triggers a 
toolbar overflow (Spanish) loosing the Stop icon and one other.

  * ok, it wasnt obvious to me that play and edit are a combo, especially with 
 them 
 right next to the activity icon which is not part of the combo
 
 * dsd_ on the edit mode, it is a bit confusing that the add and update 
 buttons dont look like buttons
  also, 'update' feels a bit like 'save' which sugar doesnt really have
  feels like instant-update would be more appropriate

+1 for an instant update when editing a card, though that is another patch for 
another time (goal was to land the new toolbars – Memorize had previous 
workflow issues that have made it a non-trivial case).

 gonzalo_ dsd_, this part has not changed
  and really i want try to keep the needed changes at minimum
  we already changed a lot
 
 * dsd_ took me a little while to understand 'Set equal pairs' but i get it 
 now
  but i'm wondering if something related to identical or matched would be 
 better terminology than equal

Hmm, so something like 'Set identical pairs' vs. 'Set different pairs' wording?

 * dsd_ also, i cant quite get my head around if that button and the 
 grouped game icon at its right is done consistently with other parts of the 
 sugar UI
  as a button that not only can be on or off, but also changing its icon at 
 the same time
  so i'm left a bit uneasy as to whether i need to click on the icon to get 
 the graphical representation it is showing, or if that is the one i already 
 have
  it may be simpler if the icon did not change
  for example the grouped button could always show 1 1 2 2
  but you'd know if you're grouped or not based on the surrounding highlight 
 (toggle)
  or that might be worse. not sure

FWIW with both these two game type options I've always needed to discover or 
remind myself of them by trial and error to see just what difference they make 
to a game.

  *  after editing the demo game and making my own
  the other collaborator's game doesnt update
  yet it shows that we are still collaborating together
  ah, it is very confused
  the collaborator has the old game (with 16 tiles) and the other laptop has 
 the modified game (with 4 tiles)
  if i click the tile in row 1, column 2, the equivalent row 1 column 2 tile 
 turns over on the other laptop as well
  but the tile contents are totally different (since the games are different)

Ouch, a bug for you Gonzalo ;)

Regards,
--Gary

 Regards
 
 Gonzalo
 
 ___
 Sugar-devel mailing list
 Sugar-devel@lists.sugarlabs.org
 http://lists.sugarlabs.org/listinfo/sugar-devel

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Hello word

2011-09-28 Thread Gary Martin
Welcome!

On 28 Sep 2011, at 17:00, Héctor Sanchez wrote:

 Hi, 
 I am a developer, member and contributor of SugarLabs Argentina and Python 
 Argentina.
 
 I'll be reading and contributing in my free time, in this mailing list.
 
 greetings!
 -- 
 Sanchez Héctor
 @hectorksanchez
 
 ___
 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] Feedback about the changes in Memorize

2011-09-28 Thread Tabitha Roder
Memorize
On 29 September 2011 06:17, Gary Martin garycmar...@googlemail.com wrote:

  * dsd_ took me a little while to understand 'Set equal pairs' but i get
 it now
   but i'm wondering if something related to identical or matched would
 be better terminology than equal

 Hmm, so something like 'Set identical pairs' vs. 'Set different pairs'
 wording?


These words are much closer I think. If it helps, I think of it as duplicate
tile.
Maybe we don't want the word pairs but tiles, but I am not sure. Even
the word set doesn't fit somehow; maybe the word there is match.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [DESIGN] Feedback about the changes in Memorize

2011-09-28 Thread Walter Bender
On Wed, Sep 28, 2011 at 3:36 PM, Tabitha Roder tabi...@tabitha.net.nz wrote:
 Memorize
 On 29 September 2011 06:17, Gary Martin garycmar...@googlemail.com wrote:

  * dsd_ took me a little while to understand 'Set equal pairs' but i
  get it now
   but i'm wondering if something related to identical or matched
  would be better terminology than equal

 Hmm, so something like 'Set identical pairs' vs. 'Set different pairs'
 wording?

 These words are much closer I think. If it helps, I think of it as duplicate
 tile.
 Maybe we don't want the word pairs but tiles, but I am not sure. Even
 the word set doesn't fit somehow; maybe the word there is match.

+1

Only just now, reading match identical tiles, does it finally click
in my head what the radio buttons do.



 ___
 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] Hello word

2011-09-28 Thread Flavio Danesse
欢迎

*PD:*
Dice bienvenido en Chino, que es el idioma que más personas hablan en el
planeta.




2011/9/28 Martin Abente martin.abente.lah...@gmail.com

 Bienvenido! :)

 2011/9/28 Héctor Sanchez hectorsanchez@gmail.com

 Hi,
 I am a developer, member and contributor of SugarLabs Argentina and
 Python Argentina.

 I'll be reading and contributing in my free time, in this mailing list.

 greetings!
 --
 Sanchez Héctor
 @hectorksanchez


 ___
 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 mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] Hello word

2011-09-28 Thread Chris Leonard
2011/9/28 Héctor Sanchez hectorsanchez@gmail.com:
 Hi,
 I am a developer, member and contributor of SugarLabs Argentina and Python
 Argentina.

 I'll be reading and contributing in my free time, in this mailing list.

Héctor,

Welcome, don't forget that that doing a little localization work in
your spare time is a wonderful way to acquaint yourself with some of
the projects going on.

http://translate.sugarlabs.org/es/

cjl
Sugar Labs Translation team Coordinator
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel


Re: [Sugar-devel] [PATCH sugar] Control Panel About my Computer: show information on XO 1.75 OLPC #11232

2011-09-28 Thread James Cameron
On Wed, Sep 28, 2011 at 04:24:06PM +0200, Simon Schampijer wrote:
 '/ofw' has been removed on the XOs now. We need to refine the
 check if the machine is an XO in order to display the
 information accordingly.

Nak.  compatible is the more correct property in device-tree to use for
identifying XO-1.75, and is the property that OpenFirmware plans to
ensure is correct.

-- 
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] jhbuild improvement?

2011-09-28 Thread Bernie Innocenti
I was reading in the Gnome 3.2 release notes:


GNOME's build tool JHBuild does not build a module anymore if the
version installed on your system is recent enough. This is controlled by
the configuration option partial_build and it is enabled by default. The
command jhbuild sysdeps lists which system modules have been found as
well as the modules that are going to be build.

If you start to build GNOME from scratch with a recent distribution,
this can easily drop 50 modules from the list of modules to compile.


This feature could potentially reduce the complexity for setting up a
new development environment. What do you think?

-- 
Bernie Innocenti
Sugar Labs Infrastructure Team
http://wiki.sugarlabs.org/go/Infrastructure_Team

___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel