[Sugar-devel] Browse scaling for XO display

2010-11-03 Thread Walter Bender 
Does anyone recall what we did to make Browse rescale web pages for
the XO display? Here in Peru there is a series of pages that scale
properly from a server but not from the file system with Browse 108 on
Sugar 0.84 but Browse on 703 rescales both sources properly. (Sorry, I
don't know which version of Browse was on 703).

-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 Write] Change the logic for preserve the mime type at reading and saving files

2010-11-03 Thread James Cameron 
Reviewed-by: James Cameron 

-- 
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] Edit/audit wikipedia activity

2010-11-03 Thread Martin Langhoff 
On Tue, Oct 26, 2010 at 4:51 PM, Martin Langhoff
 wrote:
> On Thu, Oct 21, 2010 at 12:06 PM, Martin Langhoff
>  wrote:
>> Unfortunately, there is a clear need to organise a facility to
>> audit/edit the wikipedia snapshots we have and "repack" the archive.
>
> Some simple rough mods to server.py to allow local edits

Now with a few minor updates and fixes. Documentation at

   http://wiki.laptop.org/go/WikiBrowse_Editing

cheers,


m
-- 
 martin.langh...@gmail.com
 mar...@laptop.org -- School Server Architect
 - ask interesting questions
 - don't get distracted with shiny stuff  - working code first
 - http://wiki.laptop.org/go/User:Martinlanghoff
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] [PATCH Write] Change the logic for preserve the mime type at reading and saving files

2010-11-03 Thread godiard 
From: Gonzalo Odiard 

Open the text files in plain/text format, save the new file like .odt files
and preserve the mime type in all the cases but .doc files (abiword saves them 
like .rtf)
Related to tickets SL #2127, OLPC #8972, OLPC #5291 and OLPC #1925
---
 AbiWordActivity.py |   40 +---
 1 files changed, 21 insertions(+), 19 deletions(-)

diff --git a/AbiWordActivity.py b/AbiWordActivity.py
index 0f62523..fda1fdf 100644
--- a/AbiWordActivity.py
+++ b/AbiWordActivity.py
@@ -37,6 +37,7 @@ from sugar.activity.widgets import ActivityToolbarButton
 from sugar.activity.activity import get_bundle_path
 
 from sugar.presence import presenceservice
+from sugar import mime
 
 from sugar.graphics.toolbarbox import ToolbarButton, ToolbarBox
 from sugar.graphics.toggletoolbutton import ToggleToolButton
@@ -459,8 +460,8 @@ class AbiWordActivity(activity.Activity):
 def read_file(self, file_path):
 logging.debug('AbiWordActivity.read_file: %s, mimetype: %s',
 file_path, self.metadata['mime_type'])
-if 'source' in self.metadata and self.metadata['source'] == '1':
-logger.debug('Opening file in view source mode')
+if self.metadata['mime_type'] in ['text/plain', 'text/csv'] or \
+   'text/plain' in mime.get_mime_parents(self.metadata['mime_type']):
 self.abiword_canvas.load_file('file://' + file_path, 'text/plain')
 else:
 # we pass no mime/file type, let libabiword autodetect it,
@@ -468,25 +469,26 @@ class AbiWordActivity(activity.Activity):
 self.abiword_canvas.load_file('file://' + file_path, '')
 
 def write_file(self, file_path):
-logging.debug('AbiWordActivity.write_file')
-
-# check if we have a default mimetype; if not,
-# fall back to OpenDocument
-# also fallback if we know we cannot export in that format
-if 'mime_type' not in self.metadata or \
-self.metadata['mime_type'] == '' or \
-self.metadata['mime_type'] == 'application/msword':
-self.metadata['mime_type'] = \
-'application/vnd.oasis.opendocument.text'
-
-# if we were viewing the source of a file,
-# then always save as plain text
-actual_mimetype = self.metadata['mime_type']
-if 'source' in self.metadata and self.metadata['source'] == '1':
+logging.debug('AbiWordActivity.write_file: %s, mimetype: %s',
+file_path, self.metadata['mime_type'])
+# if we were editing a text file save as plain text
+if self.metadata['mime_type'] in ['text/plain', 'text/csv'] or \
+   'text/plain' in mime.get_mime_parents(self.metadata['mime_type']):
 logger.debug('Writing file as type source (text/plain)')
