SDL 2.0 ABI locked

As of tonight, SDL 2.0 is ABI locked!

This means that no breaking changes will happen to the API until SDL 3.

Cheers!

As of tonight, SDL 2.0 is ABI locked!

This means that no breaking changes will happen to the API until SDL 3.

Wow, good news!

And if the time period between 2 -> 3 will be the same of 1 -> 2 I will be
already retired (hoping that retirement funds will still exist in 20 years)
:)On Fri, Mar 8, 2013 at 5:50 AM, Sam Lantinga wrote:


Bye,
Gabry

Agreed :slight_smile:
Glad that this http://hg.libsdl.org/SDL/rev/b73d51026c68 happened in time!

VittorioOn Fri, Mar 8, 2013 at 5:50 AM, Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!

This means that no breaking changes will happen to the API until SDL 3.

Cheers!


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Wait! We never changed SDL_INIT_EVERYTHING! Is this attached patch okay?

(Also, can we remove SDL_INIT_GAMECONTROLLER and just make that part of
SDL_INIT_JOYSTICK? If not, I’m okay with that, but it seems like a
reasonable change.)

–ryan.

-------------- next part --------------

HG changeset patch

User Ryan C. Gordon <@icculus>

Date 1362760688 18000

Node ID 3a7557947a01ee31fc6072b1c9f399c2058a76c6

Parent 8d6ab3bdc08bd79393cacd3a2e3991da196128fd

Changed SDL_INIT_EVERYTHING to only request currently-known subsystems.

diff --git a/include/SDL.h b/include/SDL.h
— a/include/SDL.h
+++ b/include/SDL.h
@@ -114,7 +114,10 @@
#define SDL_INIT_HAPTIC 0x00001000
#define SDL_INIT_GAMECONTROLLER 0x00002000 /< turn on game controller also implicitly does JOYSTICK */
#define SDL_INIT_NOPARACHUTE 0x00100000 /
< Don’t catch fatal signals */
-#define SDL_INIT_EVERYTHING 0x0000FFFF
+#define SDL_INIT_EVERYTHING ( \

  •            SDL_INIT_TIMER | SDL_INIT_AUDIO | SDL_INIT_VIDEO | \
    
  •            SDL_INIT_JOYSTICK | SDL_INIT_HAPTIC | SDL_INIT_GAMECONTROLLER \
    
  •        )
    

/@}/

