[SDL] compiling with SDL_NO_COMPAT
bob at pendleton.com
Wed Jan 4 19:24:53 PST 2012
On Wed, Jan 4, 2012 at 8:26 PM, Mason Wheeler <masonwheeler at yahoo.com> wrote:
> If you removed the graphics subsystem from SDL, you'd have to move the
> input/events subsystem as well, since the two are tightly coupled due to the
> way pretty much all OSes work. Remove those two subsystems and what's left
> of the SDL core?
User input events are usually tied to windows so the events system and
the windowing system are usually tightly coupled. The windowing system
and the graphics system are also tightly coupled because the
windowing system has to inform the graphics system where it is
permitted to draw on the screen, but they are not otherwise involved
with each other.
Seriously, looking at the SDL events list I don't see on that is from
the graphics system. I see one class from windows, and one from the
window manager, but none from the graphics system.
> From: Jonathan Dearborn <grimfang4 at gmail.com>
> To: SDL Development List <sdl at lists.libsdl.org>
> Sent: Wednesday, January 4, 2012 6:19 PM
> Subject: Re: [SDL] compiling with SDL_NO_COMPAT
> Splitting the rendering API into its own library is what I was thinking (I
> think my last post got held up in the moderation queue). That would keep
> SDL itself nice and clean whereas the add-on would expose the accelerated
> features that many of us need.
> Jonny D
> SDL mailing list
> SDL at lists.libsdl.org
+ Bob Pendleton: writer and programmer
+ email: Bob at Pendleton.com
+ web: www.TheGrumpyProgrammer.com
More information about the SDL