-actual_mimetype = 'text/plain'
+self.abiword_canvas.save('file://' + file_path, 'text/plain', '')
+else:
+#if the file is new, save in .odt format
+if self.metadata['mime_type'] == '':
+self.metadata['mime_type'] = \
+'application/vnd.oasis.opendocument.text'
+
+# Abiword can't save in .doc format, save in .rtf instead
+if self.metadata['mime_type'] == 'application/msword':
+self.metadata['mime_type'] = 'application/rtf'
+
+self.abiword_canvas.save('file://' + file_path,
+self.metadata['mime_type'], '')
 
 self.metadata['fulltext'] = \
 self.abiword_canvas.get_content(extension_or_mimetype=".txt") \
 [:3000]
-self.abiword_canvas.save('file://' + file_path, actual_mimetype, '')
-- 
1.7.2.3

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

Re: [Sugar-devel] Google Code-In

2010-11-03 Thread Walter Bender 
On Tue, Nov 2, 2010 at 8:17 AM, samir menon  wrote:
> I was just wondering if anyone knew if Sugar labs will be participating. I
> think it is a great way to encourage learners to help the Sugar community,
> and will prove to be invaluable to the Sugar community. The deadline for
> submission is , I believe, November 5th.

If someone would take the lead on it... I don't have the bandwidth at
the moment :(

-walter

>
> Thanks!,
> ~Samir
>
> ___
> 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] GIT.sugarlabs.org changes?

2010-11-03 Thread George Hunt 
Username for git.sl.o: georgejh...@gmail.com
projects: pydebug and xophoto

The push to jita.sl.o was successful!

George

On Wed, Nov 3, 2010 at 8:21 AM, Aleksey Lim  wrote:

> On Wed, Nov 03, 2010 at 06:22:14AM -0400, George Hunt wrote:
> > I tried the push from another ip address. Same result, so it's probably
> not
> > the blacklist problem.
> >
> > The literature suggests that I should check for world or group
> writeability
> > on the path from root to .ssh/known_hosts on the server, and on the
> client
> > machine. I have double checked my client. Don't have shell access to
> server.
>
> Could you try to push to the new [testing] gitorious
> http://jita.sugarlabs.org/
> To login to jita.sl.o, you need to use your git login name and wiki
> password
> for the same login (if there is no wiki account, follow "Create an account"
> link to create one) or, if you used OpenID, just login via "OpenID" link on
> jita.
>
> And what is your login on git.sl.o and project you are trying to push?
>
> > George
> >
> > On Sun, Oct 31, 2010 at 10:30 AM, Aleksey Lim  >wrote:
> >
> > > On Sat, Oct 30, 2010 at 07:58:00PM -0400, George Hunt wrote:
> > > > Hi Aleksey,
> > > >
> > > > Thanks for the response.
> > > >
> > > > The ssh step fails.  Trying ssh -vvv
> gitori...@git.sugarlabs.orgindicates
> > > > that the negotiation proceeds in what looks to be a normal manner,
> until
> > > the
> > > > point where the client determines that public key method is
> authorized,
> > > and
> > > > client is offering my public  key, and the next response is
> "connection
> > > > closed".
> > > >
> > > > 
> > > > debug1: Next authentication method: publickey
> > > > debug1: Offering public key:
> > > > debug3: send_pubkey_test
> > > > debug2: we sent a publickey packet, wait for reply
> > > > Connection closed by 140.211.167.221
> > > > 
> > >
> > > "Connection closed" seems suspiciously. We had problem w/ blacklisting
> > > of some IPs.
> > >
> > > Can you try to ssh connect from different IP?
> > >
> > > (I'm CCing it to systems@)
> > >
> > > > I guessed that the server has forgotten my public key, so I uploaded
> it
> > > > again. I don't know if it is related, but the listserve forgot that I
> was
> > > > receiving the "digest" form of the list on Oct 16 or so.
> > > >
> > > > After the upload still no luck -- though there may be some form of
> > > > authorization required and/or delay built in, since when I first
> uploaded
> > > my
> > > > public key last year, it didn't work for at least a day.
> > > >
> > > > George
> > > >
> > > > On Sat, Oct 30, 2010 at 5:53 PM, Aleksey Lim  >
> > > wrote:
> > > >
> > > > > On Sat, Oct 30, 2010 at 05:34:34PM -0400, George Hunt wrote:
> > > > > > I have 2 projects that I have been pushing git commits to  for
> almost
> > > a
> > > > > > year.  In one I created a new branch, and was concerned that my
> local
> > > > > change
> > > > > > was preventing the successful "git push".  But the other project
> has
> > > no
> > > > > > structural changes, and still gets the response "fatal: the
>  remote
> > > end
> > > > > hung
> > > > > > up unexpectedly" -- which I see has been a source of lots of
> > > headaches
> > > > > for
> > > > > > the inner circle.
> > > > > >
> > > > > > Should I just wait for 6 hours, and try again? How to proceed?
> > > > >
> > > > > Check if:
> > > > >
> > > > > * `ssh gitori...@git.sugarlabs.org` outputs "PTY allocation
> request.."
> > > > > * `git config remote.origin.url` output is equal to particular push
> > > link
> > > > >  on your project web page on git.sl.o
> > > > >
> > > > > --
> > > > > Aleksey
> > > > >
> > >
> > > --
> > > Aleksey
> > >
>
> --
> Aleksey
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [PATCH Pippy] Add EditToolbar and modify toolbars to support the older from sugar < 0.86

2010-11-03 Thread Simon Schampijer 

On 11/03/2010 04:24 AM, Anish Mangal wrote:

Hi,

Thank you for the patch, however,

* I'd prefer two patches for two different changes (layout
compatibility fix, edit toolbar), as I mailed earlier.
* Your patch moves the activity-exit button to the left for sugar
0.88+. This [1] is how it should look.
* Regarding the layout-fix, your patch introduces a 'new toolbar' to
contain the run/stop/clear buttons. There have been discussions on
list[2] and on IRC w/ erikos, garycmartin (IIRC), and we had decided
on keeping the old pippy layout for sugar<=0.84. I'd like to keep it
that way unless you can throw a good argument into the mix.