/**On 03/07/2013 11:50 PM, Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!

(Also, can we remove SDL_INIT_GAMECONTROLLER and just make that part of SDL_INIT_JOYSTICK? If not, I’m okay with that, but it seems like a reasonable change.)

More so reasonable since I added in SDL_GameControllerAddMapping so that mapping can be added & updated in AFTER init. So there’s no real reason to use the HINT anymore, other than to pick up configs from Steam via the ENV. (see my other post about change set 6976)

–ryan.

<SDL-init-everything-mask-RYAN1.diff>_______________________________________________
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Edward Rudd
OutOfOrder.cc
Skype: outoforder_cc
317-674-3296On Mar 8, 2013, at 11:40 , Ryan C. Gordon wrote:

2013/3/8 Ryan C. Gordon > On 03/07/2013 11:50 PM, Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!

Wait! We never changed SDL_INIT_EVERYTHING! Is this attached patch okay?

(Also, can we remove SDL_INIT_GAMECONTROLLER and just make that part of
SDL_INIT_JOYSTICK? If not, I’m okay with that, but it seems like a
reasonable change.)

–ryan.

If this gets accepted, please somehow attach the Indiana Jones theme to the
commit comment.

Sorry, couldn’t help it :slight_smile:


Gabriel.

The INIT_EVERYTHING patch is fine, it doesn’t affect ABI directly.

SDL_INIT_GAMECONTROLLER is locked, since there is already code in the wild
using it. I think it’s okay if people specifically request the game
controller system.On Fri, Mar 8, 2013 at 8:40 AM, Ryan C. Gordon wrote:

On 03/07/2013 11:50 PM, Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!

Wait! We never changed SDL_INIT_EVERYTHING! Is this attached patch okay?

(Also, can we remove SDL_INIT_GAMECONTROLLER and just make that part of
SDL_INIT_JOYSTICK? If not, I’m okay with that, but it seems like a
reasonable change.)

–ryan.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

The INIT_EVERYTHING patch is fine, it doesn’t affect ABI directly.

Pushed.

–ryan.

The INIT_EVERYTHING patch is fine, it doesn’t affect ABI directly.

Pushed.

Oh, I forgot…here you go, Gabriel:

 http://www.youtube.com/watch?v=2ui85HwTX1s

–ryan.

Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!
This means that no breaking changes will happen to the API until SDL 3.
Cheers!

Nice.

But, did the sensor api got approved?
If so, is there someone willing to work on a iOS implementation?
http://bugzilla.libsdl.org/show_bug.cgi?id=1717
and about the Android Joystick support? (which have some breaking changes as accelerometers are not joysticks, right?)
http://bugzilla.libsdl.org/show_bug.cgi?id=1700

Cheers!------------------------
Rodrigo Cardoso Rocha
@RodrigoRodrigoR - twitter.com/RodrigoRodrigoR
Chibata Creations - chibatacreations.com
Joystick Mapper for Mac - joystickmapper.com

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.On Mon, Mar 11, 2013 at 11:21 PM, RodrigoCard wrote:

**

Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!
This means that no breaking changes will happen to the API until SDL 3.
Cheers!

Nice.

But, did the sensor api got approved?
If so, is there someone willing to work on a iOS implementation?
http://bugzilla.libsdl.org/show_bug.cgi?id=1717
and about the Android Joystick support? (which have some breaking changes
as accelerometers are not joysticks, right?)
http://bugzilla.libsdl.org/show_bug.cgi?id=1700

Cheers!


Rodrigo Cardoso Rocha
@RodrigoRodrigoR - twitter.com/RodrigoRodrigoR
Chibata Creations - chibatacreations.com
Joystick Mapper for Mac - joystickmapper.com


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

And even add to existing APIs too, I presume :stuck_out_tongue: Or even improve the
existing ones as long as they’re fully backwards compatible. Just do
nothing that would break already existent programs at the moment of
the freeze.

Sorry for the remark, but when I see “add new APIs” I think "add a
completely new set of functions not related to the ones already there"
and I’m pretty sure ABI compatibility is more flexible than that ^^;

2013/3/13, Sam Lantinga :> The sensor API is on my list. We can still add new APIs, we just can’t

break any existing ones.

On Mon, Mar 11, 2013 at 11:21 PM, RodrigoCard wrote:

**

Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!
This means that no breaking changes will happen to the API until SDL 3.
Cheers!

Nice.

But, did the sensor api got approved?
If so, is there someone willing to work on a iOS implementation?
http://bugzilla.libsdl.org/show_bug.cgi?id=1717
and about the Android Joystick support? (which have some breaking changes
as accelerometers are not joysticks, right?)
http://bugzilla.libsdl.org/show_bug.cgi?id=1700

Cheers!


Rodrigo Cardoso Rocha
@RodrigoRodrigoR - twitter.com/RodrigoRodrigoR
Chibata Creations - chibatacreations.com
Joystick Mapper for Mac - joystickmapper.com


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Can I request a scissor API? Similar to Viewport, but without mucking up the coordinate system. Most GUI libraries that could potentially interface with SDL2.0 require it (and would need to be modified extensively to work with Viewport instead), and it would be convenient for making a GUI intended only for SDL as well.

It’s simple enough to make a wrapper around SDL_RenderCopy for non-rotated rendering, but it seems to be impossible to consistently scissor rotated rendering from outside the SDL itself without using a render target, which is inefficient and may not always be an option.

Functionality would ideally be identical to glScissor in OpenGL, SetScissorRect in D3D, or SDL_SetClipRect in SDL 1.2------------------------
EM3 Nathaniel Fries, U.S. Navy

http://natefries.net/

Should we make an SDL-2.0 branch, and start calling the default branch
"2.1"?

–ryan.On 03/13/2013 11:42 AM, Sam Lantinga wrote:

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.

Well, given that SDL 2.0’s ABI is already frozen, I suppose that calls
for work to start on 2.1 (unless you want 2.0 to be only partially
stable, that is :P).

I wouldn’t mind moving to 2.1. Feels like a victory :smiley:

2013/3/13, Ryan C. Gordon :> On 03/13/2013 11:42 AM, Sam Lantinga wrote:

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.

Should we make an SDL-2.0 branch, and start calling the default branch
"2.1"?

–ryan.


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

No, not yet. Let’s get a release out first. :)On Wed, Mar 13, 2013 at 2:30 PM, Ryan C. Gordon wrote:

On 03/13/2013 11:42 AM, Sam Lantinga wrote:

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.

Should we make an SDL-2.0 branch, and start calling the default branch
"2.1"?

–ryan.

_____________**
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/**listinfo.cgi/sdl-libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

That’s correct.On Wed, Mar 13, 2013 at 9:32 AM, Sik the hedgehog < sik.the.hedgehog at gmail.com> wrote:

And even add to existing APIs too, I presume :stuck_out_tongue: Or even improve the
existing ones as long as they’re fully backwards compatible. Just do
nothing that would break already existent programs at the moment of
the freeze.

Sorry for the remark, but when I see “add new APIs” I think "add a
completely new set of functions not related to the ones already there"
and I’m pretty sure ABI compatibility is more flexible than that ^^;

2013/3/13, Sam Lantinga <@slouken>:

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.

On Mon, Mar 11, 2013 at 11:21 PM, RodrigoCard wrote:

**

Sam Lantinga wrote:

As of tonight, SDL 2.0 is ABI locked!
This means that no breaking changes will happen to the API until SDL 3.
Cheers!

Nice.

But, did the sensor api got approved?
If so, is there someone willing to work on a iOS implementation?
http://bugzilla.libsdl.org/show_bug.cgi?id=1717
and about the Android Joystick support? (which have some breaking
changes

as accelerometers are not joysticks, right?)
http://bugzilla.libsdl.org/show_bug.cgi?id=1700

Cheers!


Rodrigo Cardoso Rocha
@RodrigoRodrigoR - twitter.com/RodrigoRodrigoR
Chibata Creations - chibatacreations.com
Joystick Mapper for Mac - joystickmapper.com


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org


SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

If you do this, an official tarball for 2.0, even if marked beta or
something, would also be nice. I think this was even asked for today in the
irc channel.

Oh, I was writing this when I saw your mail, Sam :slight_smile:

2013/3/13 Ryan C. Gordon > On 03/13/2013 11:42 AM, Sam Lantinga wrote:

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.

Should we make an SDL-2.0 branch, and start calling the default branch
"2.1"?

–ryan.

_____________**
SDL mailing list
SDL at lists.libsdl.org
http://lists.libsdl.org/**listinfo.cgi/sdl-libsdl.orghttp://lists.libsdl.org/listinfo.cgi/sdl-libsdl.org

Message-ID:

Content-Type: text/plain; charset=“iso-8859-1”

No, not yet. Let’s get a release out first. :slight_smile:

The sensor API is on my list. We can still add new APIs, we just can’t
break any existing ones.

Should we make an SDL-2.0 branch, and start calling the default branch
"2.1"?

–ryan.

Besides which, I at least would expect the “default” branch to be the
patch series for the most recent release branch, not the current dev
branch :wink: .> Date: Wed, 13 Mar 2013 14:46:09 -0700

From: Sam Lantinga
To: SDL Development List
Subject: Re: [SDL] SDL 2.0 ABI locked
On Wed, Mar 13, 2013 at 2:30 PM, Ryan C. Gordon wrote:

On 03/13/2013 11:42 AM, Sam Lantinga wrote:

No, not yet. Let’s get a release out first. :slight_smile:

Oh, I thought this was a release. :slight_smile:

–ryan.