Re: [Sugar-devel] Journal integration for Scratch

[Bert Freudenberg]

The script looks good, except for the name mangling magic (which is a  
bit hard to understand because of mis-indentations). This wouldn't  
even work with your XO's language set to non-English (which the  
majority of XOs use).

I would simply name the file "$object_id.sb".

- Bert -

On 14.01.2009, at 07:04, Philipp Kocher wrote:

> Hi John
>
> Yes, we need the mimetypes.xml file as well (thanks Tomeu I forgot  
> the USB flash drive use case). I have tested the attached  
> mimetypes.xml. It is working fine. Put it in the activity directory.
>
> Furthermore we have to change the scratch-activity script, so the  
> parameter with the scratch project object-id gets converted (copy- 
> from-journal) in a file and passed on to scratch. See the attached  
> scratch-activity script. I am not an expert with bash scripts, so  
> please give feedback.
>
> I would like to extend the script so project files in the journal  
> directory are copied back to the journal after exiting scratch, but  
> for opening project it should work fine.
>
> Best regards,
> Philipp
>
> John Maloney wrote:
>> Hi, Phillip.
>> Thanks for all your hard work in tracking this down. I had looked  
>> at several other packages, including EToys, and couldn't figure out  
>> from them how to do this.
>> I will make these changes to the next XO Scratch bundle.
>> Is that all I need to do? What about the mime types XML file  
>> similar to the one added by Etoys? Does that turn out to be  
>> unnecessary?
>>-- John
>> On Jan 13, 2009, at 12:55 AM, Philipp Kocher wrote:
>>> Tomeu Vizoso wrote:
 On Mon, Jan 12, 2009 at 18:50, Bert Freudenberg >>> > wrote:
> On 12.01.2009, at 18:11, Tomeu Vizoso wrote:
>>> So what would the Scratch activity have to do so files put  
>>> into the
>>> Journal
>>> (maybe by downloading) are displayed using a Scratch icon  
>>> rather than the
>>> generic document icon?
>> Shipping a mimetypes.xml file inside the bundle as explained  
>> here:
>>
>> http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure
>>
>> Sugar will call update-mime-database and will merge that file  
>> into the
>> xdg mime database.
>>
>> I think that John is already trying this.
>
> Guess I'm confused then - I thought that's exactly what Philipp  
> had done.
 I think he just changed the mime_types field in the .info file.
> And I just checked and it does work with Etoys projects. When  
> downloading
> one it indeed gets an etoys icon (although at a smaller size -  
> why is that?)
 No idea, though I think that the mime database is updated in the  
 etoys
 rpm and not in the bundle, am I right?
 Regards,
 Tomeu
>>>
>>> Thanks Tomeu to lead me to the /home/olpc/.local directory.  
>>> However, the
>>> mimetypes.xml is not necessary to get the icon in the journal. I  
>>> just
>>> had to copy the scratch icon file in the activity directory to
>>> "application-x-scratch-project.svg" (also in the scratch activity
>>> dirctory). The Memorize Activity is a good example for using that  
>>> feature.
>>> Sugar has to be restarted after installing Scratch to show the icon.
>>>
>>> John, could you please make the following changes in the next  
>>> Scratch
>>> version:
>>> - add the line "mime_types = application/x-scratch-project" to the
>>> activity.info file
>>> - copy the scratch icon to "application-x-scratch-project.svg" in  
>>> the
>>> activity directory
>>>
>>> Etoys gets configured by different packages. e.g. the rpm
>>> etoys-3.0.2153-1.noarch is adding the file
>>> /usr/share/mime/packges/etoys.xml and the rpm sugar- 
>>> artwork-0.82.3-1.olpc3 is
>>> adding the file
>>> /usr/share/icons/sugar/scalable/mimetypes/application-x-squake- 
>>> project.svg.
>>>
>>> Regards,
>>> Philipp
>>>
> 
> http://www.freedesktop.org/standards/shared-mime-info 
> ">
>   
> Scratch Project
> 
>   
> 
> #!/bin/sh
> # Author: Bert Freudenberg
> # Modified by: John Maloney
> # Purpose: Run Scratch using the Squeak virtual machine
>
> echo "scratch-activity"
> echo "$@"
>
> echo "$0" "$@"
> echo
>
> # arguments are unordered, have to loop
> args=""
> while [ -n "$2" ] ; do
>case "$1" in
>   -b | --bundle-id)   bundle_id="$2"   ; args="$args BUNDLE_ID  
> $2" ;;
>   -a | --activity-id) activity_id="$2" ; args="$args ACTIVITY_ID  
> $2";;
>   -o | --object-id)   object_id="$2"   ; args="$args OBJECT_ID  
> $2";;
>   -u | --uri) uri="$2" ; args="$args URI $2";;
>   *) echo unknown argument $1 $2 ;;
>esac
>shift;shift
> done
>
> # really need bundle id and activity id
> if [ -z "$bundle_id" -o -z "$activity_id" ] ; then
>  echo ERROR: bundle-id and activity-id arguments required
>  echo Aborting
>  exit 1
> fi
>
> # some debug output
> echo launching $bundle_id instance $activity_id
> [ -n "$object_id" ] && echo with journal obj $object_id
> [ -n "$uri"   ] && echo loading uri $

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[David Van Assche]

This sounds like a great foundation for a sugar framework... something
that not only coders can get a feel for...

kind Regards,
David Van Assche

On Wed, Jan 14, 2009 at 6:33 AM, Chris Ball  wrote:
> Hi Ben,
>
>   > Groupthink: Collab should be easy.
>
> (from the patch):
> -self.totranslate = gtk.Entry(max=50)
> +self.cloud.totranslate = groupthink.gtk_tools.RecentEntry(max=50)
>
> .. wow, that *is* easy.  And it's synchronous, so the text box is
> updated with each character press.  You could also use this technique
> for Pippy's source code textbox, which would immediately turn it into a
> collaborative editor.  (I don't care about collisions very much as long
> as everyone gets the same state; they can be resolved socially.)
>
> Now that we're excited, maybe you should let on what the blocker bugs
> are.  :-)
>
> Could we sign you up for a quick XOCamp demo/talk?
>
> Thanks!
>
> - Chris.
> --
> Chris Ball   
> ___
> 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] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Tomeu Vizoso]

Hi Ben,

can we use this on non-sugar pygtk apps?

For example, could we use it to add collaboration features to
Labyrinth (a pygtk app that we are reusing as a Sugar activity)? Or
does it depend on Sugar in any way?

If the data model supported sharing through telepathy tubes, I think
that the upstream GNOME developers would be interested in helping us
maintain this code.

Regards,

Tomeu

On Wed, Jan 14, 2009 at 06:11, Benjamin M. Schwartz
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Groupthink [1] is a development toolkit for collaborative activities.
> It's designed to hide all the collaboration boilerplate and algorithms
> under a clean high-level abstraction, so that Activity developers can
> spend more time on what they really care about.
>
> Groupthink is deeply pre-alpha.  Any application is likely to find a
> multitude of blocker bugs.  If that is acceptable to you, then by all
> means start your experiments.  If you are interested, please ask questions
> or read the code.
>
> As an example of the power of Groupthink, I have created a collaborative
> version of Chris Ball's "Words" activity, a multilingual dictionary.  This
> required adding the groupthink library into the bundle.  It also required
> two patches, attached.  Together, these patches represent a total of 5
> lines changed.  The resulting activity has the main input field shared
> synchronously across all instances.  This activity will be released,
> pending further testing.
>
> Groupthink: Collab should be easy.
>
> - --Ben
>
> [1] http://dev.laptop.org/git?p=projects/dobject;a=summary
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.9 (GNU/Linux)
>
> iEYEARECAAYFAkltdAwACgkQUJT6e6HFtqQ80wCfa4f13gAvJQYcdkhdmefBPBuU
> rYEAoJne2buq5hhC29/4ZFCdVvegBsne
> =aS94
> -END PGP SIGNATURE-
>
> --- activity.py.orig2009-01-12 22:51:15.0 -0500
> +++ activity.py 2009-01-12 23:31:59.0 -0500
> @@ -1,9 +1,11 @@
>  from sugar.activity import activity
>
> -class ViewSourceActivity(activity.Activity):
> +from groupthink.sugar_tools import GroupActivity
> +
> +class ViewSourceActivity(GroupActivity):
> """Activity subclass which handles the 'view source' key."""
> -def __init__(self, handle):
> -super(ViewSourceActivity, self).__init__(handle)
> +def __init__(self, handle, service_name):
> +super(ViewSourceActivity, self).__init__(handle, service_name)
> self.__source_object_id = None # XXX: persist this across invocations?
> self.connect('key-press-event', self._key_press_cb)
> def _key_press_cb(self, widget, event):
>
> --- pippy_app.py.orig   2009-01-13 23:37:25.0 -0500
> +++ pippy_app.py2009-01-13 00:13:49.0 -0500
> @@ -28,6 +28,8 @@
>  from sugar.activity.activity import ActivityToolbox, \
>  get_bundle_path, get_bundle_name
>
> +import groupthink.gtk_tools
> +
>  SERVICE = "org.laptop.Words"
>  IFACE = SERVICE
>  PATH = "/org/laptop/Words"
> @@ -36,7 +38,7 @@
> """Words Activity as specified in activity.info"""
> def __init__(self, handle):
> """Set up the Words activity."""
> -super(WordsActivity, self).__init__(handle)
> +super(WordsActivity, self).__init__(handle, SERVICE)
> self._logger = logging.getLogger('words-activity')
>
> from sugar.graphics.menuitem import MenuItem
> @@ -69,7 +71,8 @@
> label2 = gtk.Label("Translation")
>
> # Text entry box to enter word to be translated.
> -self.totranslate = gtk.Entry(max=50)
> +self.cloud.totranslate = groupthink.gtk_tools.RecentEntry(max=50)
> +self.totranslate = self.cloud.totranslate
> self.totranslate.connect("changed", self.totranslate_cb)
> self.totranslate.modify_font(pango.FontDescription("Sans 14"))
>
>
> ___
> 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] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Benjamin M. Schwartz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Chris Ball wrote:

> .. wow, that *is* easy.

Thank you!

> Now that we're excited, maybe you should let on what the blocker bugs
> are.  :-)

The best way I can put it is: I spent two hours fixing bug after bug
before this use case worked.  Any other codepath will probably need the
same treatment.  I'm really not a very good programmer, and there's not
much in the way of a test suite.  (That would be nice, some day.)

> Could we sign you up for a quick XOCamp demo/talk?

Unfortunately, it seems like its all scheduled during the work day.  I'd
feel a bit bad skipping work.

- --Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAklt7pEACgkQUJT6e6HFtqTbUACfS1yAyobwe9h5iCr9qRJ16APp
4LQAnRogo08FABOo2Dl2an4nO77494TB
=ZzID
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Python-based window manager?

[Jonas Smedegaard]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

I believe there was some discussion earlier on regarding dealing with 
core X11 from Python. And regading the choice of window manager used 
for Sugar.

Are you aware of python-xlib[1] and The Pointless Window Manager[2]?


(no, I do not intend to hack together some proof of concept - I do 
packaging not coding, and just stumbled across a Debian update of these 
today).


Kind regards,

  - Jonas


[1] http://python-xlib.sourceforge.net/

[2] http://plwm.sourceforge.net/

