Mercurial > sdl-ios-xcode
view TODO @ 956:4263beff9e38
Date: Mon, 30 Aug 2004 18:20:25 +0200
From: Joost Baas
Subject: why call arts artsc?
I, and a few other people at the mplayer-docs-mailinglist were wondering why
you decided to call arts artsc. I understand usually users have nothing to do
with libsdl, just developers, but because you can choose the audio-driver
being used by mplayer, one of which is sdl, and you can also choose the sdl
subdriver, it is necessary to have a well-known or logical name. artsc is not
the logical choice, and it's very hard to look up the right name if you don't
know what you're looking for.
| author | Sam Lantinga <slouken@libsdl.org> |
|---|---|
| date | Fri, 17 Sep 2004 13:25:06 +0000 |
| parents | df1d68818edb |
| children | 19418e4422cb |
line wrap: on
line source
Wish list for the 1.3 development branch: * Use /etc/fb.modes, if available, like GGI does * Add mousewheel events (new unified event architecture?) * DirectInput joystick support needs to be implemented * Be able to enumerate and select available audio and video drivers * Fullscreen video mode support for MacOS X * Explicit vertical retrace wait (maybe separate from SDL_Flip?) * Shaped windows, windows without borders * Multiple windows, multiple display support * SDL_INIT_EVENTTHREAD on Windows and MacOS? * Add a timestamp to events * Use RDTSC for timer resolution on x86 hardware * Add audio input API * Add hardware accelerated scaled blit * Add hardware accelerated alpha blits * Redesign blitting architecture to allow blit plugins In the jump from 1.2 to 1.3, we should change the SDL_Rect members to int and evaluate all the rest of the datatypes. This is the only place we should do it though, since the 1.2 series should not break binary compatibility in this way. Requests: * PCM and CDROM volume control (deprecated, but possible)