[gcompris-devel] Segmentation fault CVS

Olivier Samyn osamyn at easynet.be
Fri Jan 30 17:45:18 UTC 2004


>>But I do not know if a script that adds a new board directly to the 
>>gcompris tree is the best solution.
>>Maybe creating a template application that compil and install from 
>>itself will be also a good idea.
>>This way, we can think about independant gcompris plugins like xmms plugins.
>>They can be maintained by someone other than only you  :)
>>
>>    
>>
>I agree also. That's two different use cases but both approach could
>help. 
>I already discussed with Stasz (from childsplay) about the opportunity
>to rewrite in python the gcompris core so that we could provide a 100%
>python gcompris with the boards in python. These board could be provided
>for windows as well without effort. But let's not dream, this is a lot
>of work.
>  
>
Seems a good idea from a interoperability point of view...

But I like the actual idea of having a framework written in C and some 
facilities to implement the different modules in python or why not other 
languages (If some one is interested I may try to recycle what is done 
for python in an other language).

But this framework needs probably a better gui abstraction layer than 
gnome-canvas.

I think maybe a first step will be something like define a 
gcompris-canvas API.
The first implementation will use direct gnome-canvas calls, but with 
time we may port this gcompris-canvas to other targets like for example 
pygame.

This will need a lot of work on definition of this canvas and on 
existing modules rewrite but... we will get some evolution...:)

There are also maybe some other projects interested in such a way of 
doing... and we may interact...

But let's talk about all of this maybe as freedem...
Building futur is easier when all actors are round a table with a good 
Belgian beer ;)

>>The only issue I foresee comes with i18n: the plugin should handle this 
>>itself.
>>If you want, I will try this way of doing.
>>
>>    
>>
>I don't see your point here. What's the issue and what do you mean by
>"that compil and install from itself". What to you put in this.
>  
>
I was thinking to real independant modules, that when you want to build 
them you do not need to rebuild/reinstall gcompris entirely.

Just like real plugins, you get them from a site, compile and install, 
no need to have the base program sources...

And the issue comes from the fact that thos plugins need to have their 
own gettext po files. They may use the gcompris one for some common 
translations, but need to have their own for the rest.

Olivier.





More information about the Gcompris-devel mailing list