- -- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  [x] quote me freely  [ ] ask before reusing  [ ] keep private
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAklt8ZoACgkQn7DbMsAkQLg9hQCfS85ySDUwkJN4s6W9YSQmsUfK
fVoAoIc2foDGYdLSAVDMa5F3+HwyY4KL
=L5VK
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Benjamin M. Schwartz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tomeu Vizoso wrote:
> can we use this on non-sugar pygtk apps?

Yes.  Groupthink's only hard dependency is on dbus.  It also has optional
dependencies on Sugar and GTK.

> For example, could we use it to add collaboration features to
> Labyrinth (a pygtk app that we are reusing as a Sugar activity)? Or
> does it depend on Sugar in any way?

Groupthink provides a GroupActivity class which Sugar activities can
subclass.  GroupActivity contains all the boilerplate necessary to
negotiate with Telepathy, acquire a tube, notify shared objects that
sharing has occurred, etc.  If you're not running Sugar then you have to
somehow acquire a Telepathy D-Bus Tube on your own, but other than that
Groupthink should be totally usable.

> If the data model supported sharing through telepathy tubes, I think
> that the upstream GNOME developers would be interested in helping us
> maintain this code.

I would certainly love any help in maintenance/development.  I have no
training and no experience in network algorithms or framework design, and
I can think of many flaws in the current implementation that I don't
really know how to fix.  I do think that this concept could be useful
outside of Sugar.

- --Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAklt8rEACgkQUJT6e6HFtqQ80wCaAuIKyek0ldnu91oxXkIBUJGI
Fi8An06J9GfTXA4GPLArry+inUORPhrA
=HtLM
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] Cerebro v3.0: File sharing and buddy management made easy!

[Polychronis Ypodimatopoulos]

Want to exchange files between your desktop and your XO laptop? It can't 
get any easier!

In the latest version of Cerebro (currently 3.0.3) you will find 
simplified file sharing and buddy management. Just click on the buddy 
you want to send a file to and select a file to send! Screenshots are here:
http://cerebro.mit.edu/index.php/Documentation#Example_GUI

If you are a developer, there is detailed tutorial to do file sharing 
from Python prompt (!) here:
http://cerebro.mit.edu/index.php/Documentation#Buddy_management

Enjoy
Pol


-- 
Polychronis Ypodimatopoulos
Graduate student
Viral Communications
MIT Media Lab
Tel: +1 (617) 459-6058
http://www.mit.edu/~ypod/

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

Re: [Sugar-devel] ActivityTeam proposal

[Brian Jordan]

+1!

git commit -a
iWOO collaborative development!:wq
git push

On Sat, Jan 10, 2009 at 1:46 PM, Wade Brainerd  wrote:
> Hi all, hope you are enjoying FUDcon.
>
> Given the recent events at OLPC, I'm planning to refocus my activity
> development efforts on SugarLabs.  I imagine other activity developers
> are planning to do the same.
>
> SugarLabs is off to a great start getting packages into distributions,
> but I can't help noticing that the activities on the home page are
> essentially the same were shipped with OLPC build 650 back in 2007.
>
> One of the things that drew me to Sugar and OLPC was the promise of
> high quality, collaborative, constructivist educational software.
> While the initial activity set was good, it was also clear that there
> were large holes to be filled.  For a variety reasons, many of those
> holes remain two years later.
>
> And that's why I'm proposing the creation of a SugarLabs ActivityTeam.
>  The new team will be separate from the DevelopmentTeam, and will have
> the responsibility of maintaining and extending the suite of
> activities available for Sugar.
>
> We will:
> 1. Maintain and develop the current suite of Sugar activities.
> 2. Recruit and mentor activity developers from the community.
> 3. Collect, document and organize new activity and activity feature
> ideas from the EducationTeam, deployments and community.
> 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure
> activity developers are well supported.
> 5. Gather feedback with the DeploymentTeam about how Sugar activities
> are doing in the field.
>
> Until now, activity development has largely been an individual effort.
>  The purpose of this proposal is to collect the activity development
> community into an effective team who can tackle the entire ecosystem
> of Sugar activities together.  One result should be fewer activities
> "dropping off the radar" into lack of maintenance.
>
> Please respond with your feedback about the proposal.  If you like the
> idea and would like to be part of the ATeam, feel free to indicate
> that.
>
> Best,
> Wade
> ___
> 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] Journal integration for Scratch

[John Maloney]

Hi, Phillip.

Thanks for all your hard work in tracking this down. I had looked at  
several other packages, including EToys, and couldn't figure out from  
them how to do this.

I will make these changes to the next XO Scratch bundle.

Is that all I need to do? What about the mime types XML file similar  
to the one added by Etoys? Does that turn out to be unnecessary?

-- John


On Jan 13, 2009, at 12:55 AM, Philipp Kocher wrote:
> Tomeu Vizoso wrote:
>> On Mon, Jan 12, 2009 at 18:50, Bert Freudenberg  
>>  wrote:
>>> On 12.01.2009, at 18:11, Tomeu Vizoso wrote:
> So what would the Scratch activity have to do so files put into  
> the
> Journal
> (maybe by downloading) are displayed using a Scratch icon rather  
> than the
> generic document icon?
 Shipping a mimetypes.xml file inside the bundle as explained here:

 http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure

 Sugar will call update-mime-database and will merge that file  
 into the
 xdg mime database.

 I think that John is already trying this.
>>>
>>> Guess I'm confused then - I thought that's exactly what Philipp  
>>> had done.
>> I think he just changed the mime_types field in the .info file.
>>> And I just checked and it does work with Etoys projects. When  
>>> downloading
>>> one it indeed gets an etoys icon (although at a smaller size - why  
>>> is that?)
>> No idea, though I think that the mime database is updated in the  
>> etoys
>> rpm and not in the bundle, am I right?
>> Regards,
>> Tomeu
>
> Thanks Tomeu to lead me to the /home/olpc/.local directory. However,  
> the
> mimetypes.xml is not necessary to get the icon in the journal. I just
> had to copy the scratch icon file in the activity directory to
> "application-x-scratch-project.svg" (also in the scratch activity
> dirctory). The Memorize Activity is a good example for using that  
> feature.
> Sugar has to be restarted after installing Scratch to show the icon.
>
> John, could you please make the following changes in the next Scratch
> version:
> - add the line "mime_types = application/x-scratch-project" to the
> activity.info file
> - copy the scratch icon to "application-x-scratch-project.svg" in the
> activity directory
>
> Etoys gets configured by different packages. e.g. the rpm
> etoys-3.0.2153-1.noarch is adding the file
> /usr/share/mime/packges/etoys.xml and the rpm sugar- 
> artwork-0.82.3-1.olpc3 is
> adding the file
> /usr/share/icons/sugar/scalable/mimetypes/application-x-squake- 
> project.svg.
>
> Regards,
> Philipp
>

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

Re: [Sugar-devel] Activities migration status

[S Page]

Rafael Enrique Ortiz Guerrero wrote:

> Today I went through dev.laptop.org/git 
> identifying those projects
> that contain Sugar activities.
> 
> http://sugarlabs.org/go/ActivityTeam/ActivityStatus
> 
> Still remaining is to go through Activities/All (and code.google.com
> ,
> personal sites, etc) and find those activities which do not have d.l.o
> repositories.
> 
> The list is *massive*.  I had no idea we had so many cool activities
> in various stages of development! 

I'm not sure what you're doing, but if you want activities...
When the call went out for activities for 9.1.0 I put all the meta-lists 
of activities in


That links to some interesting queries in 
http://wiki.laptop.org/go/Activity_queries  :
* 45 pages with a Devel status
* 116 pages that appear to have an activity bundle
* 310 pages in Category:Activities in the main namespace.

and I'm sure there are more activities that lack a page on on 
wiki.laptop.org

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

[Sugar-devel] p2p stream tubes

[Guillaume Desmottes]

Hi guys,

I released telepathy-gabble 0.7.18 yesterday which implements a
long-awaited feature: peer to peer connections in stream tubes!

Basically this means that stream tubes will use a TCP connection (using
SOCKS 5) to transfer their data instead of sending them through the
server with IBB (base64 encoding). If the socks5 connection can't be
established (because peers are on different NAT's for example) then
Gabble will fallback to IBB.
This should drastically improve stream tube performances and reduce
server's band-with consumption.

As all of this is pure Telepathy implementation details, activities
using stream tubes (as Read) doesn't have to change a single line of
their code to benefit of this improvement! Clients just have to upgrade
their Gabble.

Of course, there are probably bugs in the current implementation so it
would be good if Sugar users could start to test it ASAP.
We should observe the following results in these scenario:

- old Gabble <-> new Gabble: continue to use IBB as before.
- new Gabble <-> new Gabble on the same network: use sock5 connections
(the transfer of the shared document in Read should be really faster)
- new Gabble <-> new Gabble on different networks: try to use sock5 and
the fallback to IBB.

This is the first step in our "improve tubes connectivity" plan and lead
the way to new improvements as using a socks5 relay to transfer data if
direct connection is impossible. The ultimate goal is to use jingle to
benefit real NAT penetration (as in audio/video calls).

Please feel free to test this new version and report any problem you
could have.


Regards,


G.

[1]
http://lists.freedesktop.org/archives/telepathy/2009-January/002734.html


-- 
Guillaume Desmottes 
Jabber 
GPG 1024D/711E31B1 | 1B5A 1BA8 11AA F0F1 2169  E28A AC55 8671 711E 31B1


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

Re: [Sugar-devel] [OLPC-GSoC] Fwd: Google Summer of Code 2009 is a go!

[Sharon Lally]

SJ, it sounds like a good planbut  OLPC/1CC had problems retaining
mentors last year, so make sure not to over-commit.  The remaining OLPC
staff may not have time to mentor.
Sharon



On Thu, Jan 8, 2009 at 7:10 PM, Samuel Klein  wrote:

> I'm copying our own gsoc list, and glad to clarify how this should work.
>
> I mentioned to Leslie yesterday that I expected SugarLabs and OLPC
> might have  separate GSOC projects this year.  Someone representing SL
> should write and formally get on their list of supported
> organizations.  [note: this requires tax/ID information for SL]
>
> OLPC is interested in participating in GSOC this year... some of the
> projects I imagine would be activities or software for creation that
> would work particularly with the XO's hardware, or would help needs in
>  OLPC deployments.
>
> It would be alright for both SugarLabs and OLPC to have people working
> on code that could be integrated into Sugar (note the different
> activity-development and python coding that was done both as an OLPC
> SoC project and via other orgs who wanted their projects to be useful
> to OLPC as an audience).  It is also possible to submit an application
> to more than one organization.
>
> I recommend noting in our organization descriptions (and definition of
> what we are looking for) that people who want to develop tools and
> features for Sugar should apply to SL, and people who want to develop
> things specifically for OLPC deployments, or other software puzzles
> specific to XOs, should apply to OLPC.
>
> I would encourage most activity developers and activity mentors to
> tackle SoC projects under sugarlabs...
>
> SJ
>
>
> On Thu, Jan 8, 2009 at 5:26 PM, Ed McNierney  wrote:
> > Yes, but in 2007 "they" were "us", no?
> >
> > Thanks, this is helpful information (I didn't know the status of
> > OLPC's previous GSoC work).  I don't see why there is any reason to
> > presume that OLPC would NOT be interested in 2009 GSoC, but I don't
> > know of any active ideas/proposals kicking around here.  I would
> > strongly encourage Sugar Labs ideas, however - to Ben's point, there
> > should be no confusion.  The only things I could imagine (and it's
> > just imagining) coming from OLPC would be ancillary ideas (school
> > server add-ons?) that would be quite distinct from XO/Sugar software.
> > Go for it!
> >
> >- Ed
> >
> >
> > On Jan 8, 2009, at 3:54 PM, Wade Brainerd wrote:
> >
> >> On Thu, Jan 8, 2009 at 3:50 PM, Tomeu Vizoso 
> >> wrote:
> >>> We should take into account that organizations are assigned slots
> >>> based on their well behaviour in past editions.
> >>
> >> To be clear, OLPC was put on GSoC 'probation' last year due to their
> >> poor performance reporting on students' work in 2007.  They only
> >> received 4 slots despite hundreds of applications.
> >>
> >> Wade
> >> ___
> >> 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
> >
> ___
> Gsoc mailing list
> g...@lists.laptop.org
> http://lists.laptop.org/listinfo/gsoc
>



-- 
Sharon Lally
Director, Human Resources
One Laptop Per Child
617.452.5680
sha...@laptop.org
www.laptop.org


Give a Laptop. Get a Laptop.  Change the world!  Visit
http://www.laptop.org/en/ for more information.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [OLPC-GSoC] Fwd: Google Summer of Code 2009 is a go!

[Alex Levenson]

Don't forget community mentors!

On Fri, Jan 9, 2009 at 11:40 AM, Sharon Lally  wrote:

>
> SJ, it sounds like a good planbut  OLPC/1CC had problems retaining
> mentors last year, so make sure not to over-commit.  The remaining OLPC
> staff may not have time to mentor.
> Sharon
>
>
>
>
> On Thu, Jan 8, 2009 at 7:10 PM, Samuel Klein  wrote:
>
>> I'm copying our own gsoc list, and glad to clarify how this should work.
>>
>> I mentioned to Leslie yesterday that I expected SugarLabs and OLPC
>> might have  separate GSOC projects this year.  Someone representing SL
>> should write and formally get on their list of supported
>> organizations.  [note: this requires tax/ID information for SL]
>>
>> OLPC is interested in participating in GSOC this year... some of the
>> projects I imagine would be activities or software for creation that
>> would work particularly with the XO's hardware, or would help needs in
>>  OLPC deployments.
>>
>> It would be alright for both SugarLabs and OLPC to have people working
>> on code that could be integrated into Sugar (note the different
>> activity-development and python coding that was done both as an OLPC
>> SoC project and via other orgs who wanted their projects to be useful
>> to OLPC as an audience).  It is also possible to submit an application
>> to more than one organization.
>>
>> I recommend noting in our organization descriptions (and definition of
>> what we are looking for) that people who want to develop tools and
>> features for Sugar should apply to SL, and people who want to develop
>> things specifically for OLPC deployments, or other software puzzles
>> specific to XOs, should apply to OLPC.
>>
>> I would encourage most activity developers and activity mentors to
>> tackle SoC projects under sugarlabs...
>>
>> SJ
>>
>>
>> On Thu, Jan 8, 2009 at 5:26 PM, Ed McNierney  wrote:
>> > Yes, but in 2007 "they" were "us", no?
>> >
>> > Thanks, this is helpful information (I didn't know the status of
>> > OLPC's previous GSoC work).  I don't see why there is any reason to
>> > presume that OLPC would NOT be interested in 2009 GSoC, but I don't
>> > know of any active ideas/proposals kicking around here.  I would
>> > strongly encourage Sugar Labs ideas, however - to Ben's point, there
>> > should be no confusion.  The only things I could imagine (and it's
>> > just imagining) coming from OLPC would be ancillary ideas (school
>> > server add-ons?) that would be quite distinct from XO/Sugar software.
>> > Go for it!
>> >
>> >- Ed
>> >
>> >
>> > On Jan 8, 2009, at 3:54 PM, Wade Brainerd wrote:
>> >
>> >> On Thu, Jan 8, 2009 at 3:50 PM, Tomeu Vizoso 
>> >> wrote:
>> >>> We should take into account that organizations are assigned slots
>> >>> based on their well behaviour in past editions.
>> >>
>> >> To be clear, OLPC was put on GSoC 'probation' last year due to their
>> >> poor performance reporting on students' work in 2007.  They only
>> >> received 4 slots despite hundreds of applications.
>> >>
>> >> Wade
>> >> ___
>> >> 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
>> >
>> ___
>> Gsoc mailing list
>> g...@lists.laptop.org
>> http://lists.laptop.org/listinfo/gsoc
>>
>
>
>
> --
> Sharon Lally
> Director, Human Resources
> One Laptop Per Child
> 617.452.5680
> sha...@laptop.org
> www.laptop.org
>
>
> Give a Laptop. Get a Laptop.  Change the world!  Visit
> http://www.laptop.org/en/ for more information.
>
> ___
> Gsoc mailing list
> g...@lists.laptop.org
> http://lists.laptop.org/listinfo/gsoc
>
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [OLPC-GSoC] Fwd: Google Summer of Code 2009 is a go!

[Sharon Lally]

We should never forget them.  Good job folks.
Sharon

On Fri, Jan 9, 2009 at 2:15 PM, Alex Levenson wrote:

> Don't forget community mentors!
>
>
> On Fri, Jan 9, 2009 at 11:40 AM, Sharon Lally  wrote:
>
>>
>> SJ, it sounds like a good planbut  OLPC/1CC had problems retaining
>> mentors last year, so make sure not to over-commit.  The remaining OLPC
>> staff may not have time to mentor.
>> Sharon
>>
>>
>>
>>
>> On Thu, Jan 8, 2009 at 7:10 PM, Samuel Klein  wrote:
>>
>>> I'm copying our own gsoc list, and glad to clarify how this should work.
>>>
>>> I mentioned to Leslie yesterday that I expected SugarLabs and OLPC
>>> might have  separate GSOC projects this year.  Someone representing SL
>>> should write and formally get on their list of supported
>>> organizations.  [note: this requires tax/ID information for SL]
>>>
>>> OLPC is interested in participating in GSOC this year... some of the
>>> projects I imagine would be activities or software for creation that
>>> would work particularly with the XO's hardware, or would help needs in
>>>  OLPC deployments.
>>>
>>> It would be alright for both SugarLabs and OLPC to have people working
>>> on code that could be integrated into Sugar (note the different
>>> activity-development and python coding that was done both as an OLPC
>>> SoC project and via other orgs who wanted their projects to be useful
>>> to OLPC as an audience).  It is also possible to submit an application
>>> to more than one organization.
>>>
>>> I recommend noting in our organization descriptions (and definition of
>>> what we are looking for) that people who want to develop tools and
>>> features for Sugar should apply to SL, and people who want to develop
>>> things specifically for OLPC deployments, or other software puzzles
>>> specific to XOs, should apply to OLPC.
>>>
>>> I would encourage most activity developers and activity mentors to
>>> tackle SoC projects under sugarlabs...
>>>
>>> SJ
>>>
>>>
>>> On Thu, Jan 8, 2009 at 5:26 PM, Ed McNierney  wrote:
>>> > Yes, but in 2007 "they" were "us", no?
>>> >
>>> > Thanks, this is helpful information (I didn't know the status of
>>> > OLPC's previous GSoC work).  I don't see why there is any reason to
>>> > presume that OLPC would NOT be interested in 2009 GSoC, but I don't
>>> > know of any active ideas/proposals kicking around here.  I would
>>> > strongly encourage Sugar Labs ideas, however - to Ben's point, there
>>> > should be no confusion.  The only things I could imagine (and it's
>>> > just imagining) coming from OLPC would be ancillary ideas (school
>>> > server add-ons?) that would be quite distinct from XO/Sugar software.
>>> > Go for it!
>>> >
>>> >- Ed
>>> >
>>> >
>>> > On Jan 8, 2009, at 3:54 PM, Wade Brainerd wrote:
>>> >
>>> >> On Thu, Jan 8, 2009 at 3:50 PM, Tomeu Vizoso 
>>> >> wrote:
>>> >>> We should take into account that organizations are assigned slots
>>> >>> based on their well behaviour in past editions.
>>> >>
>>> >> To be clear, OLPC was put on GSoC 'probation' last year due to their
>>> >> poor performance reporting on students' work in 2007.  They only
>>> >> received 4 slots despite hundreds of applications.
>>> >>
>>> >> Wade
>>> >> ___
>>> >> 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
>>> >
>>> ___
>>> Gsoc mailing list
>>> g...@lists.laptop.org
>>> http://lists.laptop.org/listinfo/gsoc
>>>
>>
>>
>>
>> --
>> Sharon Lally
>> Director, Human Resources
>> One Laptop Per Child
>> 617.452.5680
>> sha...@laptop.org
>> www.laptop.org
>>
>>
>> Give a Laptop. Get a Laptop.  Change the world!  Visit
>> http://www.laptop.org/en/ for more information.
>>
>> ___
>> Gsoc mailing list
>> g...@lists.laptop.org
>> http://lists.laptop.org/listinfo/gsoc
>>
>>
>


-- 
Sharon Lally
Director, Human Resources
One Laptop Per Child
617.452.5680
sha...@laptop.org
www.laptop.org


Give a Laptop. Get a Laptop.  Change the world!  Visit
http://www.laptop.org/en/ for more information.
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [Testing] Testing summary - 10 January 2009

[Mohit Taneja]

Thanks Tomeu,I would definitely like to attend something like that.

Regards,
Mohit Taneja

On Sun, Jan 11, 2009 at 9:44 PM, Tomeu Vizoso  wrote:

> On Sat, Jan 10, 2009 at 06:31, Mohit Taneja  wrote:
> >> Food Force II
> >>
> >> Tested on 5 XOS, concept awesome and appropriate for developing
> countries
> >> (keep working on it please), takes a long time to load - uses a lot of
> >> processing power so runs real slow, shares in neighbourbood view but
> does
> >> not collaborate. Usability - ignoring slowness, the edges of the screen
> are
> >> designed to move the user view of the village but the selection buttons
> at
> >> the bottom of the screen are within the scroll trigger zone so when
> trying
> >> to select it is scrolling. Would be good if there was a "where you are
> now"
> >> indicator on the map (for when you have scrolled away from the village).
> >> Query - would speed increase if run from school server rather than
> local? We
> >> are extremely excited about this activity and look forward to seeing
> this
> >> improve.
> >
> > Hi,
> > I would firstly like to thank you guys for your comments.
> > Well definitely, I accept that moving the screen by making the mouse go
> > towards the edges is a problem, one reaason being that the control
> buttons
> > are within their range also in some cases it leads to the frame being
> showed
> > when one takes the mouse pointer to a particular edge. We would work on
> > making the requisite changes.
> > Also, it would be great to show the exact location of the player on the
> mini
> > map (right hand side - middle ).
> > And surely working on efficiency is always a priority.
>
> If the SugarLabs's activity team would like to schedule an irc session
> about performance, I'd be glad to share the tricks I have learnt
> during the last two years.
>
> Regards,
>
> Tomeu
>
> > Regards,
> > Mohit Taneja
> > Developer
> > Food Force II
> >
> > On Sat, Jan 10, 2009 at 6:17 AM, Tabitha Roder 
> > wrote:
> >>
> >> Hello
> >>
> >> Thanks to Ian Thomson for coming along and talking to everyone about
> >> Oceania deployments. There were lots of fantastic talks today with a
> diverse
> >> group of people present. We are hoping to hear some kiwi's could be
> >> volunteering in the Pacific Islands over the next few months - fingers
> >> crossed funds can be found.
> >>
> >> Who came: Carl, Ian, Edward, Murray, Brenda, Callum, Uli, Jonathan,
> Kaleb,
> >> Joshhua, Aida, Tabitha, Aaron, Douglas, Queenie
> >>
> >> Food Force II
> >> Tested on 5 XOS, concept awesome and appropriate for developing
> countries
> >> (keep working on it please), takes a long time to load - uses a lot of
> >> processing power so runs real slow, shares in neighbourbood view but
> does
> >> not collaborate. Usability - ignoring slowness, the edges of the screen
> are
> >> designed to move the user view of the village but the selection buttons
> at
> >> the bottom of the screen are within the scroll trigger zone so when
> trying
> >> to select it is scrolling. Would be good if there was a "where you are
> now"
> >> indicator on the map (for when you have scrolled away from the village).
> >> Query - would speed increase if run from school server rather than
> local? We
> >> are extremely excited about this activity and look forward to seeing
> this
> >> improve.
> >>
> >> Chat
> >> Today we had bonjour chat on Ubuntu (pidgin on 8.10 and 8.4) talking to
> >> the XOs without issue. Intiating a chat from Ubuntu to the XOs would pop
> up
> >> a chat icon, which clicking on would start a Chat application. However,
> a OS
> >> X macbook with (using ichat bonjour) could see the XO's, but would
> return
> >> the error message "Instant Message connection failed. The other person's
> >> computer may not be reachable." Also, there is no way for an XO to
> initiate
> >> a chat, or see non-XO computers using the bonjour chat protocol.
> >>
> >> Plans for next couple of weeks -
> >> Next Saturday 17 January - learn how to pull apart your XO and put it
> back
> >> together (thanks Callum, our resident expert in XO repairs) - at The
> Cross
> >> Tuesday 27 January - meet Walter Bender, SugarLabs founder - further
> >> details to come but can say it will be at Catalyst offices in Willis
> Street
> >> One day soon - update from Andrew McMillan on OLPC presentations at
> Linux
> >> Conference (February?)
> >> One day soon - Martin Langhoff update on School server and python for
> >> sugar programming sessions (February?)
> >>
> >> Feel free to invite others.
> >>
> >> To keep up to date with what the New Zealand OLPC volunteers are doing,
> >> subscribe to olpc...@lists.laptop.org by going to
> >> http://lists.laptop.org/listinfo/olpc-nz
> >>
> >> Have a fantastic week!
> >>
> >> Kind regards
> >> Tabitha Roder
> >>
> >> (64)21482229
> >>
> >> Support OLPC G1G1 - laptop.org/xo
> >>
> >> ___
> >> Testing mailing list
> >> test...@lists.laptop.org
> >> http://lists.laptop.org/li

Re: [Sugar-devel] Journal integration for Scratch

[Philipp Kocher]

Tomeu Vizoso wrote:
> On Mon, Jan 12, 2009 at 18:50, Bert Freudenberg  wrote:
>> On 12.01.2009, at 18:11, Tomeu Vizoso wrote:
 So what would the Scratch activity have to do so files put into the
 Journal
 (maybe by downloading) are displayed using a Scratch icon rather than the
 generic document icon?
>>> Shipping a mimetypes.xml file inside the bundle as explained here:
>>>
>>> http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure
>>>
>>> Sugar will call update-mime-database and will merge that file into the
>>> xdg mime database.
>>>
>>> I think that John is already trying this.
>>
>> Guess I'm confused then - I thought that's exactly what Philipp had done.
> 
> I think he just changed the mime_types field in the .info file.
> 
>> And I just checked and it does work with Etoys projects. When downloading
>> one it indeed gets an etoys icon (although at a smaller size - why is that?)
> 
> No idea, though I think that the mime database is updated in the etoys
> rpm and not in the bundle, am I right?
> 
> Regards,
> 
> Tomeu
> 

Thanks Tomeu to lead me to the /home/olpc/.local directory. However, the
mimetypes.xml is not necessary to get the icon in the journal. I just
had to copy the scratch icon file in the activity directory to
"application-x-scratch-project.svg" (also in the scratch activity
dirctory). The Memorize Activity is a good example for using that feature.
Sugar has to be restarted after installing Scratch to show the icon.

John, could you please make the following changes in the next Scratch
version:
- add the line "mime_types = application/x-scratch-project" to the
activity.info file
- copy the scratch icon to "application-x-scratch-project.svg" in the
activity directory

Etoys gets configured by different packages. e.g. the rpm
etoys-3.0.2153-1.noarch is adding the file
/usr/share/mime/packges/etoys.xml and the rpm 
sugar-artwork-0.82.3-1.olpc3 is
adding the file
/usr/share/icons/sugar/scalable/mimetypes/application-x-squake-project.svg.

Regards,
Philipp

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

Re: [Sugar-devel] [Olpc-open] Mitra's talk on hole in the wall

[Charbax]

Hi, just wanted to say that i was there in Geneva at the Lift conference at
Sugata Mitra's talk. I was filming video interviews for
http://techvideoblog.com/category/lift/
I remember I approached Sugata Mitra after his talk to ask him what he
thought about the OLPC project. I am not sure I understood what he had to
say about OLPC or perhaps I just don't remember it clearly. But I think he
wasn't totally enthusiastic about OLPC which I thought was weird.

But I guess that he is researching some other angle on the problem.

Anyways, I hoe that with Obama that OLPC can hurry up and fix all the worlds
problems. Cause the Children are growing older without a much better
education system that they deserve. And I am thinking the problem is not
only in poor countries, although their problem obvisously is the biggest, I
think that all Children in all countries are waiting for the school system
to be made better. And that I think is using computers and the Internet in a
clever way.

On Wed, Jan 14, 2009 at 6:27 AM, Sameer Verma  wrote:

> Just saw Sugata Mitra's talk at Lift (http://liftconference.com/) on
> the hole-in-the-wall experiment and the data they collected. Most
> impressive was the concept of self-organized learning that happened in
> these places.
> http://www.ted.com/index.php/talks/sugata_mitra_shows_how_kids_teach_themselves.html
> It goes against all the talk about teacher training, etc.
>
> Sameer
> --
> Dr. Sameer Verma, Ph.D.
> Associate Professor of Information Systems
> San Francisco State University
> San Francisco CA 94132 USA
> http://verma.sfsu.edu/
> http://opensource.sfsu.edu/
> ___
> Olpc-open mailing list
> olpc-o...@lists.laptop.org
> http://lists.laptop.org/listinfo/olpc-open
>



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

Re: [Sugar-devel] Journal integration for Scratch

[Philipp Kocher]

Hi John

Yes, we need the mimetypes.xml file as well (thanks Tomeu I forgot the 
USB flash drive use case). I have tested the attached mimetypes.xml. It 
is working fine. Put it in the activity directory.


Furthermore we have to change the scratch-activity script, so the 
parameter with the scratch project object-id gets converted 
(copy-from-journal) in a file and passed on to scratch. See the attached 
scratch-activity script. I am not an expert with bash scripts, so please 
give feedback.


I would like to extend the script so project files in the journal 
directory are copied back to the journal after exiting scratch, but for 
opening project it should work fine.


Best regards,
Philipp

John Maloney wrote:

Hi, Phillip.

Thanks for all your hard work in tracking this down. I had looked at 
several other packages, including EToys, and couldn't figure out from 
them how to do this.


I will make these changes to the next XO Scratch bundle.

Is that all I need to do? What about the mime types XML file similar to 
the one added by Etoys? Does that turn out to be unnecessary?


-- John


On Jan 13, 2009, at 12:55 AM, Philipp Kocher wrote:

Tomeu Vizoso wrote:
On Mon, Jan 12, 2009 at 18:50, Bert Freudenberg 
 wrote:

On 12.01.2009, at 18:11, Tomeu Vizoso wrote:

So what would the Scratch activity have to do so files put into the
Journal
(maybe by downloading) are displayed using a Scratch icon rather 
than the

generic document icon?

Shipping a mimetypes.xml file inside the bundle as explained here:

http://wiki.laptop.org/go/Activity_bundles#Bundle_Structure

Sugar will call update-mime-database and will merge that file into the
xdg mime database.

I think that John is already trying this.


Guess I'm confused then - I thought that's exactly what Philipp had 
done.

I think he just changed the mime_types field in the .info file.
And I just checked and it does work with Etoys projects. When 
downloading
one it indeed gets an etoys icon (although at a smaller size - why 
is that?)

No idea, though I think that the mime database is updated in the etoys
rpm and not in the bundle, am I right?
Regards,
Tomeu


Thanks Tomeu to lead me to the /home/olpc/.local directory. However, the
mimetypes.xml is not necessary to get the icon in the journal. I just
had to copy the scratch icon file in the activity directory to
"application-x-scratch-project.svg" (also in the scratch activity
dirctory). The Memorize Activity is a good example for using that 
feature.

Sugar has to be restarted after installing Scratch to show the icon.

John, could you please make the following changes in the next Scratch
version:
- add the line "mime_types = application/x-scratch-project" to the
activity.info file
- copy the scratch icon to "application-x-scratch-project.svg" in the
activity directory

Etoys gets configured by different packages. e.g. the rpm
etoys-3.0.2153-1.noarch is adding the file
/usr/share/mime/packges/etoys.xml and the rpm 
sugar-artwork-0.82.3-1.olpc3 is

adding the file
/usr/share/icons/sugar/scalable/mimetypes/application-x-squake-project.svg. 



Regards,
Philipp




http://www.freedesktop.org/standards/shared-mime-info";>
   
 Scratch Project
 
   

#!/bin/sh
# Author: Bert Freudenberg
# Modified by: John Maloney
# Purpose: Run Scratch using the Squeak virtual machine

echo "scratch-activity"
echo "$@"

echo "$0" "$@"
echo

# arguments are unordered, have to loop
args=""
while [ -n "$2" ] ; do
case "$1" in
-b | --bundle-id)   bundle_id="$2"   ; args="$args BUNDLE_ID $2" ;;
-a | --activity-id) activity_id="$2" ; args="$args ACTIVITY_ID $2";;
-o | --object-id)   object_id="$2"   ; args="$args OBJECT_ID $2";;
-u | --uri) uri="$2" ; args="$args URI $2";;
*) echo unknown argument $1 $2 ;;
esac
shift;shift
done