Yeah, this is true we did already argue about it. Though, I think that 
the changes Gonzalo is proposing do make sense. They make Pippy being 
aligned to the Sugar lookalike both for the old and for the new toolbar.


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

[Sugar-devel] [PATCH] Sugar Ad-hoc icons show in search results when connect/disconnect to AP OLPC #10412

2010-11-03 Thread Simon Schampijer 
When searching for an AP the Sugar ad-hoc networks are greyed
out (if their name does not contain the search string). When
then trying to connect to an AP the Sugar ad-hoc networks get
colored again.

The patch does make sure that the color is not set by each update
and that the member change does not trigger setting the color
of the icon.
---
 src/jarabe/desktop/networkviews.py |8 +++-
 1 files changed, 3 insertions(+), 5 deletions(-)

diff --git a/src/jarabe/desktop/networkviews.py 
b/src/jarabe/desktop/networkviews.py
index 87f182f..6305f04 100644
--- a/src/jarabe/desktop/networkviews.py
+++ b/src/jarabe/desktop/networkviews.py
@@ -517,9 +517,6 @@ class SugarAdhocView(CanvasPulsingIcon):
 else:
 icon_name = self._ICON_NAME + str(self._channel)
 
-self.props.base_color = self._state_color
-self._palette_icon.props.xo_color = self._state_color
-
 if icon_name is not None:
 self.props.icon_name = icon_name
 icon = self._palette.props.icon
@@ -549,6 +546,7 @@ class SugarAdhocView(CanvasPulsingIcon):
 
 def _update_color(self):
 if self._greyed_out:
+self.props.pulsing = False
 self.props.base_color = XoColor('#D5D5D5,#D5D5D5')
 else:
 self.props.base_color = self._state_color
@@ -557,12 +555,12 @@ class SugarAdhocView(CanvasPulsingIcon):
 if channel == self._channel:
 if has_members == True:
 self._state_color = profile.get_color()
-self.props.base_color = self._state_color
-self._palette_icon.props.xo_color = self._state_color
 else:
 color = '%s,%s' % (profile.get_color().get_stroke_color(),
style.COLOR_TRANSPARENT.get_svg())
 self._state_color = XoColor(color)
+
+if not self._greyed_out:
 self.props.base_color = self._state_color
 self._palette_icon.props.xo_color = self._state_color
 
-- 
1.7.2.3

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

Re: [Sugar-devel] [PATCH Pippy] Add EditToolbar and modify toolbars to support the older from sugar < 0.86

