[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[pygame] Pygame support for both SDL and DirectFB
- To: pygame-users@seul.org
- Subject: [pygame] Pygame support for both SDL and DirectFB
- From: =?koi8-r?Q?=22?=Dmitry Borisov=?koi8-r?Q?=22=20?= <jbors@mail.ru>
- Date: Thu, 08 Jan 2004 22:31:59 +0300
- Delivered-to: archiver@seul.org
- Delivered-to: pygame-users-outgoing@seul.org
- Delivered-to: pygame-users@seul.org
- Delivery-date: Thu, 08 Jan 2004 14:32:21 -0500
- Reply-to: pygame-users@seul.org
- Sender: owner-pygame-users@seul.org
Guys,
Just trying to understand the need of the above.
I was pretty bored when trying SDL to use all features of my CLE266 chipset through using DirectFB. In some cases it works 8 times slower, in some it does not work at all.
I was trying to fix that miscommunication in SDL but realized that it would be very messy to use DirectFB from python through pygame->SDL->DFB. Very long run isn't it ?
My next guess was to use pydfb to get that thing working. But it has very weird and raw interface, so I can hardly do something serious with it.
So I came up to the need for pygame to support DirectFB. The major reason for that is performance. SDL->DirectFB giving me 10-12 MPix/sec ( 7-8 MPix/sec with pygame+psyco ) whereas the same DirectFB app can easily run up to 80 MPix/sec.
My questions would be:
Is it really mean to someone to have pygame using DirectFB as a displaying layer ?
Don't you think it would be too bad to have pygame->DFB on linux only ( meaning no portability in this case ) ?
Any comments ? Thoughts ?
Thanks,
Dmitry/