headers
Bruno Coudoin | 1 Jul 13:59
Picon
Favicon
Gravatar

GComprisXO progress


GCompriXO is a development branch of GCompris which focuses on Sugar
integration. Once complete, it will be the base of all future
development in GCompris.

Currently, there as been two major changes in GCompris related to the
XO:
- we removed libsdl_mixer as our audio backend and replaced it by
  gstreamer (already in gcompris trunk).
- Screen size Independence. We rely on the scaling feature of the gnome
  canvas to size our window to the user screen. We no more use xvidmode.
  There is a drawback in term of quality, moving to svg should help but
  currently the gnome canvas and our code does not use the svg native
  scaling feature.
- changed the way we organize activities in our code. Now each activity
  has its own directory. This makes it easy to package independent
  activity instead of having a big GCompris that contains all of them.

To test it:
svn co svn+ssh://bcoudoin <at> svn.gnome.org/svn/gcompris/branches/gcomprixo
gcomprixo
cd gcomprixo
sh autogen.sh --disable-sqlite && make

To test one acytivity:
cd src/fifteen-activity/
./runit.sh

To create an independant 'bundle' (not at the sugar standard yet)
tar -cvhzf wordprocessor-activity.tgz wordprocessor-activity/
(Continue reading)

Permalink | Reply | 28 comments |
headers
Bruno Coudoin | 1 Jul 14:49
Picon
Favicon
Gravatar

Re: GComprisXO progress

Le dimanche 01 juillet 2007 à 13:59 +0200, Bruno Coudoin a écrit :

> To test it:
> svn co svn
> +ssh://bcoudoin <at> svn.gnome.org/svn/gcompris/branches/gcomprixo

Sorry, you must use the anonymous access instead:
svn co http://svn.gnome.org/svn/gcompris/branches/gcomprixo

> gcomprixo
> cd gcomprixo
> sh autogen.sh --disable-sqlite && make

This doesn't change.

--

-- 
Bruno Coudoin
http://gcompris.net Free educational software for kids
http://toulibre.org Logiciel Libre à Toulouse
Permalink | Reply | 0 comments |
headers
Marco Pesenti Gritti | 1 Jul 21:05
Picon
Favicon

Re: GComprisXO progress

Bruno Coudoin wrote:
> GCompriXO is a development branch of GCompris which focuses on Sugar
> integration. Once complete, it will be the base of all future
> development in GCompris.
>   

Yay! Awesome to see progress on this.

> The most important for sugar:
> - sugarize gcompris binary. On this one, I need help. I have seen that 
>   we need to have dbus support. I could not find documentation on that
>   point, can someone point me on the right direction.
>   

Can you please explain what's exactly the role of the binary? Is each 
activity runned from the binary? What does it provide?

Thanks,
Marco
Permalink | Reply | 20 comments |
headers
Bruno Coudoin | 1 Jul 22:41
Picon
Favicon
Gravatar

Re: GComprisXO progress

Le dimanche 01 juillet 2007 à 21:05 +0200, Marco Pesenti Gritti a
écrit :
> Can you please explain what's exactly the role of the binary? Is each 
> activity runned from the binary? What does it provide?

GCompris can be seen as a game engine, we call it the core, and each
activity rely on it to play. In our case, the gcompris binary contains
the game engine and within each activity directory you can find either a
bunch of C or python files for the activity code.

For python activity, it would make sense to have a GCompris core in
python but for now we don't have it.

--

-- 
Bruno Coudoin
http://gcompris.net Free educational software for kids
http://toulibre.org Logiciel Libre à Toulouse
Permalink | Reply | 18 comments |
headers
Michael Rueger | 2 Jul 13:52

Re: OLPC software: our first release and beyond.

Walter Bender wrote:

> It is important now to set expectations for the software that ships on
> the XOs in September. The tremendous amount of work to date does not
> change the fact that our first-release software is very much a work in
> progress. The software at ship time will not have all the richness of
> the Mesh view as described in our User Interface Guide, but we are on
> track to have an extensible framework in place. The Journal, another
> important component of Sugar, recently appeared in our builds and
> currently offers bare-bones functionality; however, the first
> iteration of the data store is near completion and includes support
> for removable media and network file systems. The Journal is on track
> to include more features, such as a rich system to tag, search, and
> sort in the coming months, and an API for developers. The ability to
> open files, read, write, etc., are being transitioned to mediation by
> both the Journal and, at a lower level, Bitfrost, our security system.
> These transitions will be completed before we ship.

How long a time frame is planned to give application developers time to 
port/adjust/extend their applications to work with the APIs, security 
system etc?

Is there time allocated for regression testing?

We (the Squeakers) already have a hard time keeping up with changing 
APIs, launch sequences etc. And to make life even more interesting 
things like the need to extract the DBus Activity Protocol from the 
source code.

