I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3, but
I wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
That’s really awesome Sam! It might step on a few people’s toes, but it’s
for the greater good, I think.
Keep up the good work!
-OzOn Sun, Jan 22, 2012 at 2:20 PM, Sam Lantinga wrote:
I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3, but
I wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
2012/1/22 Alex Barry <alex.barry at gmail.com>> That’s really awesome Sam! It might step on a few people’s toes, but it’s
for the greater good, I think.
Keep up the good work!
-Oz
On Sun, Jan 22, 2012 at 2:20 PM, Sam Lantinga wrote:
I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3, but
I wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
Great :)On 01/22/2012 11:20 AM, Sam Lantinga wrote:
I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy process because there’s a lot of documentation that refers to SDL 1.3, but I wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility layer, and future SDL_* libraries are also going to switch to SDL2, e.g. SDL2_image, etc.
–
LordHavoc
Author of DarkPlaces Quake1 engine - http://icculus.org/twilight/darkplaces
Co-designer of Nexuiz - http://alientrap.org/nexuiz
"War does not prove who is right, it proves who is left." - Unknown
"Any sufficiently advanced technology is indistinguishable from a rigged demo." - James Klass
"A game is a series of interesting choices." - Sid Meier
If someone else wanted to maintain it, I wonder if a SDL2_compat could be a
separate library? Can you please give an idea if this would be impossible,
or too hard to do? I’m guessing it would be impossible, since there aren’t
really any hooks for it.
So the migration process for old code is now port to SDL2? It should be
impossible to write a library that uses either 1.2 or 2.
cheers,On Sun, Jan 22, 2012 at 8:20 PM, Sam Lantinga wrote:
I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3, but
I wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
2012/1/22 Sam Lantinga :> I’m in the process of switching over SDL 1.3 to SDL2. ?It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3, but I
wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
Sure, if you want to change 1.3 to 2.0 in the wiki that would be very
helpful. Let me know once you have a wiki account and I’ll give you edit
access.
Thanks!On Mon, Jan 23, 2012 at 5:19 AM, Michael Bonfils wrote:
How can we help you on wiki part ?
Can I just rename SDL1.3 to SDL2 in first step ?
2012/1/22 Sam Lantinga <@slouken>:
I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3,
but I
wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
You wouldn’t want it as a separate library, but I’ll definitely put the
zlib licensed SDL_compat.h/c up as a resource for people to use or learn
from.On Mon, Jan 23, 2012 at 12:19 AM, Ren? Dudfield wrote:
Hello,
If someone else wanted to maintain it, I wonder if a SDL2_compat could be
a separate library? Can you please give an idea if this would be
impossible, or too hard to do? I’m guessing it would be impossible, since
there aren’t really any hooks for it.
So the migration process for old code is now port to SDL2? It should be
impossible to write a library that uses either 1.2 or 2.
cheers,
On Sun, Jan 22, 2012 at 8:20 PM, Sam Lantinga <@slouken> wrote:
I’m in the process of switching over SDL 1.3 to SDL2. It’ll be a lengthy
process because there’s a lot of documentation that refers to SDL 1.3, but
I wanted to give everyone a heads up.
One of the implications of this is that I’m removing the compatibility
layer, and future SDL_* libraries are also going to switch to SDL2, e.g.
SDL2_image, etc.
If someone else wanted to maintain it, I wonder if a SDL2_compat could
be a separate library? Can you please give an idea if this would be
impossible, or too hard to do? I’m guessing it would be impossible,
since there aren’t really any hooks for it.
I think this is possible to do; part of the problem with the compat
layer is the intermingling of incompatible 1.2+1.3 calls, but a separate
library, that provides nothing but the 1.2 API and talks to nothing but
1.3 behind the scenes, should be possible.
I haven’t considered this fully, but the idea of building an add-on
library like SDL_mixer, named SDL_compat12, crossed my mind, too.
So the migration process for old code is now port to SDL2? It should be
impossible to write a library that uses either 1.2 or 2.
That’s not the explicit goal, but that is a side effect of the current
approach. With some small amount of #ifdefs, a program can use either,
but you won’t be able to just drop SDL2 into an app that’s linked
against 1.2.
The expectation is that 1.2 is always available if you want it, but code
should plan to migrate to SDL2 eventually. In most cases, the migration
isn’t difficult at all.
We are using SDL ver 1.2.15 for our project.
Currently SDL Window (or screen) is created by one of the SDL APIs. Can
I supply this window handle from outside and have SDL library use this
HANDLE for drawing instead of creating a new one.
Another step should to verify that API description is synchronized
with SDL.h, few month ago, I was checking wiki and it was out-dated (
I don’t remember which ones )
Another step should to verify that API description is synchronized
with SDL.h, few month ago, I was checking wiki and it was out-dated (
I don’t remember which ones )