# really need bundle id and activity id
if [ -z "$bundle_id" -o -z "$activity_id" ] ; then
  echo ERROR: bundle-id and activity-id arguments required
  echo Aborting
  exit 1
fi

# some debug output
echo launching $bundle_id instance $activity_id
[ -n "$object_id" ] && echo with journal obj $object_id
[ -n "$uri"   ] && echo loading uri $uri
echo

# do not crash on dbus errors
export DBUS_FATAL_WARNINGS=0

if [ -n "$object_id" ] ; then
JOURNAL_DIR="$SUGAR_ACTIVITY_ROOT/data/Journal"
mkdir -p "$JOURNAL_DIR"
temp_filename="$JOURNAL_DIR/temp.sb"
title=`copy-from-journal -o "$object_id" -m "$temp_filename" | grep 
"title "`
# title is something like this for files downloaded from server:
#   title -> File do_math_3.sb from 
http://schoolserver/Scratch/do_math_3.sb.
# or like this if copied from USB flash drive:
#   title -> do_math_3
title=${title#*"title -> "} #cut off description
echo "title: $title"

# workaround for copy-from-journal bug (adds another dot before 
fileextension)
if [ -f "$JOURNAL_DIR/temp..sb" ] ; then
   

Re: [Sugar-devel] ActivityTeam proposal