Is there a plan for central/country specific server locations where
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marco Pesenti Gritti | 2 Jul 16:41
Picon
Favicon

Re: GComprisXO progress

Bruno Coudoin wrote:
> Le dimanche 01 juillet 2007 à 21:05 +0200, Marco Pesenti Gritti a
> écrit :
>   
>> Can you please explain what's exactly the role of the binary? Is each 
>> activity runned from the binary? What does it provide?
>>     
>
> GCompris can be seen as a game engine, we call it the core, and each
> activity rely on it to play. In our case, the gcompris binary contains
> the game engine and within each activity directory you can find either a
> bunch of C or python files for the activity code.
>
> For python activity, it would make sense to have a GCompris core in
> python but for now we don't have it.
>   

I'd suggest to have a look at sugar-native-factory.c in sugar git. You 
can either add something like that to the binary or use it as is to 
launch the binary.

Marco
Permalink | Reply | 16 comments |
headers
Bert Freudenberg | 2 Jul 17:05
Picon
Gravatar

Re: GComprisXO progress


On Jul 2, 2007, at 16:41 , Marco Pesenti Gritti wrote:

> Bruno Coudoin wrote:
>> Le dimanche 01 juillet 2007 à 21:05 +0200, Marco Pesenti Gritti a
>> écrit :
>>
>>> Can you please explain what's exactly the role of the binary? Is  
>>> each
>>> activity runned from the binary? What does it provide?
>>>
>>
>> GCompris can be seen as a game engine, we call it the core, and each
>> activity rely on it to play. In our case, the gcompris binary  
>> contains
>> the game engine and within each activity directory you can find  
>> either a
>> bunch of C or python files for the activity code.
>>
>> For python activity, it would make sense to have a GCompris core in
>> python but for now we don't have it.
>>
>
> I'd suggest to have a look at sugar-native-factory.c in sugar git. You
> can either add something like that to the binary or use it as is to
> launch the binary.

For an example of its use, see the Etoys activity in git. If anything  
is unclear, feel free to ask.
(Continue reading)

Permalink | Reply | 12 comments |
headers
Jean Piché | 2 Jul 17:10

TamTam for Trial-2


Hello all,

The Trial-2 TamTam is slated for final release on July 8th.

Implemented feature set:

	Mic recording fully functional
	Keyboard recording fully functional
	Save tunes as .ogg audio files
	Variable number of beats per page
	Play Loop facilities
	
The following features will depend on Mesh and Journal stability/ 
usability over the next few days:

	Network synchronisation for TamTamJam (many machines can improvise/ 
play together on a shared pulse)
	Some Journal functionality to save and load TamTam tunes
	

Not implemented

	User interface is not Sugar compliant.
	The new and final design for TamTam will be unveiled later this  
summer and will be three distinct activities.
	

jp
(Continue reading)

Permalink | Reply | 1 comment |
headers
Tomeu Vizoso | 2 Jul 18:02

Re: [sugar] TamTam for Trial-2

Hi,

On Mon, 2007-07-02 at 11:10 -0400, Jean Piché wrote:
> The following features will depend on Mesh and Journal stability/ 
> usability over the next few days:
> 
> 	Network synchronisation for TamTamJam (many machines can improvise/ 
> play together on a shared pulse)
> 	Some Journal functionality to save and load TamTam tunes

Regarding the journal support, if you can write to and read from a file
on the fs (from python), then adding journal support will be trivial.

Thanks,

Tomeu

_______________________________________________
Devel mailing list
Devel <at> lists.laptop.org
http://lists.laptop.org/listinfo/devel
Permalink | Reply | 0 comments |
headers
Bruno Coudoin | 2 Jul 18:24
Picon
Favicon
Gravatar

Re: GComprisXO progress

Le lundi 02 juillet 2007 à 16:41 +0200, Marco Pesenti Gritti a écrit :
> Bruno Coudoin wrote:
> > Le dimanche 01 juillet 2007 à 21:05 +0200, Marco Pesenti Gritti a
> > écrit :
> >   
> >> Can you please explain what's exactly the role of the binary? Is each 
> >> activity runned from the binary? What does it provide?
> >>     
> >
> > GCompris can be seen as a game engine, we call it the core, and each
> > activity rely on it to play. In our case, the gcompris binary contains
> > the game engine and within each activity directory you can find either a
> > bunch of C or python files for the activity code.
> >
> > For python activity, it would make sense to have a GCompris core in
> > python but for now we don't have it.
> >   
> 
> I'd suggest to have a look at sugar-native-factory.c in sugar git. You 
> can either add something like that to the binary or use it as is to 
> launch the binary.

Hum, sounds great on paper. I'll check but won't work on it until the
end of the week, I am busy presenting GCompris at KDE-EDU in Akademy
2007 in Glasgow.

/humor: KDE teams try to make Gnome stall by inviting developers to
drink English beer.

Bruno.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane