pyopengl-users — Discussion of all PyOpenGL matters.

Re: [PyOpenGL-Users] can't import

[<il...@ya...>]

Hello.

These are the import lines which I use.

from OpenGL.GL import *
from OpenGL.GLUT import *
from OpenGL.GLU import *


Have fun!

 --- Strato <fl...@id...> wrote: > hi,
> I'm trying to write an easily portable train
> simulation game for linux,
> windows, mac os x and so on. Because my 3d graphics
> adapter isn't well
> supported under linux (only the 3d part) I decided
> to do the main developing
> under windows. I fetched the pyopengl-2.0.exe from
> sourceforge and installed
> it.
> But when I now type "import PyOpenGL"
> I get an error message "couldn't load"
> "no module named PyOpenGL"
> What did  I do wrong?
> thanks in advance
> Florian Idelberger
> 
> 
> 

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

Re: [PyOpenGL-Users] can't import

[Jack J. <Jac...@or...>]

On maandag, september 16, 2002, at 10:34 , Strato wrote:

> hi,
> I'm trying to write an easily portable train simulation game for linux,
> windows, mac os x and so on. Because my 3d graphics adapter isn't well
> supported under linux (only the 3d part) I decided to do the 
> main developing
> under windows. I fetched the pyopengl-2.0.exe from sourceforge 
> and installed
> it.
> But when I now type "import PyOpenGL"
> I get an error message "couldn't load"
> "no module named PyOpenGL"
> What did  I do wrong?

It probably got installed in the wrong location. Run "python 
-vv" (which is very verbose, it not only prints where it 
imported modules from, but also where it looked but couldn't 
find the module) and do "import PyOpenGL" at the >>> prompt.
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- 
Emma Goldman -

[PyOpenGL-Users] can't import

[Strato <fl...@id...>]

hi,
I'm trying to write an easily portable train simulation game for linux,
windows, mac os x and so on. Because my 3d graphics adapter isn't well
supported under linux (only the 3d part) I decided to do the main developing
under windows. I fetched the pyopengl-2.0.exe from sourceforge and installed
it.
But when I now type "import PyOpenGL"
I get an error message "couldn't load"
"no module named PyOpenGL"
What did  I do wrong?
thanks in advance
Florian Idelberger

[PyOpenGL-Users] [ pyopengl-Feature Requests-452946 ] Font modules

[<no...@so...>]

Feature Requests item #452946, was opened at 2001-08-19 11:00
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355988&aid=452946&group_id=5988

Category: new module
Group: v2.1
Status: Open
Resolution: None
Priority: 3
Submitted By: Tarn Weisner Burton (twburton)
Assigned to: Tarn Weisner Burton (twburton)
Summary: Font modules

Initial Comment:
Create font modules.  Targets: bitmap + outline.  It 
would be nice if out lines could be sent to GLE

methods:

1) wrap GLTT (see http://gltt.sf.net) -> under GPL!  
Also doesn't interface with GLE
2) Use PyFT to create own variant of GLTT.  Problem 
with this is that PyFT is under GPL, even though 
Freetype can be used with either BSD/GPL.  Also PyFT 
is Freetype1 not Freetype2.
3) Wrap Freetype2 and write own python code.
4) write own C version of GLTT that uses Freetype.
5) Use python FontTools? (No rasterizer)
6) expose platform specific bitmap font capabilities 
through WGL, AGL, GLX, etc.  or come up with common 
call.

----------------------------------------------------------------------

>Comment By: Mike C. Fletcher (mcfletch)
Date: 2002-06-27 19:35

Message:
Logged In: YES 
user_id=34901

Python fonttools project does a nice job of giving you the
shells for the code, I'm playing around with making a
run-time renderer with it.  As noted, no rasteriser,
however, so have to roll both geometry and raster-mode
implementations.

----------------------------------------------------------------------

Comment By: Mike C. Fletcher (mcfletch)
Date: 2002-01-17 04:25

Message:
Logged In: YES 
user_id=34901

Another possible option:
http://oglft.sourceforge.net/ -- LGPL, (apparently) same
basic functionality as GLTT, based on FreeType2.  Claims to
be 0.0 status, but has what looks to be fairly close to a
completed OGLFT.CPP (haven't tested it's functionality, just
browsed the code).  Note that it's C++, not C, code.  By the
look of it, could be its own module, rather than being part
of the base PyOpenGL module (especially given the license),
as it's interactions are all self-contained (you pass in
strings, booleans, etceteras, there's no arrays/callbacks).
 Has all the bells+whistles you'd want (multiple 2D and 3D
