Personally, I think idler should go into soya, not py2play. Why? Because I want to use FPS and what appears to be some other timing functions, but I'm not using py2play. :)
On Wed, 2003-01-15 at 16:24, Jiba wrote: > On Tue, 14 Jan 2003 15:01:03 -0800 > Sean Lynch <[EMAIL PROTECTED]> wrote: > > > I was trying to make a first person camera to use with my modified > > version of the landscape tutorial. I noticed that game.level already has > > several camera classes in it, but game.level depends on Py2Play. The > > camera classes in game.level don't use any Py2Play objects, however. > > For now, I will probably just try copying the appropriate classes into > > my code, but I think it might make sense to keep the parts of game that > > don't require Py2Play in separate modules. I don't think I'll be using > > Py2Play since it uses peer to peer networking whereas I will be using > > client server networking. > > Yes you are right. That is exactely the job of the soya.game module... > > Soya and Py2Play have been designed to interface well, though both are independant. > > As the traveling camera is independant of the level stuff, i think the best is to >create a new soya.game.camera module with it. > > BTW you may look at py2Play.idler; this file contains a main loop featuring FPS >regulation. Actually i don't figure if the Idler should go in PY2play (as it is >currently) or in Soya... any idea ??? > > When Slune will be more stable, i'll look more closely at what should go in Slune, >in Soya or in Py2Play. > > Jiba > > > -- > Pour vous desabonner envoyez un mail a [EMAIL PROTECTED] > -- Pour vous desabonner envoyez un mail a [EMAIL PROTECTED]