[Brian Jordan]

Hey,

On Mon, Jan 12, 2009 at 2:26 PM, Wade Brainerd  wrote:
> Hello again,
>
> If you would like to join the ActivityTeam, the Contact page at
> http://sugarlabs.org/go/ActivityTeam/Contacts is available for you to
> add your name.
>
> When adding your name to the list, please take a minute and decide how
> you will contribute to the effort.  Then, go over to the To Do List at
> http://sugarlabs.org/go/ActivityTeam/TODO and put your name down next
> to something using four tildes ().
>
> A lot of tasks are as simple as moving a Git repository or making sure
> activities have up to date tarballs for distribution.  There are also
> bigger tasks like helping to get activities.sugarlabs.org running or
> taking up one of the High Impact tasks from the other thread.
>

(Pardon my inexperience with Gitorious)

To become a contributor to an activity, is the suggested process (1)
make account on Gitorious, (2) email owner of project directly, (3)
wait to be added, (4) commit changes?

What do you think about adding an active ActivityTeam coordinator to
be an admin for each activity project, in case (3) takes a while? Or
is there a global admin role that would allow for something like this?

Over analyzing imaginary bottlenecks,
Brian

> Looking forward to seeing you there!
>
> -Wade
>
> PS - I'm hoping to make it down to XOcamp one evening this week,
> either Tuesday or Wednesday.
>
> On Sat, Jan 10, 2009 at 1:46 PM, Wade Brainerd  wrote:
>> Hi all, hope you are enjoying FUDcon.
>>
>> Given the recent events at OLPC, I'm planning to refocus my activity
>> development efforts on SugarLabs.  I imagine other activity developers
>> are planning to do the same.
>>
>> SugarLabs is off to a great start getting packages into distributions,
>> but I can't help noticing that the activities on the home page are
>> essentially the same were shipped with OLPC build 650 back in 2007.
>>
>> One of the things that drew me to Sugar and OLPC was the promise of
>> high quality, collaborative, constructivist educational software.
>> While the initial activity set was good, it was also clear that there
>> were large holes to be filled.  For a variety reasons, many of those
>> holes remain two years later.
>>
>> And that's why I'm proposing the creation of a SugarLabs ActivityTeam.
>>  The new team will be separate from the DevelopmentTeam, and will have
>> the responsibility of maintaining and extending the suite of
>> activities available for Sugar.
>>
>> We will:
>> 1. Maintain and develop the current suite of Sugar activities.
>> 2. Recruit and mentor activity developers from the community.
>> 3. Collect, document and organize new activity and activity feature
>> ideas from the EducationTeam, deployments and community.
>> 4. Work with the DevelopmentTeam and the InfrastructureTeam to ensure
>> activity developers are well supported.
>> 5. Gather feedback with the DeploymentTeam about how Sugar activities
>> are doing in the field.
>>
>> Until now, activity development has largely been an individual effort.
>>  The purpose of this proposal is to collect the activity development
>> community into an effective team who can tackle the entire ecosystem
>> of Sugar activities together.  One result should be fewer activities
>> "dropping off the radar" into lack of maintenance.
>>
>> Please respond with your feedback about the proposal.  If you like the
>> idea and would like to be part of the ATeam, feel free to indicate
>> that.
>>
>> Best,
>> Wade
>>
> ___
> 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] Activities migration status

[Wade Brainerd]

On Wed, Jan 14, 2009 at 6:05 AM, S Page  wrote:
> I'm not sure what you're doing, but if you want activities...
> When the call went out for activities for 9.1.0 I put all the meta-lists of
> activities in
> 
>
> That links to some interesting queries in
> http://wiki.laptop.org/go/Activity_queries  :
> * 45 pages with a Devel status
> * 116 pages that appear to have an activity bundle
> * 310 pages in Category:Activities in the main namespace.
>
> and I'm sure there are more activities that lack a page on on
> wiki.laptop.org

Thanks, this is a great source of information.

What we are trying to do is track down all the activities that have
been written (or started) and then migrate them to SugarLabs
infrastructure, with permission from their authors.  At the same time
we will encourage their authors to finish them, update them to work
with recent builds, document them, make sure they can be packaged for
non-XO distros, etc.

-Wade

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

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Gary C Martin]

On 14 Jan 2009, at 13:02, Tomeu Vizoso wrote:

> Hi Ben,
>
> can we use this on non-sugar pygtk apps?
>
> For example, could we use it to add collaboration features to
> Labyrinth (a pygtk app that we are reusing as a Sugar activity)? Or
> does it depend on Sugar in any way?

Tomeu, FWIW I've tried multiple times to (politely) make contact with  
the original Labyrinth authors since Dec. Not a peep response from  
anyone, and the google mail list is dead (authorised posters only and  
no one is authorising any one new it seems). Don't hold out hope of  
upstream support – I think there's a lot of code in the core that  
needing changing to improve UI and a lot of code we don't need to  
bundle (custom win NT support!?). I'm guessing upstreaming would work  
much better for a project with a well established code-base, and an  
active maintainer – we seem to have neither.

I'm happy to fork, and make it work its best for us under Sugar, so we  
have a solid activity.

--G

> If the data model supported sharing through telepathy tubes, I think
> that the upstream GNOME developers would be interested in helping us
> maintain this code.
>
> Regards,
>
> Tomeu
>
> On Wed, Jan 14, 2009 at 06:11, Benjamin M. Schwartz
>  wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Groupthink [1] is a development toolkit for collaborative activities.
>> It's designed to hide all the collaboration boilerplate and  
>> algorithms
>> under a clean high-level abstraction, so that Activity developers can
>> spend more time on what they really care about.
>>
>> Groupthink is deeply pre-alpha.  Any application is likely to find a
>> multitude of blocker bugs.  If that is acceptable to you, then by all
>> means start your experiments.  If you are interested, please ask  
>> questions
>> or read the code.
>>
>> As an example of the power of Groupthink, I have created a  
>> collaborative
>> version of Chris Ball's "Words" activity, a multilingual  
>> dictionary.  This
>> required adding the groupthink library into the bundle.  It also  
>> required
>> two patches, attached.  Together, these patches represent a total  
>> of 5
>> lines changed.  The resulting activity has the main input field  
>> shared
>> synchronously across all instances.  This activity will be released,
>> pending further testing.
>>
>> Groupthink: Collab should be easy.
>>
>> - --Ben
>>
>> [1] http://dev.laptop.org/git?p=projects/dobject;a=summary
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v2.0.9 (GNU/Linux)
>>
>> iEYEARECAAYFAkltdAwACgkQUJT6e6HFtqQ80wCfa4f13gAvJQYcdkhdmefBPBuU
>> rYEAoJne2buq5hhC29/4ZFCdVvegBsne
>> =aS94
>> -END PGP SIGNATURE-
>>
>> --- activity.py.orig2009-01-12 22:51:15.0 -0500
>> +++ activity.py 2009-01-12 23:31:59.0 -0500
>> @@ -1,9 +1,11 @@
>> from sugar.activity import activity
>>
>> -class ViewSourceActivity(activity.Activity):
>> +from groupthink.sugar_tools import GroupActivity
>> +
>> +class ViewSourceActivity(GroupActivity):
>>"""Activity subclass which handles the 'view source' key."""
>> -def __init__(self, handle):
>> -super(ViewSourceActivity, self).__init__(handle)
>> +def __init__(self, handle, service_name):
>> +super(ViewSourceActivity, self).__init__(handle,  
>> service_name)
>>self.__source_object_id = None # XXX: persist this across  
>> invocations?
>>self.connect('key-press-event', self._key_press_cb)
>>def _key_press_cb(self, widget, event):
>>
>> --- pippy_app.py.orig   2009-01-13 23:37:25.0 -0500
>> +++ pippy_app.py2009-01-13 00:13:49.0 -0500
>> @@ -28,6 +28,8 @@
>> from sugar.activity.activity import ActivityToolbox, \
>> get_bundle_path, get_bundle_name
>>
>> +import groupthink.gtk_tools
>> +
>> SERVICE = "org.laptop.Words"
>> IFACE = SERVICE
>> PATH = "/org/laptop/Words"
>> @@ -36,7 +38,7 @@
>>"""Words Activity as specified in activity.info"""
>>def __init__(self, handle):
>>"""Set up the Words activity."""
>> -super(WordsActivity, self).__init__(handle)
>> +super(WordsActivity, self).__init__(handle, SERVICE)
>>self._logger = logging.getLogger('words-activity')
>>
>>from sugar.graphics.menuitem import MenuItem
>> @@ -69,7 +71,8 @@
>>label2 = gtk.Label("Translation")
>>
>># Text entry box to enter word to be translated.
>> -self.totranslate = gtk.Entry(max=50)
>> +self.cloud.totranslate =  
>> groupthink.gtk_tools.RecentEntry(max=50)
>> +self.totranslate = self.cloud.totranslate
>>self.totranslate.connect("changed", self.totranslate_cb)
>>self.totranslate.modify_font(pango.FontDescription("Sans 14"))
>>
>>
>> ___
>> 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
> htt

Re: [Sugar-devel] Activities migration status

[Gabriel Eirea]

Wade:

I'm an activity developer with my code at dev.laptop.org. I'm a bit
confused about this migration. Is it necessary to change the location
for some reason? Is dev.laptop.org going to be killed?

I believe the Activity Team is a wonderful idea but would like to have
this point clarified.

Thanks,

Gabriel


2009/1/14 Wade Brainerd :
> On Wed, Jan 14, 2009 at 6:05 AM, S Page  wrote:
>> I'm not sure what you're doing, but if you want activities...
>> When the call went out for activities for 9.1.0 I put all the meta-lists of
>> activities in
>> 
>>
>> That links to some interesting queries in
>> http://wiki.laptop.org/go/Activity_queries  :
>> * 45 pages with a Devel status
>> * 116 pages that appear to have an activity bundle
>> * 310 pages in Category:Activities in the main namespace.
>>
>> and I'm sure there are more activities that lack a page on on
>> wiki.laptop.org
>
> Thanks, this is a great source of information.
>
> What we are trying to do is track down all the activities that have
> been written (or started) and then migrate them to SugarLabs
> infrastructure, with permission from their authors.  At the same time
> we will encourage their authors to finish them, update them to work
> with recent builds, document them, make sure they can be packaged for
> non-XO distros, etc.
>
> -Wade
>
> -Wade
> ___
> Devel mailing list
> de...@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Tomeu Vizoso]

On Wed, Jan 14, 2009 at 18:23, Gary C Martin  wrote:
> On 14 Jan 2009, at 13:02, Tomeu Vizoso wrote:
>
>> Hi Ben,
>>
>> can we use this on non-sugar pygtk apps?
>>
>> For example, could we use it to add collaboration features to
>> Labyrinth (a pygtk app that we are reusing as a Sugar activity)? Or
>> does it depend on Sugar in any way?
>
> Tomeu, FWIW I've tried multiple times to (politely) make contact with the
> original Labyrinth authors since Dec. Not a peep response from anyone, and
> the google mail list is dead (authorised posters only and no one is
> authorising any one new it seems). Don't hold out hope of upstream support –
> I think there's a lot of code in the core that needing changing to improve
> UI and a lot of code we don't need to bundle (custom win NT support!?). I'm
> guessing upstreaming would work much better for a project with a well
> established code-base, and an active maintainer – we seem to have neither.
>
> I'm happy to fork, and make it work its best for us under Sugar, so we have
> a solid activity.