formats, extrusions with GLE, use of truetype, etceteras).

----------------------------------------------------------------------

Comment By: Mike C. Fletcher (mcfletch)
Date: 2002-01-17 04:02

Message:
Logged In: YES 
user_id=34901

Another possible option:
http://oglft.sourceforge.net/ -- LGPL, (apparently) same
basic functionality as GLTT, based on FreeType2.  Claims to
be 0.0 status, but has what looks to be fairly close to a
completed OGLFT.CPP (haven't tested it's functionality, just
browsed the code).  Note that it's C++, not C, code.  By the
look of it, could be its own module, rather than being part
of the base PyOpenGL module (especially given the license),
as it's interactions are all self-contained (you pass in
strings, booleans, etceteras, there's no arrays/callbacks).
 Has all the bells+whistles you'd want (multiple 2D and 3D
formats, extrusions with GLE, use of truetype, etceteras).

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355988&aid=452946&group_id=5988

[PyOpenGL-Users] [ pyopengl-Feature Requests-574464 ] Testing framework

[<no...@so...>]

Feature Requests item #574464, was opened at 2002-06-27 02:48
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355988&aid=574464&group_id=5988

Category: new module-OpenGLContext
Group: OpenGLContext v1.0
Status: Open
Resolution: None
Priority: 5
Submitted By: Mike C. Fletcher (mcfletch)
Assigned to: Mike C. Fletcher (mcfletch)
Summary: Testing framework

Initial Comment:
Need to work on creating an automated testing framework
for PyOpenGL.  This should allow for testing the
various context modes with test code snippets and
possibly comparing results with expected-results
bitmaps (taking into consideration that OpenGL doesn't
guarantee pixel-perfect reproduction AFAIK).

At the least the code should be able to run every
method in the library just to see if they blow up.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=355988&aid=574464&group_id=5988

[PyOpenGL-Users] RE: [PyOpenGL] Need for a C (lead) developer...

[twburton <twb...@fo...>]

Although I am not currently able to actively work on PyOpenGL because of my
graduate work, I can help out the new lead developer if he runs into any
bumps, hurdles or fubar code sections.

Tarn

Re: [PyOpenGL-Users] [PyOpenGL] Need for a C (lead) developer...

[<il...@ya...>]

Hello Mike.

I'd like to help out.  I don't think I'm the rene you
were talking about?

I've allready got some fixes for a few things I'd like
to apply to cvs (gl*Pointer memory leak fixes, and
some  fixes to glGetInteger ).  These would be better
fixed after/during the update to the new swig though.


I'm familiar with swig, and was considering updating
the code to the new version of swig just the other
day.  I've looked through the pyopengl code base a
fair bit.

I use pyopengl a lot, and might be using it more at
work soon.  So I'd probably be doing some of the stuff
you'd mention anyway if no one does it.

One other thing which I think needs to be done is port
all of the nehe tutorials to python. 


I'm on irc as well if you like talking there. as
illume, on #opengl openprojects.  I've got the week
off work, so I'll be monitoring the channel fairly
reguarly.


Looking forward to hearing from you.

__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com

[PyOpenGL-Users] [PyOpenGL] Need for a C (lead) developer...

[Mike C. F. <mcf...@ro...>]

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/

[PyOpenGL-Users] PyOpenGL samples

[philippe G. <pgu...@ap...>]

Hello,

I have writed some programs using PyOpenGL, GtkGLArea, ...

I have ported this programs from some tutorials in C.

They are here:

http://guillaumaud.dyndns.org/cgi-bin/viewcvs.cgi/python/

regards

--=20
"Toute r=E9ponse constitue une prise dangereuse sur l'univers.
 Malgr=E9 une apparence sens=E9e, elle n'explique peut-=EAtre rien"
Le Fouet Zensunni

http://doubleclic89.eu.org
http://idll.tuxfamily.org

[PyOpenGL-Users] 3D textures

[Antti K. <ant...@he...>]

Hi!
I'm interested in 3D texture support in PyOpenGL. Are they supported in CVS 
version? What is the plan/schedule for them?

thanks,

Antti Korvenoja

Re: [PyOpenGL-Users] Exiting immidialty on errors

[Carlos M. <dud...@ya...>]

--- David <mp...@ch...> wrote:

> So how can i make python halt immidiatly when there
> has been an error in 
> any of the callbacks?

import sys
...
try:
	<python code>