2010-11-03 Thread Gary Martin 
Hi Gonzalo,

On 3 Nov 2010, at 02:40, Gonzalo Odiard  wrote:

> This patch modify the last two patches from Anish to enable the use of the 
> right toolbars in every Sugar version.
> There are screenshots here:
> http://dev.laptop.org/~gonzalo/pippy-in-sugar-0.84.png
> http://dev.laptop.org/~gonzalo/pippy-in-sugar-0.90.png

The 'Stop' icon for new design toolbars should be pushed all the way over the 
the right with an invisible separator set to expand, here's a quick code 
example:


http://git.sugarlabs.org/projects/physics/repos/mainline/blobs/master/activity.py#line101

Regards,
--Gary

> 
> 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] New gitorious test request

2010-11-03 Thread Aleksey Lim 
On Wed, Nov 03, 2010 at 04:29:22AM +, Aleksey Lim wrote:
> Hi all,
> 
> It is a call to help with testing new gitorious.
> Please take a look to http://jita.sugarlabs.org/.
> It contains a *copy* or git.sugarlabs.org.

There is know problem with broken utf encoding for some non-English text,
it will be fixed while pushing new gitorious to the production.

> This is also a call to test integration of gitorious with
> a Central Login system[1] that might be used for password based
> accounts on all SL sites. For now, it looks to wiki-devel.sugarlabs.org
> account database. To login to git.sl.o, you need to use your git login
> name and wiki password for the same login (if there is no wiki account,
> follow "Create an account" link to create one).
> 
> [1] http://en.wikipedia.org/wiki/Central_Authentication_Service

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

Re: [Sugar-devel] GIT.sugarlabs.org changes?

2010-11-03 Thread Aleksey Lim 
On Wed, Nov 03, 2010 at 06:22:14AM -0400, George Hunt wrote:
> I tried the push from another ip address. Same result, so it's probably not
> the blacklist problem.
> 
> The literature suggests that I should check for world or group writeability
> on the path from root to .ssh/known_hosts on the server, and on the client
> machine. I have double checked my client. Don't have shell access to server.

Could you try to push to the new [testing] gitorious http://jita.sugarlabs.org/
To login to jita.sl.o, you need to use your git login name and wiki password
for the same login (if there is no wiki account, follow "Create an account"
link to create one) or, if you used OpenID, just login via "OpenID" link on 
jita.

And what is your login on git.sl.o and project you are trying to push?

> George
> 
> On Sun, Oct 31, 2010 at 10:30 AM, Aleksey Lim wrote:
> 
> > On Sat, Oct 30, 2010 at 07:58:00PM -0400, George Hunt wrote:
> > > Hi Aleksey,
> > >
> > > Thanks for the response.
> > >
> > > The ssh step fails.  Trying ssh -vvv gitori...@git.sugarlabs.orgindicates
> > > that the negotiation proceeds in what looks to be a normal manner, until
> > the
> > > point where the client determines that public key method is authorized,
> > and
> > > client is offering my public  key, and the next response is "connection
> > > closed".
> > >
> > > 
> > > debug1: Next authentication method: publickey
> > > debug1: Offering public key:
> > > debug3: send_pubkey_test
> > > debug2: we sent a publickey packet, wait for reply
> > > Connection closed by 140.211.167.221
> > > 
> >
> > "Connection closed" seems suspiciously. We had problem w/ blacklisting
> > of some IPs.
> >
> > Can you try to ssh connect from different IP?
> >
> > (I'm CCing it to systems@)
> >
> > > I guessed that the server has forgotten my public key, so I uploaded it
> > > again. I don't know if it is related, but the listserve forgot that I was
> > > receiving the "digest" form of the list on Oct 16 or so.
> > >
> > > After the upload still no luck -- though there may be some form of
> > > authorization required and/or delay built in, since when I first uploaded
> > my
> > > public key last year, it didn't work for at least a day.
> > >
> > > George
> > >
> > > On Sat, Oct 30, 2010 at 5:53 PM, Aleksey Lim 
> > wrote:
> > >
> > > > On Sat, Oct 30, 2010 at 05:34:34PM -0400, George Hunt wrote:
> > > > > I have 2 projects that I have been pushing git commits to  for almost
> > a
> > > > > year.  In one I created a new branch, and was concerned that my local
> > > > change
> > > > > was preventing the successful "git push".  But the other project has
> > no
> > > > > structural changes, and still gets the response "fatal: the  remote
> > end
> > > > hung
> > > > > up unexpectedly" -- which I see has been a source of lots of
> > headaches
> > > > for
> > > > > the inner circle.
> > > > >
> > > > > Should I just wait for 6 hours, and try again? How to proceed?
> > > >
> > > > Check if:
> > > >
> > > > * `ssh gitori...@git.sugarlabs.org` outputs "PTY allocation request.."
> > > > * `git config remote.origin.url` output is equal to particular push
> > link
> > > >  on your project web page on git.sl.o
> > > >
> > > > --
> > > > Aleksey
> > > >
> >
> > --
> > Aleksey
> >

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

Re: [Sugar-devel] [PATCH Pippy] Add EditToolbar and modify toolbars to support the older from sugar < 0.86

2010-11-03 Thread Gonzalo Odiard 
On Wed, Nov 3, 2010 at 12:24 AM, Anish Mangal  wrote:

> Hi,
>
> Thank you for the patch, however,
>
> * I'd prefer two patches for two different changes (layout
> compatibility fix, edit toolbar), as I mailed earlier.
>