Makes sense. What about keeping the old code or starting anew?

Regards,

Tomeu

> --G
>
>> If the data model supported sharing through telepathy tubes, I think
>> that the upstream GNOME developers would be interested in helping us
>> maintain this code.
>>
>> Regards,
>>
>> Tomeu
>>
>> On Wed, Jan 14, 2009 at 06:11, Benjamin M. Schwartz
>>  wrote:
>>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> Groupthink [1] is a development toolkit for collaborative activities.
>>> It's designed to hide all the collaboration boilerplate and algorithms
>>> under a clean high-level abstraction, so that Activity developers can
>>> spend more time on what they really care about.
>>>
>>> Groupthink is deeply pre-alpha.  Any application is likely to find a
>>> multitude of blocker bugs.  If that is acceptable to you, then by all
>>> means start your experiments.  If you are interested, please ask
>>> questions
>>> or read the code.
>>>
>>> As an example of the power of Groupthink, I have created a collaborative
>>> version of Chris Ball's "Words" activity, a multilingual dictionary.
>>>  This
>>> required adding the groupthink library into the bundle.  It also required
>>> two patches, attached.  Together, these patches represent a total of 5
>>> lines changed.  The resulting activity has the main input field shared
>>> synchronously across all instances.  This activity will be released,
>>> pending further testing.
>>>
>>> Groupthink: Collab should be easy.
>>>
>>> - --Ben
>>>
>>> [1] http://dev.laptop.org/git?p=projects/dobject;a=summary
>>> -BEGIN PGP SIGNATURE-
>>> Version: GnuPG v2.0.9 (GNU/Linux)
>>>
>>> iEYEARECAAYFAkltdAwACgkQUJT6e6HFtqQ80wCfa4f13gAvJQYcdkhdmefBPBuU
>>> rYEAoJne2buq5hhC29/4ZFCdVvegBsne
>>> =aS94
>>> -END PGP SIGNATURE-
>>>
>>> --- activity.py.orig2009-01-12 22:51:15.0 -0500
>>> +++ activity.py 2009-01-12 23:31:59.0 -0500
>>> @@ -1,9 +1,11 @@
>>> from sugar.activity import activity
>>>
>>> -class ViewSourceActivity(activity.Activity):
>>> +from groupthink.sugar_tools import GroupActivity
>>> +
>>> +class ViewSourceActivity(GroupActivity):
>>>   """Activity subclass which handles the 'view source' key."""
>>> -def __init__(self, handle):
>>> -super(ViewSourceActivity, self).__init__(handle)
>>> +def __init__(self, handle, service_name):
>>> +super(ViewSourceActivity, self).__init__(handle, service_name)
>>>   self.__source_object_id = None # XXX: persist this across
>>> invocations?
>>>   self.connect('key-press-event', self._key_press_cb)
>>>   def _key_press_cb(self, widget, event):
>>>
>>> --- pippy_app.py.orig   2009-01-13 23:37:25.0 -0500
>>> +++ pippy_app.py2009-01-13 00:13:49.0 -0500
>>> @@ -28,6 +28,8 @@
>>> from sugar.activity.activity import ActivityToolbox, \
>>>get_bundle_path, get_bundle_name
>>>
>>> +import groupthink.gtk_tools
>>> +
>>> SERVICE = "org.laptop.Words"
>>> IFACE = SERVICE
>>> PATH = "/org/laptop/Words"
>>> @@ -36,7 +38,7 @@
>>>   """Words Activity as specified in activity.info"""
>>>   def __init__(self, handle):
>>>   """Set up the Words activity."""
>>> -super(WordsActivity, self).__init__(handle)
>>> +super(WordsActivity, self).__init__(handle, SERVICE)
>>>   self._logger = logging.getLogger('words-activity')
>>>
>>>   from sugar.graphics.menuitem import MenuItem
>>> @@ -69,7 +71,8 @@
>>>   label2 = gtk.Label("Translation")
>>>
>>>   # Text entry box to enter word to be translated.
>>> -self.totranslate = gtk.Entry(max=50)
>>> +self.cloud.totranslate =
>>> groupthink.gtk_tools.RecentEntry(max=50)
>>> +self.totranslate = self.cloud.totranslate
>>>   self.totranslate.connect("changed", self.totranslate_cb)
>>>   self.totranslate.modify_font(pango.FontDescription("Sans 14"))
>>>
>>>
>>> ___
>>> Sugar-devel mailing list
>>> Su

Re: [Sugar-devel] Activities migration status

[Ed McNierney]

Gabriel -

No, there are no current plans to shut down any services on  
dev.laptop.org.  OLPC has an 8.2.1 release underway and we'll continue  
to maintain those services in the future.

On the other hand, anyone working on Sugar efforts such as Activity  
development should be encouraged to put all those efforts under the  
Sugar Labs roof where they can be more readily available to the entire  
Sugar community (not just the OLPC portion of it).  The last paragraph  
of Wade's message (quoted below) described it very well.

- Ed


On Jan 14, 2009, at 12:33 PM, Gabriel Eirea wrote:

> Wade:
>
> I'm an activity developer with my code at dev.laptop.org. I'm a bit
> confused about this migration. Is it necessary to change the location
> for some reason? Is dev.laptop.org going to be killed?
>
> I believe the Activity Team is a wonderful idea but would like to have
> this point clarified.
>
> Thanks,
>
> Gabriel
>
>
> 2009/1/14 Wade Brainerd :
>> On Wed, Jan 14, 2009 at 6:05 AM, S Page  wrote:
>>> I'm not sure what you're doing, but if you want activities...
>>> When the call went out for activities for 9.1.0 I put all the meta- 
>>> lists of
>>> activities in
>>> >> >
>>>
>>> That links to some interesting queries in
>>> http://wiki.laptop.org/go/Activity_queries  :
>>> * 45 pages with a Devel status
>>> * 116 pages that appear to have an activity bundle
>>> * 310 pages in Category:Activities in the main namespace.
>>>
>>> and I'm sure there are more activities that lack a page on on
>>> wiki.laptop.org
>>
>> Thanks, this is a great source of information.
>>
>> What we are trying to do is track down all the activities that have
>> been written (or started) and then migrate them to SugarLabs
>> infrastructure, with permission from their authors.  At the same time
>> we will encourage their authors to finish them, update them to work
>> with recent builds, document them, make sure they can be packaged for
>> non-XO distros, etc.
>>
>> -Wade
>>
>> -Wade
>> ___
>> Devel mailing list
>> de...@lists.laptop.org
>> http://lists.laptop.org/listinfo/devel
>>
> ___
> Devel mailing list
> de...@lists.laptop.org
> http://lists.laptop.org/listinfo/devel

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

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Gary C Martin]

On 14 Jan 2009, at 17:33, Tomeu Vizoso wrote:

> On Wed, Jan 14, 2009 at 18:23, Gary C Martin   
> wrote:
>> On 14 Jan 2009, at 13:02, Tomeu Vizoso wrote:
>>
>>> Hi Ben,
>>>
>>> can we use this on non-sugar pygtk apps?
>>>
>>> For example, could we use it to add collaboration features to
>>> Labyrinth (a pygtk app that we are reusing as a Sugar activity)? Or
>>> does it depend on Sugar in any way?
>>
>> Tomeu, FWIW I've tried multiple times to (politely) make contact  
>> with the
>> original Labyrinth authors since Dec. Not a peep response from  
>> anyone, and
>> the google mail list is dead (authorised posters only and no one is
>> authorising any one new it seems). Don't hold out hope of upstream  
>> support –
>> I think there's a lot of code in the core that needing changing to  
>> improve
>> UI and a lot of code we don't need to bundle (custom win NT  
>> support!?). I'm
>> guessing upstreaming would work much better for a project with a well
>> established code-base, and an active maintainer – we seem to have  
>> neither.
>>
>> I'm happy to fork, and make it work its best for us under Sugar, so  
>> we have
>> a solid activity.
>
> Makes sense. What about keeping the old code or starting anew?

For me, it'll be quicker to work with what's there already, trim it  
down to what we need, and tune it for Sugar (and specifically XO) use.  
Is there some FOSS political/religious baggage about forking like this  
that I've just trodden in? Or were you just hoping to engage upstream  
to do some of the work for Sugar support ;-)

--G

> Regards,
>
> Tomeu
>
>> --G
>>
>>> If the data model supported sharing through telepathy tubes, I think
>>> that the upstream GNOME developers would be interested in helping us
>>> maintain this code.
>>>
>>> Regards,
>>>
>>> Tomeu
>>>
>>> On Wed, Jan 14, 2009 at 06:11, Benjamin M. Schwartz
>>>  wrote:

 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1

 Groupthink [1] is a development toolkit for collaborative  
 activities.
 It's designed to hide all the collaboration boilerplate and  
 algorithms
 under a clean high-level abstraction, so that Activity developers  
 can
 spend more time on what they really care about.

 Groupthink is deeply pre-alpha.  Any application is likely to  
 find a
 multitude of blocker bugs.  If that is acceptable to you, then by  
 all
 means start your experiments.  If you are interested, please ask
 questions
 or read the code.

 As an example of the power of Groupthink, I have created a  
 collaborative
 version of Chris Ball's "Words" activity, a multilingual  
 dictionary.
 This
 required adding the groupthink library into the bundle.  It also  
 required
 two patches, attached.  Together, these patches represent a total  
 of 5
 lines changed.  The resulting activity has the main input field  
 shared
 synchronously across all instances.  This activity will be  
 released,
 pending further testing.

 Groupthink: Collab should be easy.

 - --Ben

 [1] http://dev.laptop.org/git?p=projects/dobject;a=summary
 -BEGIN PGP SIGNATURE-
 Version: GnuPG v2.0.9 (GNU/Linux)

 iEYEARECAAYFAkltdAwACgkQUJT6e6HFtqQ80wCfa4f13gAvJQYcdkhdmefBPBuU
 rYEAoJne2buq5hhC29/4ZFCdVvegBsne
 =aS94
 -END PGP SIGNATURE-

 --- activity.py.orig2009-01-12 22:51:15.0 -0500
 +++ activity.py 2009-01-12 23:31:59.0 -0500
 @@ -1,9 +1,11 @@
 from sugar.activity import activity

 -class ViewSourceActivity(activity.Activity):
 +from groupthink.sugar_tools import GroupActivity
 +
 +class ViewSourceActivity(GroupActivity):
  """Activity subclass which handles the 'view source' key."""
 -def __init__(self, handle):
 -super(ViewSourceActivity, self).__init__(handle)
 +def __init__(self, handle, service_name):
 +super(ViewSourceActivity, self).__init__(handle,  
 service_name)
  self.__source_object_id = None # XXX: persist this across
 invocations?
  self.connect('key-press-event', self._key_press_cb)
  def _key_press_cb(self, widget, event):

 --- pippy_app.py.orig   2009-01-13 23:37:25.0 -0500
 +++ pippy_app.py2009-01-13 00:13:49.0 -0500
 @@ -28,6 +28,8 @@
 from sugar.activity.activity import ActivityToolbox, \
   get_bundle_path, get_bundle_name

 +import groupthink.gtk_tools
 +
 SERVICE = "org.laptop.Words"
 IFACE = SERVICE
 PATH = "/org/laptop/Words"
 @@ -36,7 +38,7 @@
  """Words Activity as specified in activity.info"""
  def __init__(self, handle):
  """Set up the Words activity."""
 -super(WordsActivity, self).__init__(handle)
 +super(WordsActivity, self).__init__(handle, SERVICE)
  self._logger = logging.getLogger('words-activ

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Tomeu Vizoso]

