Re: [pygame] summer of code: OSC networking proposal

[Alexandre Quessy <alexandre@xxxxxxxxxx>]

Hello everyone,
Using OSC with Pygame should already be quite easy with Twisted and our
OSC library. See http://bitbucket.org/arjan/twisted-osc/

I don't really like how pygame re-writes everything in itself, rather
than improving and using already existing code. For example, it would
have been better, IMHO, to put the camera in SDL, not in Pygame. Same
for the MIDI. I also had to port the changes to MIDI upstream. (and I am
planning to bring it all the way to portmidi) The work would only need
to be done, and not twice like right now, if you guys were not
implementing everything in Pygame, instead of where it should be -
upstream.

Regards,
Alexandre


Marcus von Appen wrote:
> Hi Gabe,
> 
> On, Tue Apr 06, 2010, Gabe Silk wrote:
> 
> [...]
> 
>> *Timeline*
>> Week 1: Finalize design and intended API
>> Week 2-3: Implement OSC Server
>> Weeks 4-5: Implement OSC Client and Message classes, work on first example
>> application
>> Week 6-7: Implement Bundles, complete first example application
>> Week 8: Finalize multicast API
>> Week 9-10: Implement multicast, complete second example application
>> Week 11: System and integration testing; complete third example application
>> Week 12: Finish up documentation for system and examples
> 
> I'm not sure, whether it would fit your timeline, but an integration or
> interface of the available portmidi interface of pygame (pygame.midi)
> with your message classes would be quite helpful for most people, I
> think. That would allow some easy bridging from the midi-based
> controller application to an OSC server being available elsewhere
> without having to create the bridge manually.
> 
> Though that might be something edgy for several midi devices (due to the
> open namespaces for OSC) and incompatibilities with MIDI, some generic
> message type might help people to get their stuff up and running much
> faster.
> 
> Regards
> Marcus