Ok, resolve first the last. Does not have sense make two patches if you
don't want to use these changes.


> * Your patch moves the activity-exit button to the left for sugar
> 0.88+. This [1] is how it should look.
>

Done


> * Regarding the layout-fix, your patch introduces a 'new toolbar' to
> contain the run/stop/clear buttons. There have been discussions on
> list[2] and on IRC w/ erikos, garycmartin (IIRC), and we had decided
> on keeping the old pippy layout for sugar <=0.84. I'd like to keep it
> that way unless you can throw a good argument into the mix.
>
>
I think we can discuss if is better have two toolbars (one for
run/stop/clear and another to edit buttons) or have only one toolbar.
In Sugar usually we use a separated toolbar to the edit buttons, but a
development environment like Pippy can be a exception.

About using a toolbar or the old gtk buttons, my arguments are:
* The activity looks more integrated to Sugar
* Better screen usage
* The code is cleaner.

May be Gary and Simon can take a look again?

Gonzalo

Attached is the patch wth the quit button at the right.


[1] http://people.sugarlabs.org/anish/pippy.png
> [2] http://lists.sugarlabs.org/archive/sugar-devel/2010-July/0My
> arguments  
> are:25756.html
>
> On Wed, Nov 3, 2010 at 8:10 AM, Gonzalo Odiard 
> wrote:
> > This patch modify the last two patches from Anish to enable the use of
> the
> > right toolbars in every Sugar version.
> > There are screenshots here:
> > http://dev.laptop.org/~gonzalo/pippy-in-sugar-0.84.png
> > http://dev.laptop.org/~gonzalo/pippy-in-sugar-0.90.png
> >
> > Gonzalo
> >
> > ___
> > Sugar-devel mailing list
> > Sugar-devel@lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/sugar-devel
> >
> >
>
>
>
> --
> Anish
>



-- 
Gonzalo Odiard
SugarLabs Argentina
From b2149dbb2766c6410c42e9f26fddd18fc0532910 Mon Sep 17 00:00:00 2001
From: Gonzalo Odiard 
Date: Tue, 2 Nov 2010 18:50:47 -0300
Subject: [PATCH] Add EditToolbar and modify toolbars to support the older from sugar < 0.86

---
 groupthink/sugar_tools.py |   23 +--
 pippy_app.py  |   94 +++-
 2 files changed, 101 insertions(+), 16 deletions(-)

diff --git a/groupthink/sugar_tools.py b/groupthink/sugar_tools.py
index 0292a0b..66d4a0e 100644
--- a/groupthink/sugar_tools.py
+++ b/groupthink/sugar_tools.py
@@ -28,6 +28,13 @@ import gobject
 
 import groupthink_base as groupthink
 
+OLD_TOOLBAR = False
+try:
+from sugar.graphics.toolbarbox import ToolbarBox, ToolbarButton
+from sugar.activity.widgets import ActivityToolbarButton
+except ImportError:
+OLD_TOOLBAR = True
+
 def exhaust_event_loop():
 while gtk.events_pending():
 gtk.main_iteration()