except ExceptionType:
	<python code - Exception handle>
	sys.exit()


	[]'s

Cadu Moreira
KaduSoft President
----------------------------
[...give me a beer...]

__________________________________________________
Do You Yahoo!?
Yahoo! - Official partner of 2002 FIFA World Cup
http://fifaworldcup.yahoo.com

[PyOpenGL-Users] Exiting immidialty on errors

[David <mp...@ch...>]

If an error occurs in the display function my python opengl demos python 
doesn't halt and give me an error, instead it gives me an error but 
calls the display function again and again and again.
If you have glPushMatrix():es in your code this means you will get a 
xterm full of "stack overflow" errors instead of the actual error that 
is causing the problem.

So how can i make python halt immidiatly when there has been an error in 
any of the callbacks?

[PyOpenGL-Users] Was able to fix glTexCoordPointer problem!

[Andy S. <an...@ne...>]

The fix outlined in
http://www.geocrawler.com/archives/3/4494/2002/3/0/8161591/
seems to work! Please post your experiences.

You need not go through the trouble I experienced
by following the tips below. These are for compiling
via distutils under Windows MSVC 6.

Tip #1. I used PyOpenGL-2.0.0.44-zip, the CVS
compile this afternoon seemed to finally
work, but there were warnings...

Tip #2. Use Swig1.3a5.zip - I had a hell of
a time trying to get other versions to work
until I saw the message recommending I use
that version.

Unzip to Swig1.3a5.zip to a directory of your
choice (should be in your path so distutils can
find it). Then "set SWIG_LIB=c:\the_new_swig_path\lib"

Tip #3. Fix togl_setup.py.
The Tcl lib and include entries seem to be wrong -
at least for ActivePython 2.2.1.

Change

include_dirs.append(os.path.join(tk.getvar('tk_library'), '..', '..',
'include'))

at line 45 to:

include_dirs.append(os.path.join(tk.getvar('tk_library'), '..', 'include'))

Note: Not sure if this will break builds under Linux or other Python
distributions. This corresponds to
changing -IC:\python22\tcl\tk8.3\..\..\include
to -IC:\python22\tcl\tk8.3\..\include

Add

lib_dirs.append(os.path.normpath(os.path.join(tk.getvar('tcl_library'),
'..', 'lib')))

after the

if sys.platform == 'win32':

at line 49.

Tip #3 applies to the CVS source as well.

Perhaps these fixes (if they are correct) could be included in
the next PyOpenGL 2.0.0.x.

Are there any plans to migrate the interfaces to work with
the latest Swig?

[PyOpenGL-Users] PyOpenGL and stereo

[Jack J. <Jac...@cw...>]

Is anyone using stereo with PyOpenGL? I've had absolutely no success 
with it, so far.

I started out with a rather complex program, where my PyOpenGL code was 
basically embedded in a large C-based OpenGL infrastructure (basically 
my Python code is only the redraw callback, all the double-buffer and 
left-right juggling and perspective matrices and such are handled for me 
in C).
This worked fine for the mono case, but when I ran the program in stereo 
I got to see the both viewpoints sort-of interspersed, with a lot of 
flickering and not in sync with the glasses.

I've slowly worked back, taking out bits and pieces of the system to 
narrow down the culprit, and I'm now at a minimal PyOpenGL GLUT-based 
program, which is basically the PyOpenGL GLE example with stereo turned 
on and the do_display() routine replaced by
	glDrawBuffer(GL_BACK_LEFT)
	glClearColor(0, 0, 1, 0)
	glClear(GL_COLOR_BUFFER_BIT)
	glDrawBuffer(GL_BACK_RIGHT)
	glClearColor(1, 0, 0, 0)
	glClear(GL_COLOR_BUFFER_BIT)
	# [see below]
	glutSwapBuffers()
and I see a blue background, nothing more. However, if I wiggle the 
mouse (which causes draw events, because the original GLE.py example 
code used that to rotate the tube) I see flashes of red.
To make matters more unintellegible, if I insert drawing code at the 
[see below] I do see what I draw here, but against the blue background! 
So, what I see is a non-stereo image consisting of the background color 
of the left buffer and the graphics in the right buffer??!?

None of these problems exist with C OpenGL code, so I tend towards 
blaming something PyOpenGL does for this.

What would be really helpful to me at this moment is a PyOpenGL script 
that is known to work, at least for someone on some machine, at some 
time:-)

