I am interested in becoming a contributor to the SDL 1.3 SVN, is this
possible? If so how may I go about this?
Not that it’s much but I’ve updated SDL_opengl.h to include the current
version of glext to include openGL 3.2 functionality, I’ve also added an
optional include of the draft gl3.h header through the SDL_GL3 flag, along
with #ifdefs to ensure that gl.h/glu.h/glext.h aren’t included as these are
not compatible.
Yeah, if there’s any way to gain update access to the SVN repository, I’d like
to sign up too. I’ve got a handful of patches to both SDL and SDL_Image
that are just sitting around, apparently just because nobody’s gotten around
to applying them yet.
Hello,
I am interested in becoming a contributor to the SDL 1.3 SVN, is this
possible? If so how may I go about this?From: ali_lowe@sky.com (GMScribe)
Subject: [SDL] SVN Contributions
I am interested in becoming a contributor to the SDL 1.3 SVN, is this
possible? If so how may I go about this?
Not that it’s much but I’ve updated SDL_opengl.h to include the current
version of glext to include openGL 3.2 functionality, I’ve also added an
optional include of the draft gl3.h header through the SDL_GL3 flag, along
with #ifdefs to ensure that gl.h/glu.h/glext.h aren’t included as these are
not compatible.
Yeah, if there’s any way to gain update access to the SVN repository, I’d
like
to sign up too. I’ve got a handful of patches to both SDL and SDL_Image
that are just sitting around, apparently just because nobody’s gotten
around
to applying them yet.
Hello,
I am interested in becoming a contributor to the SDL 1.3 SVN, is this
possible? If so how may I go about this?
On the note of SDL_image, I’m aware that a large part of SDL now uses texturing rather than surfaces. Has anyone considered integrating openIL into SDL? It is a multiplatform API capable of loading more image formats than I can count, and can do so directly to texture with support for openGL (in fact uses openGL syntax), DirectX, GDI and Allergo. It even supports texture compression conversion/loading. If it could be wrapped up with SDL it would be great as it’s very powerful and simple to use. masonwheeler wrote:
From: GMScribe <@GMScribe>
Subject: [SDL] SVN Contributions
–
View this message in context: http://www.nabble.com/SVN-Contributions-tp24817954p24818374.html
Sent from the SDL mailing list archive at Nabble.com.
You can create a patch by using the svn diff (or di) command on the
modified working copy and piping the results to a new file.
For linux users this looks like:
user at computer ~ $ svn checkout http://svn.libsdl.org/trunk/SDL SDL-1.3
user at computer ~ $ cd SDL-1.3
user at computer ~/SDL-1.3 $
make your changes
user at computer ~/SDL-1.3 $ svn diff >…/my-changes-to-SDL.diff
create bug report and upload patch
You can use the same commands on DOS, Windows and probably Mac as long
as you have svn installed.
I’ve got a handful of patches to both SDL and SDL_Image
that are just sitting around, apparently just because nobody’s gotten around
to applying them yet.
Thanks for the advice. I’ve bug report posted some code for basic openGL 3.2
functionality and context creation in wgl and xgl so hopefully someone will
pay attention at some point! If I knew where the SDL were wanting to go with
future openGL support I’d be able to help out a lot more but without an idea
of their ideology for SDL 1.3 I can’t really propose any larger changes.
Many thanks.
Kenneth Bull wrote:>
2009/8/4 GMScribe <@GMScribe>:
Hello,
I am interested in becoming a contributor to the SDL 1.3 SVN, is this
possible? If so how may I go about this?
You can create a patch by using the svn diff (or di) command on the
modified working copy and piping the results to a new file.
For linux users this looks like:
user at computer ~ $ svn checkout http://svn.libsdl.org/trunk/SDL SDL-1.3
user at computer ~ $ cd SDL-1.3
user at computer ~/SDL-1.3 $
make your changes
user at computer ~/SDL-1.3 $ svn diff >…/my-changes-to-SDL.diff
create bug report and upload patch
You can use the same commands on DOS, Windows and probably Mac as long
as you have svn installed.
I can discuss the ideology for SDL 1.3, if that helps.
In general I give access to people who have repeatedly submitted good
quality patches through bugzilla or the mailing list.
See ya!On Thu, Aug 6, 2009 at 1:43 PM, GMScribe <ali_lowe at sky.com> wrote:
Thanks for the advice. I’ve bug report posted some code for basic openGL
3.2
functionality and context creation in wgl and xgl so hopefully someone will
pay attention at some point! If I knew where the SDL were wanting to go
with
future openGL support I’d be able to help out a lot more but without an
idea
of their ideology for SDL 1.3 I can’t really propose any larger changes.
You can create a patch by using the svn diff (or di) command on the
modified working copy and piping the results to a new file.
For linux users this looks like:
user at computer ~ $ svn checkout http://svn.libsdl.org/trunk/SDL SDL-1.3
user at computer ~ $ cd SDL-1.3
user at computer ~/SDL-1.3 $
make your changes
user at computer ~/SDL-1.3 $ svn diff >…/my-changes-to-SDL.diff
create bug report and upload patch
You can use the same commands on DOS, Windows and probably Mac as long
as you have svn installed.
I’ve already gone and replied to another post but, please, if you could
discuss the ideology of SDL 1.3 it would be a great help. It’ll be good to
know where you and your team are wanting to go with the API so that 3rd
party contributors are spending their time making relevant changes
in-keeping with with the ideals that the API is trying to reach.
For example, though currently out of date, one consideration was to
integrate GLEW into SDL. Its only purpose is to speed up user access to
openGL extensions by handling the binding of extensions and the introduction
of extensions addressable as core features. It is also highly multiplatform.
Would this be a good idea as the functionality can be entirely hidden from
the end user?
Another prospect is the integration of openIL for SDL_image. Again
multiplatform and on the same licensing conditions as SDL. It uses
essentially the same APIs as the current SDL_image but supports many many
more formats, including advanced features such as direct to texture, high
quality scaling/effects optionally and texture compression. Which I believe
would suit the upcoming texture based 2d renderer quite well. In this
situation it would be nice to know just what you’d need out of the API and
at what points we could look to exploit these features for better
integration with SDL.
Many thanks.
Sam Lantinga-4 wrote:>
I can discuss the ideology for SDL 1.3, if that helps.
In general I give access to people who have repeatedly submitted good
quality patches through bugzilla or the mailing list.
See ya!
On Thu, Aug 6, 2009 at 1:43 PM, GMScribe <@GMScribe> wrote:
Thanks for the advice. I’ve bug report posted some code for basic openGL
3.2
functionality and context creation in wgl and xgl so hopefully someone
will
pay attention at some point! If I knew where the SDL were wanting to go
with
future openGL support I’d be able to help out a lot more but without an
idea
of their ideology for SDL 1.3 I can’t really propose any larger changes.
Many thanks.
Kenneth Bull wrote:
2009/8/4 GMScribe <@GMScribe>:
Hello,
I am interested in becoming a contributor to the SDL 1.3 SVN, is this
possible? If so how may I go about this?
You can create a patch by using the svn diff (or di) command on the
modified working copy and piping the results to a new file.
For linux users this looks like:
user at computer ~ $ svn checkout http://svn.libsdl.org/trunk/SDL SDL-1.3
user at computer ~ $ cd SDL-1.3
user at computer ~/SDL-1.3 $
make your changes
user at computer ~/SDL-1.3 $ svn diff >…/my-changes-to-SDL.diff
create bug report and upload patch
You can use the same commands on DOS, Windows and probably Mac as long
as you have svn installed.
While GLEW seems incredibly useful for someone working with OpenGL
(and SDL), it seems like a fairly hefty chunk to add to the core SDL
distribution. I’d be open to it being an optional module, or even
just linked from the SDL website.
As for openIL, is that perhaps a successor to SDL_image? Maybe there
just needs to be an SDL surface module added to it?
Mostly the intent is for SDL to be a very powerful core over which
people can layer lots of additional functionality.
See ya!On Fri, Aug 7, 2009 at 2:23 AM, GMScribe <ali_lowe at sky.com> wrote:
I’ve already gone and replied to another post but, please, if you could
discuss the ideology of SDL 1.3 it would be a great help. It’ll be good to
know where you and your team are wanting to go with the API so that 3rd
party contributors are spending their time making relevant changes
in-keeping with with the ideals that the API is trying to reach.
For example, though currently out of date, one consideration was to
integrate GLEW into SDL. Its only purpose is to speed up user access to
openGL extensions by handling the binding of extensions and the introduction
of extensions addressable as core features. It is also highly multiplatform.
Would this be a good idea as the functionality can be entirely hidden from
the end user?
Another prospect is the integration of openIL for SDL_image. Again
multiplatform and on the same licensing conditions as SDL. It uses
essentially the same APIs as the current SDL_image but supports many many
more formats, including advanced features such as direct to texture, high
quality scaling/effects optionally and texture compression. Which I believe
would suit the upcoming texture based 2d renderer quite well. In this
situation it would be nice to know just what you’d need out of the API and
at what points we could look to exploit these features for better
integration with SDL.
Many thanks.
Sam Lantinga-4 wrote:
I can discuss the ideology for SDL 1.3, if that helps.
In general I give access to people who have repeatedly submitted good
quality patches through bugzilla or the mailing list.
See ya!
On Thu, Aug 6, 2009 at 1:43 PM, GMScribe <ali_lowe at sky.com> wrote:
Thanks for the advice. I’ve bug report posted some code for basic openGL
3.2
functionality and context creation in wgl and xgl so hopefully someone
will
pay attention at some point! If I knew where the SDL were wanting to go
with
future openGL support I’d be able to help out a lot more but without an
idea
of their ideology for SDL 1.3 I can’t really propose any larger changes.
You can create a patch by using the svn diff (or di) command on the
modified working copy and piping the results to a new file.
For linux users this looks like:
user at computer ~ $ svn checkout http://svn.libsdl.org/trunk/SDL SDL-1.3
user at computer ~ $ cd SDL-1.3
user at computer ~/SDL-1.3 $
make your changes
user at computer ~/SDL-1.3 $ svn diff >…/my-changes-to-SDL.diff
create bug report and upload patch
You can use the same commands on DOS, Windows and probably Mac as long
as you have svn installed.
GLEW is a heavy add-on. Though the concepts of how GLEW works should be
portable to an SDL specific release for full integration as an add-on as you
suggest. I got most of the way to producing one, however landed into some
minor issues regarding where to store context specific information
(currently we return openGL context handlers in SDL but not an object that
could contain x amount of information) and I would have liked to integrate
it more completely before posting it as a patch, sadly I’ve ran out of time
for the near future.
openIL I think would be a great successor to SDL_image. It’s much more
powerful and supports many more image formats. It actually already has
SDL_surface code and I have used this in an SDL 1.3 project. I can’t
remember if you need to comment it back in and rebuild the source though.
Sam Lantinga-4 wrote:>
While GLEW seems incredibly useful for someone working with OpenGL
(and SDL), it seems like a fairly hefty chunk to add to the core SDL
distribution. I’d be open to it being an optional module, or even
just linked from the SDL website.
As for openIL, is that perhaps a successor to SDL_image? Maybe there
just needs to be an SDL surface module added to it?
Mostly the intent is for SDL to be a very powerful core over which
people can layer lots of additional functionality.
See ya!
On Fri, Aug 7, 2009 at 2:23 AM, GMScribe <@GMScribe> wrote:
I’ve already gone and replied to another post but, please, if you could
discuss the ideology of SDL 1.3 it would be a great help. It’ll be good
to
know where you and your team are wanting to go with the API so that 3rd
party contributors are spending their time making relevant changes
in-keeping with with the ideals that the API is trying to reach.
For example, though currently out of date, one consideration was to
integrate GLEW into SDL. Its only purpose is to speed up user access to
openGL extensions by handling the binding of extensions and the
introduction
of extensions addressable as core features. It is also highly
multiplatform.
Would this be a good idea as the functionality can be entirely hidden
from
the end user?
Another prospect is the integration of openIL for SDL_image. Again
multiplatform and on the same licensing conditions as SDL. It uses
essentially the same APIs as the current SDL_image but supports many many
more formats, including advanced features such as direct to texture, high
quality scaling/effects optionally and texture compression. Which I
believe
would suit the upcoming texture based 2d renderer quite well. In this
situation it would be nice to know just what you’d need out of the API
and
at what points we could look to exploit these features for better
integration with SDL.
Many thanks.
Sam Lantinga-4 wrote:
I can discuss the ideology for SDL 1.3, if that helps.
In general I give access to people who have repeatedly submitted good
quality patches through bugzilla or the mailing list.
See ya!
On Thu, Aug 6, 2009 at 1:43 PM, GMScribe <@GMScribe> wrote:
Thanks for the advice. I’ve bug report posted some code for basic
openGL
3.2
functionality and context creation in wgl and xgl so hopefully someone
will
pay attention at some point! If I knew where the SDL were wanting to go
with
future openGL support I’d be able to help out a lot more but without an
idea
of their ideology for SDL 1.3 I can’t really propose any larger
changes.
Many thanks.
Kenneth Bull wrote:
2009/8/4 GMScribe <@GMScribe>:
Hello,
I am interested in becoming a contributor to the SDL 1.3 SVN, is
this
You can create a patch by using the svn diff (or di) command on the
modified working copy and piping the results to a new file.
For linux users this looks like:
user at computer ~ $ svn checkout http://svn.libsdl.org/trunk/SDL
SDL-1.3
user at computer ~ $ cd SDL-1.3
user at computer ~/SDL-1.3 $
make your changes
user at computer ~/SDL-1.3 $ svn diff >…/my-changes-to-SDL.diff
create bug report and upload patch
You can use the same commands on DOS, Windows and probably Mac as
long
as you have svn installed.