On Wed, Jan 14, 2009 at 18:54, Gary C Martin  wrote:
> On 14 Jan 2009, at 17:33, Tomeu Vizoso wrote:
>
>> On Wed, Jan 14, 2009 at 18:23, Gary C Martin  wrote:
>>>
>>> On 14 Jan 2009, at 13:02, Tomeu Vizoso wrote:
>>>
 Hi Ben,

 can we use this on non-sugar pygtk apps?

 For example, could we use it to add collaboration features to
 Labyrinth (a pygtk app that we are reusing as a Sugar activity)? Or
 does it depend on Sugar in any way?
>>>
>>> Tomeu, FWIW I've tried multiple times to (politely) make contact with the
>>> original Labyrinth authors since Dec. Not a peep response from anyone,
>>> and
>>> the google mail list is dead (authorised posters only and no one is
>>> authorising any one new it seems). Don't hold out hope of upstream
>>> support –
>>> I think there's a lot of code in the core that needing changing to
>>> improve
>>> UI and a lot of code we don't need to bundle (custom win NT support!?).
>>> I'm
>>> guessing upstreaming would work much better for a project with a well
>>> established code-base, and an active maintainer – we seem to have
>>> neither.
>>>
>>> I'm happy to fork, and make it work its best for us under Sugar, so we
>>> have
>>> a solid activity.
>>
>> Makes sense. What about keeping the old code or starting anew?
>
> For me, it'll be quicker to work with what's there already, trim it down to
> what we need, and tune it for Sugar (and specifically XO) use. Is there some
> FOSS political/religious baggage about forking like this that I've just
> trodden in? Or were you just hoping to engage upstream to do some of the
> work for Sugar support ;-)

The latter ;)

Tomeu

>
>> Regards,
>>
>> Tomeu
>>
>>> --G
>>>
 If the data model supported sharing through telepathy tubes, I think
 that the upstream GNOME developers would be interested in helping us
 maintain this code.

 Regards,

 Tomeu

 On Wed, Jan 14, 2009 at 06:11, Benjamin M. Schwartz
  wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Groupthink [1] is a development toolkit for collaborative activities.
> It's designed to hide all the collaboration boilerplate and algorithms
> under a clean high-level abstraction, so that Activity developers can
> spend more time on what they really care about.
>
> Groupthink is deeply pre-alpha.  Any application is likely to find a
> multitude of blocker bugs.  If that is acceptable to you, then by all
> means start your experiments.  If you are interested, please ask
> questions
> or read the code.
>
> As an example of the power of Groupthink, I have created a
> collaborative
> version of Chris Ball's "Words" activity, a multilingual dictionary.
> This
> required adding the groupthink library into the bundle.  It also
> required
> two patches, attached.  Together, these patches represent a total of 5
> lines changed.  The resulting activity has the main input field shared
> synchronously across all instances.  This activity will be released,
> pending further testing.
>
> Groupthink: Collab should be easy.
>
> - --Ben
>
> [1] http://dev.laptop.org/git?p=projects/dobject;a=summary
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.9 (GNU/Linux)
>
> iEYEARECAAYFAkltdAwACgkQUJT6e6HFtqQ80wCfa4f13gAvJQYcdkhdmefBPBuU
> rYEAoJne2buq5hhC29/4ZFCdVvegBsne
> =aS94
> -END PGP SIGNATURE-
>
> --- activity.py.orig2009-01-12 22:51:15.0 -0500
> +++ activity.py 2009-01-12 23:31:59.0 -0500
> @@ -1,9 +1,11 @@
> from sugar.activity import activity
>
> -class ViewSourceActivity(activity.Activity):
> +from groupthink.sugar_tools import GroupActivity
> +
> +class ViewSourceActivity(GroupActivity):
>  """Activity subclass which handles the 'view source' key."""
> -def __init__(self, handle):
> -super(ViewSourceActivity, self).__init__(handle)
> +def __init__(self, handle, service_name):
> +super(ViewSourceActivity, self).__init__(handle, service_name)
> self.__source_object_id = None # XXX: persist this across
> invocations?
> self.connect('key-press-event', self._key_press_cb)
>  def _key_press_cb(self, widget, event):
>
> --- pippy_app.py.orig   2009-01-13 23:37:25.0 -0500
> +++ pippy_app.py2009-01-13 00:13:49.0 -0500
> @@ -28,6 +28,8 @@
> from sugar.activity.activity import ActivityToolbox, \
>  get_bundle_path, get_bundle_name
>
> +import groupthink.gtk_tools
> +
> SERVICE = "org.laptop.Words"
> IFACE = SERVICE
> PATH = "/org/laptop/Words"
> @@ -36,7 +38,7 @@
>  """Words Activity as specified in activity.info"""
>  def __init__(self, handle):
> """Set up the Words activity."""
> -super(WordsActivity, self).__init__(handle)
> +supe

Re: [Sugar-devel] p2p stream tubes

[Morgan Collett]