This is all with PyOpenGL from the CVS HEAD (built with swig 1.3.9, 
later versions don't seem to work) with a few mods needed to make it 
compile (missing semicolons!). The machine is a dual 1.6GHz Pentium 
Linux box (2.4.9 kernel) with an ATI Rage XL graphics board.

Please reply to me directly (as well as possibly ccing to the list if 
it's deemed of general interest), I'm not on this list yet,
--
- Jack Jansen        <Jac...@or...>        
http://www.cwi.nl/~jack -
- If I can't dance I don't want to be part of your revolution -- Emma 
Goldman -

Re: [PyOpenGL-Users] Samples

[Richard J. <ric...@op...>]

On Thursday 09 May 2002 06:44 am, David wrote:
> Where can i find samples for using PyOpenGl? Preferably about using
> PyOpenGl with glut, but any samples would be greatly appriciated. I kno=
w
> GL, so that's not a problem.

Something I hacked on last December:

   http://mechanicalcat.net/tech/ufo/

This includes some optimisation work - try running with and without the C=
=20
extension modules.


   Richard

[PyOpenGL-Users] Samples

[David <mp...@ch...>]

Where can i find samples for using PyOpenGl? Preferably about using 
PyOpenGl with glut, but any samples would be greatly appriciated. I know 
GL, so that's not a problem.

Regards,
David

[PyOpenGL-Users] Re: More problems installing PyOpenGL on MacOSX

[Dave R. <dr...@ca...>]

> From: Peter Lundh <si...@te...>
> 
> Thank you very much to all of you for your advice. It seems that I got a bit
> further by installing the previous version of PyOpenGL - but I still got
> stuck:
> 
> > [localhost:~/desktop/pyopengl-1.5.7] peter% sudo python setup.py
> > usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
> >  or: setup.py --help [cmd1 cmd2 ...]
> >  or: setup.py --help-commands
> >  or: setup.py cmd --help
> > 
> > error: no commands supplied
> 
> Can anyone suggest what it is that I'm doing wrong.
> 
> Thanks
> 
> -Peter
> -- 
> Peter Lundh von Leithner
> Sweden
> E: si...@te...


If that's your command above, you need to supply an action for the
setup.py script:

The following is the common usage:

python setup.py build
(see if everything goes ok)
python setup.py install

HTH,
DAve

[PyOpenGL-Users] More problems installing PyOpenGL on MacOSX

[Peter L. <si...@te...>]

Thank you very much to all of you for your advice. It seems that I got a bit
further by installing the previous version of PyOpenGL - but I still got
stuck:

> [localhost:~/desktop/pyopengl-1.5.7] peter% sudo python setup.py
> usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
>  or: setup.py --help [cmd1 cmd2 ...]
>  or: setup.py --help-commands
>  or: setup.py cmd --help
> 
> error: no commands supplied

Can anyone suggest what it is that I'm doing wrong.

Thanks

-Peter
-- 
Peter Lundh von Leithner
Sweden
E: si...@te...

RE: [PyOpenGL-Users] Problems installing PyOpenGL on MacOSX

[twburton <twb...@fo...>]

2.0.0.44 doesn't work with Mac yet.  The ambitious may try CVS as it works
better, but still fails at some point.

Tarn

[PyOpenGL-Users] Problems installing PyOpenGL on MacOSX

[Peter L. <si...@te...>]

I have problems installing PyOpenGL on MacOSX.  I have installed Python with
Fink and have downloaded "PyOpenGL-2.0.0.44".

When I try to run the python setup.py command I get the following message:

> [laptop1:~/PyOpenGL-2.0.0.44] peter% python setup.py
> Traceback (most recent call last):
> File "setup.py", line 54, in ?
>   from setup import togl_setup
> File "setup/togl_setup.py", line 16, in ?
>   tk = Tkinter.Tk()
> File "/sw/lib/python2.2/lib-tk/Tkinter.py", line 1487, in __init__
>   self.tk = _tkinter.create(screenName, baseName, className)
> TclError: couldn't connect to display "localhost:0.0"
> [laptop1:~/PyOpenGL-2.0.0.44] peter%

What am I doing wrong?
-- 
Peter Lundh von Leithner
Sweden
E: si...@te...

RE: [PyOpenGL-Users] Solaris build problems

[twburton <twb...@fo...>]

The fix for GL_SUN_triangle_list is indeed in CVS, but in order to build out
of CVS you need SWIG 1.3.9

Tarn

[PyOpenGL-Users] Solaris build problems

[Meyer, A. <am...@ex...>]

Hi:
 
I'm trying to install PyOpenGL 2.0.0.44 on Solaris (sunos5) with gcc and
without swig. I hit and fixed the problem with GL.EXT.vertex_array.c
mentioned earlier, but can't compile GL.SUN.triangle_list.0106.inc. Error
messages follow:
 
src/interface/GL.SUN.triangle_list.0106.inc:731: parse error before `->'
src/interface/GL.SUN.triangle_list.0106.inc:732: parse error before `->'
src/interface/GL.SUN.triangle_list.0106.inc:733: parse error before `->'
src/interface/GL.SUN.triangle_list.0106.inc:734: parse error before `->'
src/interface/GL.SUN.triangle_list.0106.inc:735: parse error before `->'
src/interface/GL.SUN.triangle_list.0106.inc:736: parse error before `->'
 
Per an earlier suggestion I checked CVS for a new version of the file, but
it looks like the interface sources have been removed. Anybody know what a
fix for this is?
 
Andy Meyer

---------------------------------------------------------------------- 
Andrew Meyer 
Bldg 911A, Collider-Accelerator Dept. 
Brookhaven National Laboratory

 

[PyOpenGL-Users] Re: Test-first and mock objects with PyOpenGL

[Mike C. F. <mcf...@ro...>]

I've never done unit testing with OpenGL code, but I'll give a shot at 
the problem.

I'd guess the easiest test you could create would be to create an image 
that shows what you want and simply test whether that matches the image 
created by the new system.  Problem there is that the original image 
would need to be generated by your system, so you'd have that 
anti-pattern (don't recall what the XP name is) where you rely on output 
of the system to check correctness of the system.

If you really want to make the checks "manually predicted", you'd have 
to figure out particularly what calls, with what parameters you expected 
to get... all in all, sounds like a pain in the arse unless you're 
dropping in the "mockup" with the "known-good" system to generate a set 
of data... that's the same anti-pattern cropping up though.

 From a practical standpoint, replacing the whole GL with a mock-up 
seems a bit extreme (you'd have to figure out the internal state to do 
it right I'd think).  You could easily write a script that just walks 
through the Python OpenGL.GL, OpenGL.GLU and OpenGL.GLUT modules 
replacing every method with a wrapped version which logs the method 
name, parameters and return values to somewhere.  Check that log versus 
your expected results and you'd be golden (assuming you can create the 
set of "expected results" somehow).  Tarn did something very similar a 
while back to introduce stronger error checking without changing the C code.

Well, hope that helps somewhat, shout if anything I've said is unclear,
Mike

Phlip wrote:
> Alpha OpenGL Engineers:
> 
> I have a large spike-solution ("quicky non-production quality code
> base") of PyOpenGL, and I want to refactor it into something healthy.
> 
> I don't want to use GuruChecksOutput. This means I want tests that
> reveal changes did not affect how the code call the GL libraries.
> 
> The standard way to do this is to provide a MockObject in place of
> something, call the tested functions, let them call into the
> MockObject, and test what they told it. If these values did not change
> then the refactor did not break anything important.
> 
> However, I don't know if I have to Mock GL itself. Maybe I can replace
> OpenGL's back-end with a Mock that renders not to the screen but into
> my test code.
> 
> Who has done this and knows the pattern for it?
> 


-- 
_______________________________________
   Mike C. Fletcher
   http://members.rogers.com/mcfletch/

[PyOpenGL-Users] passing arrays

[Mathew Y. <ma...@fu...>]

Hi, I'm trying to use a GL function
which is wrapped so that one of the parameters
is passed to SWIG_ConvertPtr where it is supposed
to be converted to the type ,SWIGTYPE_p_q_const__GLvoid.

What do I do? How can I create this variable? I don't
see the function ptrcreate inside the module I'm importing.

Mathew

Re: [PyOpenGL-Users] opengl() title question

[Carlos M. <dud...@ya...>]

--- "Douglas S. Blank" <db...@br...> wrote:
> I have a basic question:
> 
> I'm using Opengl() function to create a window, and
> everything is 

Errata:

	OpenGL() doesn't create windows or callbacks.
OpenGL() only work on graphics, your toolkits (like
Glut, PyQT ---> is very cool ;), Tkinter, etc) manage
this features.

	[]'s

Cadu Moreira
KaduSoft President
----------------------------
[...Marx live...]


__________________________________________________
Do You Yahoo!?
Yahoo! Greetings - send holiday greetings for Easter, Passover
http://greetings.yahoo.com/