@@ -69,11 +76,17 @@ class GroupActivity(Activity):
 else:
 self.message = self.message_preparing
 
-# top toolbar with share and close buttons:
-toolbox = ActivityToolbox(self)
-self.set_toolbox(toolbox)
-toolbox.show()
-
+if OLD_TOOLBAR:
+self.toolbox = ActivityToolbox(self)
+self.set_toolbox(self.toolbox)
+self.toolbox.show()
+self.set_toolbox(self.toolbox)
+else:
+toolbar_box = ToolbarBox()
+self.activity_button = ActivityToolbarButton(self)
+toolbar_box.toolbar.insert(self.activity_button, 0)
+self.set_toolbar_box(toolbar_box)
+
 v = gtk.VBox()
 self.startup_label = gtk.Label(self.message)
 v.pack_start(self.startup_label)
diff --git a/pippy_app.py b/pippy_app.py
index fc8..64e9a46 100644
--- a/pippy_app.py
+++ b/pippy_app.py
@@ -30,9 +30,10 @@ from port.style import font_zoom
 from signal import SIGTERM
 from gettext import gettext as _
 
+from sugar.activity import activity
 from activity import ViewSourceActivity, TARGET_TYPE_TEXT
 from sugar.activity.activity import ActivityToolbox, \
- get_bundle_path, get_bundle_name
+ EditToolbar, get_bundle_path, get_bundle_name
 from sugar.graphics import style
 from sugar.graphics.toolbutton import ToolButton
 
@@ -45,6 +46,13 @@ PYTHON_PREFIX="""#!/usr/bin/python
 # -*- coding: utf-8 -*-
 """
 
+OLD_TOOLBAR = False
+try:
+from sugar.graphics.toolbarbox import ToolbarBox, ToolbarButton
+from sugar.activity.widgets import StopButton
+except ImportError:
+OLD_TOOLBAR = True
+
 # get screen sizes
 SIZE_X = gtk.gdk.screen_width()
 SIZE_Y = gtk.gdk.screen_height()
