Re: [Sugar-devel] Pippy not ready for Sucrose

2009-02-23 Thread Simon Schampijer
Brian Jordan wrote: On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer si...@schampijer.de wrote: Simon Schampijer wrote: Hi, the Sucrose package of Pippy is version 25 - when I last released it back in August. Since then there has been some development going into Pippy (now version 30)

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-02-23 Thread Brian Jordan
Hi Simon, Yup, I will have it completed this week. Apologies for my recent absence, and thanks for the reminder: -- Forwarded message -- From: Brian Jordan bcjor...@gmail.com Date: Mon, Feb 23, 2009 at 3:10 PM Subject: Re: Migrating activities from OLPC to SL To: David Farning

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-27 Thread Simon Schampijer
Brian Jordan wrote: On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer si...@schampijer.de wrote: Simon Schampijer wrote: Hi, the Sucrose package of Pippy is version 25 - when I last released it back in August. Since then there has been some development going into Pippy (now version 30)

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-26 Thread Brian Jordan
On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer si...@schampijer.de wrote: Simon Schampijer wrote: Hi, the Sucrose package of Pippy is version 25 - when I last released it back in August. Since then there has been some development going into Pippy (now version 30)

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-26 Thread Wade Brainerd
Awesome, thank you Brian for stepping up! Is something additional required in order to make sure the activity runs properly in SoaS or jhbuild? -Wade On Mon, Jan 26, 2009 at 2:14 PM, Brian Jordan br...@laptop.org wrote: On Fri, Jan 23, 2009 at 2:21 PM, Simon Schampijer si...@schampijer.de

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-23 Thread Wade Brainerd
I don't have anyone in mind immediately who is not reading this list,. If anyone is willing to step up to maintain Pippy with the Sucrose release schedule please contact me or reply to this emaiml. So far, the ActivityTeam has a few members but we are not really organized as yet, and time

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 20, 2009 at 12:27:08PM +0100, Simon Schampijer wrote: the Sucrose package of Pippy is version 25 - when I last released it back in August. Since then there has been some development going into Pippy (now version 30)

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Nirav Patel
PyBox2D is included locally in the activity, just as it is in Physics, x2o, Bridge, and other Activities that use physics. Though, that is ~2.5mB of duplicated libraries for each. Nirav On 1/20/09, Jonas Smedegaard d...@jones.dk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue,

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 20, 2009 at 01:10:11PM -0500, Nirav Patel wrote: PyBox2D is included locally in the activity, just as it is in Physics, x2o, Bridge, and other Activities that use physics. Though, that is ~2.5mB of duplicated libraries for each.

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Luke Faraone
On Tue, Jan 20, 2009 at 2:03 PM, Jonas Smedegaard d...@jones.dk wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 20, 2009 at 01:10:11PM -0500, Nirav Patel wrote: PyBox2D is included locally in the activity, just as it is in Physics, x2o, Bridge, and other Activities that use

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Nirav Patel
I prefer to look at it pragmatically. Until there is some kind of dependency handling for .xo packages, this is the difference between a child at an existing deployment being able to browse to the wiki, download an activity, and use it, or not being able to. Nirav On Tue, Jan 20, 2009 at 2:03

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Luke Faraone
On Tue, Jan 20, 2009 at 5:21 PM, Nirav Patel o...@spongezone.net wrote: I prefer to look at it pragmatically. Until there is some kind of dependency handling for .xo packages, this is the difference between a child at an existing deployment being able to browse to the wiki, download an

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Wade Brainerd
It's important to separate the pragmatism from the license concern. I fully support the pragmatism of shipping libraries with activities as a temporary solution, if that's what is needed to make the activity work. If the license *requires* us to include the source code to the compiled module (is

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Chris Ball
Hi, I prefer to look at it pragmatically. Until there is some kind of dependency handling for .xo packages, this is the difference between a child at an existing deployment being able to browse to the wiki, download an activity, and use it, or not being able to. It's also the

Re: [Sugar-devel] Pippy not ready for Sucrose

2009-01-20 Thread Jonas Smedegaard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 20, 2009 at 06:24:48PM -0500, Chris Ball wrote: Hi, I prefer to look at it pragmatically. Until there is some kind of dependency handling for .xo packages, this is the difference between a child at an existing deployment