On Wed, Jan 7, 2009 at 12:57, Guillaume Desmottes  wrote:
> Hi guys,
>
> I released telepathy-gabble 0.7.18 yesterday which implements a
> long-awaited feature: peer to peer connections in stream tubes!
>
> Basically this means that stream tubes will use a TCP connection (using
> SOCKS 5) to transfer their data instead of sending them through the
> server with IBB (base64 encoding). If the socks5 connection can't be
> established (because peers are on different NAT's for example) then
> Gabble will fallback to IBB.
> This should drastically improve stream tube performances and reduce
> server's band-with consumption.
>
> As all of this is pure Telepathy implementation details, activities
> using stream tubes (as Read) doesn't have to change a single line of
> their code to benefit of this improvement! Clients just have to upgrade
> their Gabble.
>
> Of course, there are probably bugs in the current implementation so it
> would be good if Sugar users could start to test it ASAP.
> We should observe the following results in these scenario:
>
> - old Gabble <-> new Gabble: continue to use IBB as before.
> - new Gabble <-> new Gabble on the same network: use sock5 connections
> (the transfer of the shared document in Read should be really faster)
> - new Gabble <-> new Gabble on different networks: try to use sock5 and
> the fallback to IBB.
>
> This is the first step in our "improve tubes connectivity" plan and lead
> the way to new improvements as using a socks5 relay to transfer data if
> direct connection is impossible. The ultimate goal is to use jingle to
> benefit real NAT penetration (as in audio/video calls).
>
> Please feel free to test this new version and report any problem you
> could have.
>
>
> Regards,
>
>
>G.
>
> [1]
> http://lists.freedesktop.org/archives/telepathy/2009-January/002734.html

I want to add it to jhbuild, but on intrepid I get "Requested
'dbus-glib-1 >= 0.78' but version of dbus-glib is 0.76".

Are we going to need to put a newer libdbus-glib-1 into jhbuild?

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

Re: [Sugar-devel] p2p stream tubes

[Guillaume Desmottes]

Le mercredi 14 janvier 2009 à 20:20 +0200, Morgan Collett a écrit :
> I want to add it to jhbuild, but on intrepid I get "Requested
> 'dbus-glib-1 >= 0.78' but version of dbus-glib is 0.76".
> 
> Are we going to need to put a newer libdbus-glib-1 into jhbuild?

Probably, recent Gabble needs this new version.


G.



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

Re: [Sugar-devel] p2p stream tubes

[Benjamin M. Schwartz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Guillaume Desmottes wrote:
> I released telepathy-gabble 0.7.18 yesterday which implements a
> long-awaited feature: peer to peer connections in stream tubes!

That's fantastic!

...

But of course we are never satisfied, so I must ask: how soon do you think
Gabble will implement the new File Transfer spec?

- --Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkluOSkACgkQUJT6e6HFtqQwHACeOFoDv2KKT+fFPzVq9liUjrWc
5cIAmQE1tJny0E2ye58+RA05d5X0lxyx
=86pk
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

[Sugar-devel] jhbuild obsoleted itself:)

[David Farning]

I have just gone through the wiki and deleted the
developmentteam/jhbuild/* pages:)

These pages were created in around June of 2008 when jhbuild was the
only method for running Sugar on non-XO platforms.  Now that we have
packages for several distributions and will be using the distributions
as our primary means of delivery, it makes sense to reduce the
emphasis of jhbuild as a method for delivering Sugar to end-users.

Don't worry, developmentteam/jhbuild is alive and well for 'developer' use.

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

Re: [Sugar-devel] XOCamp 2: Day 3 update

[Samuel Klein]

Hello,

We are currently talking about a string of technical topics : l10n,
journal, performance/memory, power, and jffs/ubi --- through the end
of the day.

After this there will be a brief talk about digitizing and creating
books from ed cherlin at 5.  The post below has the latest information
for joining in.

SJ

On Tue, Jan 13, 2009 at 11:31 AM, Samuel Klein  wrote:
> We've made a few schedule changes today, with talks about
> customization, signing, and activation moved to later in the
> afternoon, and a longer session on the school server through the
> morning.
>
> http://blog.laptop.org/2009/01/12/xo-camp-on-tv/
>
> Feel free to leave comments, questions and ideas on the schedule's
> talkpage if you can't join in person.
>
> SJ
>
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] jhbuild obsoleted itself:)

[Luke Faraone]

On Wed, Jan 14, 2009 at 4:15 PM, David Farning wrote:

> I have just gone through the wiki and deleted the
> developmentteam/jhbuild/* pages:)
>
> These pages were created in around June of 2008 when jhbuild was the
> only method for running Sugar on non-XO platforms.  Now that we have
> packages for several distributions and will be using the distributions
> as our primary means of delivery, it makes sense to reduce the
> emphasis of jhbuild as a method for delivering Sugar to end-users.
>
> Don't worry, developmentteam/jhbuild is alive and well for 'developer' use.


David,

I don't see the justification in deleting these pages, they are still very
useful for developers who need to get up and running.

Those pages contained information about dependancies, etc that are different
for each platform.

Even if they were of questionable current usefulness, I'd rather keep things
around and simply put a "deprecated" header over them, so that people who
want the information can still see it. Deleting the content makes them
invisible to all but administrators, which is, imho, a bad idea.

I'm not going to revert your changes, but I disagree that these pages were
not useful. They are in the same category as redirects like
http://sugarlabs.org/wiki/index.php?title=Sugar_Labs/Meetings&action=edit&redlink=1,
http://sugarlabs.org/wiki/index.php?title=OLE_Presentation&action=edit&redlink=1,
http://sugarlabs.org/wiki/index.php?title=Presentations&action=edit&redlink=1,
and http://sugarlabs.org/go/IRC.


-- 
Luke Faraone
http://luke.faraone.cc
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] jhbuild obsoleted itself:)

[Marco Pesenti Gritti]

On Wed, Jan 14, 2009 at 4:49 PM, Luke Faraone  wrote:
> David,
>
> I don't see the justification in deleting these pages, they are still very
> useful for developers who need to get up and running.
>
> Those pages contained information about dependancies, etc that are different
> for each platform.

Personally I think those are just adding confusion. We should have
automatic checks in jhbuild for all the distro we care about. Trying
support the rest is a lost battle, because instructions will always be
out of sync.

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

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Sebastian Silva]

I love the API, great contribution Ben!

I also love the name, Groupthink, from WikiPedia:
"Groupthink is a type of thought exhibited by group members who try to
minimize conflict and reach consensus without critically testing,
analyzing, and evaluating ideas. Individual creativity, uniqueness,
and independent thinking are lost in the pursuit of group
cohesiveness, as are the advantages of reasonable balance in choice
and thought that might normally be obtained by making decisions as a
group.[1] During groupthink, members of the group avoid promoting
viewpoints outside the comfort zone of consensus thinking. A variety
of motives for this may exist such as a desire to avoid being seen as
foolish, or a desire to avoid embarrassing or angering other members
of the group. Groupthink may cause groups to make hasty, irrational
decisions, where individual doubts are set aside, for fear of
upsetting the groups balance. The term is frequently used
pejoratively, with hindsight."

*Grin*

Sebastian

2009/1/14 Benjamin M. Schwartz :
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Groupthink [1] is a development toolkit for collaborative activities.
> It's designed to hide all the collaboration boilerplate and algorithms
> under a clean high-level abstraction, so that Activity developers can
> spend more time on what they really care about.
>
> Groupthink is deeply pre-alpha.  Any application is likely to find a
> multitude of blocker bugs.  If that is acceptable to you, then by all
> means start your experiments.  If you are interested, please ask questions
> or read the code.
>
> As an example of the power of Groupthink, I have created a collaborative
> version of Chris Ball's "Words" activity, a multilingual dictionary.  This
> required adding the groupthink library into the bundle.  It also required
> two patches, attached.  Together, these patches represent a total of 5
> lines changed.  The resulting activity has the main input field shared
> synchronously across all instances.  This activity will be released,
> pending further testing.
>
> Groupthink: Collab should be easy.
>
> - --Ben
>
> [1] http://dev.laptop.org/git?p=projects/dobject;a=summary
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.9 (GNU/Linux)
>
> iEYEARECAAYFAkltdAwACgkQUJT6e6HFtqQ80wCfa4f13gAvJQYcdkhdmefBPBuU
> rYEAoJne2buq5hhC29/4ZFCdVvegBsne
> =aS94
> -END PGP SIGNATURE-
>
> --- activity.py.orig2009-01-12 22:51:15.0 -0500
> +++ activity.py 2009-01-12 23:31:59.0 -0500
> @@ -1,9 +1,11 @@
>  from sugar.activity import activity
>
> -class ViewSourceActivity(activity.Activity):
> +from groupthink.sugar_tools import GroupActivity
> +
> +class ViewSourceActivity(GroupActivity):
> """Activity subclass which handles the 'view source' key."""
> -def __init__(self, handle):
> -super(ViewSourceActivity, self).__init__(handle)
> +def __init__(self, handle, service_name):
> +super(ViewSourceActivity, self).__init__(handle, service_name)
> self.__source_object_id = None # XXX: persist this across invocations?
> self.connect('key-press-event', self._key_press_cb)
> def _key_press_cb(self, widget, event):
>
> --- pippy_app.py.orig   2009-01-13 23:37:25.0 -0500
> +++ pippy_app.py2009-01-13 00:13:49.0 -0500
> @@ -28,6 +28,8 @@
>  from sugar.activity.activity import ActivityToolbox, \
>  get_bundle_path, get_bundle_name
>
> +import groupthink.gtk_tools
> +
>  SERVICE = "org.laptop.Words"
>  IFACE = SERVICE
>  PATH = "/org/laptop/Words"
> @@ -36,7 +38,7 @@
> """Words Activity as specified in activity.info"""
> def __init__(self, handle):
> """Set up the Words activity."""
> -super(WordsActivity, self).__init__(handle)
> +super(WordsActivity, self).__init__(handle, SERVICE)
> self._logger = logging.getLogger('words-activity')
>
> from sugar.graphics.menuitem import MenuItem
> @@ -69,7 +71,8 @@
> label2 = gtk.Label("Translation")
>
> # Text entry box to enter word to be translated.
> -self.totranslate = gtk.Entry(max=50)
> +self.cloud.totranslate = groupthink.gtk_tools.RecentEntry(max=50)
> +self.totranslate = self.cloud.totranslate
> self.totranslate.connect("changed", self.totranslate_cb)
> self.totranslate.modify_font(pango.FontDescription("Sans 14"))
>
>
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
>
>



-- 
Sebastian Silva
Laboratorios FuenteLibre
http://blog.sebastiansilva.com/
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Martin Dengler]

On Wed, Jan 14, 2009 at 08:37:08PM -0300, Sebastian Silva wrote:
> I also love the name, Groupthink [...] *Grin*

I love the irony of loving the ironic use of the pejorative name for
an API that helps people exchange (by implication) different ideas.
This kind of recursive irony (irony loop) is hilarious...

> Sebastian

Martin


pgpS3UDAYxFOu.pgp
Description: PGP signature
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Martin Edmund Sevior]

Hi David,
 How do you solve "internet lag". 

User A puts a character "A" in position 10, then before user B see sees this 
(because of the finite propagation time), he puts character "B" in position 10?

Who wins? You just have to make sure the the document remains the same for both 
users.

Cheers!

Martin


 
-Original Message-
From: sugar-devel-boun...@lists.sugarlabs.org on behalf of David Van Assche
Sent: Wed 1/14/2009 11:42 PM
To: Chris Ball
Cc: b...@alum.mit.edu; Sugar Devel
Subject: Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha
 
This sounds like a great foundation for a sugar framework... something
that not only coders can get a feel for...

kind Regards,
David Van Assche

On Wed, Jan 14, 2009 at 6:33 AM, Chris Ball  wrote:
> Hi Ben,
>
>   > Groupthink: Collab should be easy.
>
> (from the patch):
> -self.totranslate = gtk.Entry(max=50)
> +self.cloud.totranslate = groupthink.gtk_tools.RecentEntry(max=50)
>
> .. wow, that *is* easy.  And it's synchronous, so the text box is
> updated with each character press.  You could also use this technique
> for Pippy's source code textbox, which would immediately turn it into a
> collaborative editor.  (I don't care about collisions very much as long
> as everyone gets the same state; they can be resolved socially.)
>
> Now that we're excited, maybe you should let on what the blocker bugs
> are.  :-)
>
> Could we sign you up for a quick XOCamp demo/talk?
>
> Thanks!
>
> - Chris.
> --
> Chris Ball   
> ___
> 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] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Caroline Meeks]

On Wed, Jan 14, 2009 at 6:59 PM, Martin Dengler wrote:

> On Wed, Jan 14, 2009 at 08:37:08PM -0300, Sebastian Silva wrote:
> > I also love the name, Groupthink [...] *Grin*
>
> I love the irony of loving the ironic use of the pejorative name for
> an API that helps people exchange (by implication) different ideas.
> This kind of recursive irony (irony loop) is hilarious...
>

+1

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


-- 
Caroline Meeks
Solution Grove
carol...@solutiongrove.com

617-500-3488 - Office
505-213-3268 - Fax
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] Sugarlabs and GSOC

[Leslie Hawthorn]

Hi Jameson,

Pleasure to virtually meet you.

And hello again to the fabulous Mel Chua. :)

On Fri, Jan 9, 2009 at 9:19 AM, Jameson Quinn wrote:

> Last year, OLPC handled the sugar educational environment in GSOC. This
> year, that responsibility could be split. Sugarlabs, a more traditional
> open-source government org, handles Sugar; and OLPC only in one platform
> version of that, for Fedora on the XO. It is not clear to me what, if any,
> interest in GSOC OLPC will have (they are undergoing some serious
> belt-tightening right now, so it's not the best time to ask). Some of last
> years' OLPC mentors for GSOC are now associated with Sugarlabs instead.
>
> LH, I've been delegated to ask you what implications that has for what
> range of numbers of slots Sugarlabs might reasonably expect. It is
> emphatically not our intention to take any slots from OLPC which OLPC can
> legitimately use, but it is our impression that OLPC might have a lower
> number of interesting applicants this year due to the much-smaller code base
> that is still strictly "theirs". There are rumors that GSOC puts "new"
> organizations at the end of the line for slots, and we hope that some of
> OLPC's track record might rub off on us. In fact, we dare hope that, as a
> less heierarchical organization than OLPC, we may actually do a better job
> than they did with open source community tasks like GSOC.
>

This question is a bit premature, but enthusiasm is always appreciated.

Assuming you are accepted as a mentoring organization, your number of
student slots would be based on overall popularity as with all other
organizations. There's full documentation available here that may be helpful
to you:

http://groups.google.com/group/google-summer-of-code-announce/web/notes-on-student-allocations

I look forward to reviewing your organization application.

Cheers,
LH


-- 
Leslie Hawthorn
Program Manager - Open Source
Google Inc.

http://code.google.com/opensource/

I blog here:

http://google-opensource.blogspot.com - http://www.hawthornlandings.org
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Bryan Berry]

I love any name that somehow reference directly or indirectly George
Orwell's Classic 1984. I dont' know if 1984 ever used the term
groupthink but it certainly coined the wonderful term "doublethink" :)
On Wed, 2009-01-14 at 19:26 -0500, Caroline Meeks wrote:
> 
> 
> On Wed, Jan 14, 2009 at 6:59 PM, Martin Dengler
>  wrote:
> On Wed, Jan 14, 2009 at 08:37:08PM -0300, Sebastian Silva
> wrote:
> > I also love the name, Groupthink [...] *Grin*
> 
> I love the irony of loving the ironic use of the pejorative
> name for
> an API that helps people exchange (by implication) different
> ideas.
> This kind of recursive irony (irony loop) is hilarious...
> 
> +1 
> 
> 
> > Sebastian
> 
> Martin
> 
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
> 
> 
> 
> 
> -- 
> Caroline Meeks
> Solution Grove
> carol...@solutiongrove.com
> 
> 617-500-3488 - Office
> 505-213-3268 - Fax
> ___
> Sugar-devel mailing list
> Sugar-devel@lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/sugar-devel
-- 
Bryan W. Berry
Technology Director
OLE Nepal, http://www.olenepal.org

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

Re: [Sugar-devel] [ANNOUNCE] Groupthink 0.1 pre-alpha

[Benjamin M. Schwartz]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Martin Edmund Sevior wrote:
>  How do you solve "internet lag".
>
> User A puts a character "A" in position 10, then before user B see sees
this (because of the finite propagation time), he puts character "B" in
position 10?
>
> Who wins? You just have to make sure the the document remains the same
for both users.

This is, indeed, the central problem.  For the moment, the answer is:
Groupthink does not support full documents, only short snippets of text.
I have prototyped a data structure that I believe can coherently resolve
these sorts of edit conflicts in long documents without any negotiation,
but it remains to be seen if the design will work.

In general, Groupthink's approach (described at length in docstrings in
the code) is to write each data structure in such a way that any two users
who have observed the same set of messages will arrive at the same state,
regardless of the order in which those messages are received.  The hard
part is figuring out how to do this for each kind of data structure.
However, once it is working, the code can be reused for many purposes
without needing to understand how it works.

- --Ben
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkluuskACgkQUJT6e6HFtqQb2QCfXnSJHwZpn6Q/OsDSs8nJEb3x
vWIAoIJYuSuEp8EFOeKynHDLctW2S5iq
=Po5R
-END PGP SIGNATURE-
___
Sugar-devel mailing list
Sugar-devel@lists.sugarlabs.org
http://lists.sugarlabs.org/listinfo/sugar-devel