@@ -62,10 +70,14 @@ class PippyActivity(ViewSourceActivi

Re: [Sugar-devel] GIT.sugarlabs.org changes?

2010-11-03 Thread George Hunt 
I tried the push from another ip address. Same result, so it's probably not
the blacklist problem.

The literature suggests that I should check for world or group writeability
on the path from root to .ssh/known_hosts on the server, and on the client
machine. I have double checked my client. Don't have shell access to server.

George

On Sun, Oct 31, 2010 at 10:30 AM, Aleksey Lim wrote:

> On Sat, Oct 30, 2010 at 07:58:00PM -0400, George Hunt wrote:
> > Hi Aleksey,
> >
> > Thanks for the response.
> >
> > The ssh step fails.  Trying ssh -vvv gitori...@git.sugarlabs.orgindicates
> > that the negotiation proceeds in what looks to be a normal manner, until
> the
> > point where the client determines that public key method is authorized,
> and
> > client is offering my public  key, and the next response is "connection
> > closed".
> >
> > 
> > debug1: Next authentication method: publickey
> > debug1: Offering public key:
> > debug3: send_pubkey_test
> > debug2: we sent a publickey packet, wait for reply
> > Connection closed by 140.211.167.221
> > 
>
> "Connection closed" seems suspiciously. We had problem w/ blacklisting
> of some IPs.
>
> Can you try to ssh connect from different IP?
>
> (I'm CCing it to systems@)
>
> > I guessed that the server has forgotten my public key, so I uploaded it
> > again. I don't know if it is related, but the listserve forgot that I was
> > receiving the "digest" form of the list on Oct 16 or so.
> >
> > After the upload still no luck -- though there may be some form of
> > authorization required and/or delay built in, since when I first uploaded
> my
> > public key last year, it didn't work for at least a day.
> >
> > George
> >
> > On Sat, Oct 30, 2010 at 5:53 PM, Aleksey Lim 
> wrote:
> >
> > > On Sat, Oct 30, 2010 at 05:34:34PM -0400, George Hunt wrote:
> > > > I have 2 projects that I have been pushing git commits to  for almost
> a
> > > > year.  In one I created a new branch, and was concerned that my local
> > > change
> > > > was preventing the successful "git push".  But the other project has
> no
> > > > structural changes, and still gets the response "fatal: the  remote
> end
> > > hung
> > > > up unexpectedly" -- which I see has been a source of lots of
> headaches
> > > for
> > > > the inner circle.
> > > >
> > > > Should I just wait for 6 hours, and try again? How to proceed?
> > >
> > > Check if:
> > >
> > > * `ssh gitori...@git.sugarlabs.org` outputs "PTY allocation request.."
> > > * `git config remote.origin.url` output is equal to particular push
> link
> > >  on your project web page on git.sl.o
> > >
> > > --
> > > Aleksey
> > >
>
> --
> Aleksey
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Appearance Customization

2010-11-03 Thread Hal Murray 

csc...@laptop.org said:
> I'm not certain that editing the existing gtkrc will be sufficient (although
> it would certainly be a good start).  As my history briefly explained, Sugar
> was not designed to be 'colored' in the sorts of ways a kid might want.  (We
> might care whether the text/icons are easily readable; they might not.
> Should we prevent them from doing what they want.) 

Sometimes people learn something when they shoot themselves in the foot.

I assume there is a plan for recovering if a kid breaks something.  How ugly 
is it?  Can a kid do it by themselves, perhaps after a tolerable amount of 
coaching?  (If it happens often enough, perhaps the coaching can come from 
other kids who have done it already.)



-- 
These are my opinions, not necessarily my employer's.  I hate spam.



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

Re: [Sugar-devel] [SoaS] SoaS 4 - Mango Lassi is out.

2010-11-03 Thread Thomas C Gilliard 

Great News;

Fedora-14-x86_64-Live-SoaS CD Boots fine on an Apple MacBook Air with an 
external hp-DVD/CD usb drive.


Hold "C"  and tap power button keep holding the "C" key down until the 
blue fedora boot screen appears

Select Boot (Basic Video)-second line
boots to bar display Fedora 14; (Name_); Choose password for new 
keyring; hit cancel 6 times.

F3 Ring appears

Use the usb to cat 5 Air dongle ( applesmc.78) as Network Manager does 
not recognize the Mac Air's wireless hardware.

f1 neighborhood will be full of xxx...@jabber.sugarlabs.org names

To fix this go to drop down / My settings /About me. change colors and 
restart. On restart the names will be correct.
ONLY IF you enter the key chain password you entered 1 time when you 
started sugar.


These are known bugs
 http://wiki.sugarlabs.org/go/Sugar_on_a_Stick_Bugs#Current_Bugs

ALSO

There is a new Boot CD for Macs and computers that cannot boot from USB

Boot helper CD for Fedora-14-i686-Live-SoaS:



Matt

On Fri, Oct 29, 2010 at 9:45 PM, Matt Wronkiewicz  wrote:
  

> If anyone else is interested, I put together a boot helper for
> Mirabelle. Burned to a CD, it enabled booting a USB stick on my
> MacBook Pro. The stick was partitioned with the plain old MBR format
> and labeled "FEDORA". I also got both VMware Fusion and VirtualBox to
> boot the USB stick using this boot helper ISO. The soas-2-boot ISO
> sort of works with Mirabelle sticks, but they have different kernel
> versions so modules don't load, thus no networking. That is fixed in
> this build.
>
> 
>
> Matt
>


Please Test these result on other MAC's and report here in wiki:

http://wiki.sugarlabs.org/go/Talk:Sugar_on_a_Stick_release_process#Macintosh_Testing

Congratulations to all

Enjoy;

Tom Gilliard
satellit





Peter Robinson wrote:

Hi All,

This is the non announcement announcement of the release of Sugar on a
Stick 4 Mango Lassi is out.

You can download both the 32 and 64 bit version from
http://spins.fedoraproject.org/soas/

There's an outline of some common bugs in Fedora 14 and hence Fedora
14 outlined here
https://fedoraproject.org/wiki/Common_F14_bugs

Some of the notable enhancements include:
- Sugar 0.90
- Support for more wireless adapters including the rtl2xxx series of
adapters that are common in eee PCs
- Improved Apple Mac support (still needs SoaS verification as
apparently its a major problem but I could only find Fedora people to
test it for me)
- Quite a lot of things that I can't remember

I would like to thank Sebastian, Mel, Simon, Thomas and everyone else
who has contributed to this release.

Cheers,
Peter
___
SoaS mailing list
s...@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/soas

  

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