[Pythonmac-SIG] porting PyOpenGL to Mac OS X
John Schmitt
jschmitt@ati.com
Mon, 24 Jun 2002 15:57:02 -0700
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C21BD2.7466C710
Content-Type: text/plain;
charset="iso-8859-1"
Did you guys receive this? Does this answer your question about why they're
using the old SWIG?
John
-----Original Message-----
From: Mike C. Fletcher [mailto:mcfletch@rogers.com]
Sent: Sunday, June 23, 2002 7:17 PM
To: Python List; PyOpenGL
Subject: [PyOpenGL] Need for a C (lead) developer...
Summary:
PyOpenGL (the Python binding to the OpenGL graphics library) is in
need
of a C developer (preferably with SWIG experience) to work on
maintaining and extending the package. Need is both short-term and
long-term; we could use an immediate helping hand, but we're also
looking for someone interested in long term work.
PyOpenGL is a fairly large project (source-size), which is used by a
considerable number of people (latest version has been downloaded
something like 16,000 times). Developers looking to take on a popular
project and make a name for themselves would find this a good opportunity.
Current Tasks:
PyOpenGL is currently generated using an old version of the SWIG
wrapper
generator (originally chosen because of missing features in other
versions of SWIG with the idea that the missing features would
eventually be adopted in newer SWIG versions (status of this unknown,
but some work is definitely required to use the newer versions)). This
build process tends to create lots of problems for those porting to new
architectures, and we'd like to move off the (old, beta) version soon.
This is a fairly extensive project, and will require familiarising
yourself with the code base before making the attempt.
We have a number of cross-platform build issues that need to be
coordinated and integrated. In one case, we have already-submitted
patches/fixes for fixing bug(s), in others, there are patches not yet
submitted, but available. We need these integrated and tested.
Integration is the developer requirement, we can get users with the
exotic architectures to test the fixed versions.
We have reports of complete meltdown under OpenGL 1.3
implementations
under Linux. This is likely a trivial build or configuration problem,
but it needs to be tracked down.
Future Tasks:
Maintenance of the package.
Creation of new wrappers for common OpenGL modules (optional).
Simplification of the build system for exotic architectures.
Insert your PyOpenGL dreams here.
Resources:
The project has 3 administrators, myself (a designer with minimal
(read
non-existent) C coding skills), Tarn (author of the current code
(current missing in action)) and Rene (who is/was primarily interested
in the building and porting work). I work primarily on the
OpenGLContext side (which provides a series of tests for the base
implementation, and tends to uncover errors as I develop it). I tend to
do the work on the web-site, and general answering of questions when I can.
At the moment, we have no active C developers, and just myself
working on
the administrative front. The PyOpenGL work I'm doing is minimal due to
other projects and the fact that I'm largely unqualified for the work
that needs to be done. I am working on a way to use fonttools for
rendering 3D text in PyOpenGL+OpenGLContext, but that's not going to
help with the general coding that needs to get done.
How to Get Involved:
If you'd be interested in working as a developer, let me know and
I'll
see about adding you to the developer list. People familiar with the
PyOpenGL codebase and project would be especially welcome.
http://pyopengl.sourceforge.net/
With thanks,
Mike Fletcher
_______________________________________
Mike C. Fletcher
http://members.rogers.com/mcfletch/
--
http://mail.python.org/mailman/listinfo/python-list
------_=_NextPart_001_01C21BD2.7466C710
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>[Pythonmac-SIG] porting PyOpenGL to Mac OS X</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Did you guys receive this? Does this answer =
your question about why they're using the old SWIG?</FONT>
</P>
<P><FONT SIZE=3D2>John</FONT>
</P>
<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Mike C. Fletcher [<A =
HREF=3D"mailto:mcfletch@rogers.com">mailto:mcfletch@rogers.com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: Sunday, June 23, 2002 7:17 PM</FONT>
<BR><FONT SIZE=3D2>To: Python List; PyOpenGL</FONT>
<BR><FONT SIZE=3D2>Subject: [PyOpenGL] Need for a C (lead) =
developer...</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Summary:</FONT>
<BR> <FONT SIZE=3D2>PyOpenGL =
(the Python binding to the OpenGL graphics library) is in need </FONT>
<BR><FONT SIZE=3D2>of a C developer (preferably with SWIG experience) =
to work on </FONT>
<BR><FONT SIZE=3D2>maintaining and extending the package. Need is =
both short-term and </FONT>
<BR><FONT SIZE=3D2>long-term; we could use an immediate helping hand, =
but we're also </FONT>
<BR><FONT SIZE=3D2>looking for someone interested in long term =
work.</FONT>
</P>
<P> <FONT SIZE=3D2>PyOpenGL =
is a fairly large project (source-size), which is used by a </FONT>
<BR><FONT SIZE=3D2>considerable number of people (latest version has =
been downloaded </FONT>
<BR><FONT SIZE=3D2>something like 16,000 times). Developers =
looking to take on a popular </FONT>
<BR><FONT SIZE=3D2>project and make a name for themselves would find =
this a good opportunity.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Current Tasks:</FONT>
<BR> <FONT SIZE=3D2>PyOpenGL =
is currently generated using an old version of the SWIG wrapper </FONT>
<BR><FONT SIZE=3D2>generator (originally chosen because of missing =
features in other </FONT>
<BR><FONT SIZE=3D2>versions of SWIG with the idea that the missing =
features would </FONT>
<BR><FONT SIZE=3D2>eventually be adopted in newer SWIG versions (status =
of this unknown, </FONT>
<BR><FONT SIZE=3D2>but some work is definitely required to use the =
newer versions)). This </FONT>
<BR><FONT SIZE=3D2>build process tends to create lots of problems for =
those porting to new </FONT>
<BR><FONT SIZE=3D2>architectures, and we'd like to move off the (old, =
beta) version soon. </FONT>
<BR><FONT SIZE=3D2>This is a fairly extensive project, and will require =
familiarising </FONT>
<BR><FONT SIZE=3D2>yourself with the code base before making the =
attempt.</FONT>
</P>
<P> <FONT SIZE=3D2>We have a =
number of cross-platform build issues that need to be </FONT>
<BR><FONT SIZE=3D2>coordinated and integrated. In one case, we =
have already-submitted </FONT>
<BR><FONT SIZE=3D2>patches/fixes for fixing bug(s), in others, there =
are patches not yet </FONT>
<BR><FONT SIZE=3D2>submitted, but available. We need these =
integrated and tested. </FONT>
<BR><FONT SIZE=3D2>Integration is the developer requirement, we can get =
users with the </FONT>
<BR><FONT SIZE=3D2>exotic architectures to test the fixed =
versions.</FONT>
</P>
<P> <FONT SIZE=3D2>We have =
reports of complete meltdown under OpenGL 1.3 implementations </FONT>
<BR><FONT SIZE=3D2>under Linux. This is likely a trivial build or =
configuration problem, </FONT>
<BR><FONT SIZE=3D2>but it needs to be tracked down.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Future Tasks:</FONT>
<BR> <FONT =
SIZE=3D2>Maintenance of the package.</FONT>
</P>
<P> <FONT SIZE=3D2>Creation =
of new wrappers for common OpenGL modules (optional).</FONT>
</P>
<P> <FONT =
SIZE=3D2>Simplification of the build system for exotic =
architectures.</FONT>
</P>
<P> <FONT SIZE=3D2>Insert =
your PyOpenGL dreams here.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>Resources:</FONT>
<BR> <FONT SIZE=3D2>The =
project has 3 administrators, myself (a designer with minimal (read =
</FONT>
<BR><FONT SIZE=3D2>non-existent) C coding skills), Tarn (author of the =
current code </FONT>
<BR><FONT SIZE=3D2>(current missing in action)) and Rene (who is/was =
primarily interested </FONT>
<BR><FONT SIZE=3D2>in the building and porting work). I work =
primarily on the </FONT>
<BR><FONT SIZE=3D2>OpenGLContext side (which provides a series of tests =
for the base </FONT>
<BR><FONT SIZE=3D2>implementation, and tends to uncover errors as I =
develop it). I tend to </FONT>
<BR><FONT SIZE=3D2>do the work on the web-site, and general answering =
of questions when I can.</FONT>
</P>
<P> <FONT SIZE=3D2>At the =
moment, we have no active C developers, and just myself working on =
</FONT>
<BR><FONT SIZE=3D2>the administrative front. The PyOpenGL work =
I'm doing is minimal due to </FONT>
<BR><FONT SIZE=3D2>other projects and the fact that I'm largely =
unqualified for the work </FONT>
<BR><FONT SIZE=3D2>that needs to be done. I am working on a way =
to use fonttools for </FONT>
<BR><FONT SIZE=3D2>rendering 3D text in PyOpenGL+OpenGLContext, but =
that's not going to </FONT>
<BR><FONT SIZE=3D2>help with the general coding that needs to get =
done.</FONT>
</P>
<BR>
<P><FONT SIZE=3D2>How to Get Involved:</FONT>
<BR> <FONT SIZE=3D2>If you'd =
be interested in working as a developer, let me know and I'll </FONT>
<BR><FONT SIZE=3D2>see about adding you to the developer list. People =
familiar with the </FONT>
<BR><FONT SIZE=3D2>PyOpenGL codebase and project would be especially =
welcome.</FONT>
</P>
<P> <FONT SIZE=3D2><A =
HREF=3D"http://pyopengl.sourceforge.net/" =
TARGET=3D"_blank">http://pyopengl.sourceforge.net/</A></FONT>
</P>
<P><FONT SIZE=3D2>With thanks,</FONT>
<BR><FONT SIZE=3D2>Mike Fletcher</FONT>
</P>
<P><FONT SIZE=3D2>_______________________________________</FONT>
<BR><FONT SIZE=3D2> Mike C. Fletcher</FONT>
<BR><FONT SIZE=3D2> <A =
HREF=3D"http://members.rogers.com/mcfletch/" =
TARGET=3D"_blank">http://members.rogers.com/mcfletch/</A></FONT>
</P>
<BR>
<BR>
<BR>
<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://mail.python.org/mailman/listinfo/python-list" =
TARGET=3D"_blank">http://mail.python.org/mailman/listinfo/python-list</A=
></FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C21BD2.7466C710--