April 2009 - HOpenGL - Haskell.org

Fwd: [Haskell] ANNOUNCE: GLUT 2.1.2.0
by Sven Panne 30 Apr '09

30 Apr '09

[ Forgot to CC: to the hopengl mailing list... ] ---------- Weitergeleitete Nachricht ---------- Betreff: [Haskell] ANNOUNCE: GLUT 2.1.2.0 Datum: Dienstag, 28. April 2009 Von: Sven Panne <Sven.Panne(a)aedion.de> An: Haskell Mailing List <haskell(a)haskell.org> A new version of the GLUT package has been uploaded to Hackage. This is a feature release, adding all the shiny new features of the upcoming freeglut 2.6.0 C library plus a few older bits and pieces which had been missing: * Minor tweaks for recent Cabal versions * Removal of old GHC build system relics. * Added support for OpenGL 3.x context creation (freeglut only) * Added support for getModeValues (freeglut extension) * Added freeglut-specific full screen API * Added freeglut-specific (de-)initialization API * Added support for multisampling with given samples per pixel (freeglut) * Added support for mouse wheel callback (freeglut) * Added support for window state callback (freeglut) * Added support for captionless/borderless windows (freeglut 2.6.0) * Handle special keys introduced by freeglut 2.6.0 The most important addition is the ability to create versioned context, so you can use forward compatible OpenGL 3.1 contexts. Death to the fixed function pipeline!! ;-) Cheers, S.

1 0

Fwd: [Haskell] ANNOUNCE: OpenGL 2.2.2.0
by Sven Panne 30 Apr '09

30 Apr '09

[ Forgot to CC: to the hopengl mailing list... ] ---------- Weitergeleitete Nachricht ---------- Betreff: [Haskell] ANNOUNCE: OpenGL 2.2.2.0 Datum: Dienstag, 28. April 2009 Von: Sven Panne <Sven.Panne(a)aedion.de> An: Haskell Mailing List <haskell(a)haskell.org> A new version of the OpenGL package has bee uploaded to Hackage. This is mainly a bug fix release, containing the following changes: * Minor tweaks for recent Cabal versions. * Removal of old GHC build system relics. * Handle "invalid framebuffer operation" error. * Terminate GLSL attribute names with NUL in various functions. * Access 3D texture functions via their core API names, improving portability (e.g. for MacOS X). * Added a workaround for a bug in the SGI tessellator. * Fixed marshalling of control points for evaluators. * Added mapBuffer/unmapBuffer and beginQuery/endQuery to exported API. Cheers, S.

1 0

GL.BufferObjects patch request (1-liner)
by Neal Alexander 30 Apr '09

30 Apr '09

I think withMappedBuffer does not cover all the use cases of mapped PBO - please add mapBuffer, unmapBuffer to the list of module exports. They come in handy when trying to do concurrent/async texture streaming.

4 5

Re: Opengl Patch
by Sven Panne 29 Apr '09

29 Apr '09

Am Freitag, 24. April 2009 13:53:16 schrieb Hugo Gomes: > Hey, > i stumbled upon this patch in the internets: > http://code.haskell.org/~bkomuves/ > Why isn't it applyed to the Opengl package ? Basically because I wasn't aware of those patches... ;-) I'm currently having a look at them, initially at the bug fixes only. I was planning to add support for generic vertex attribute arrays and frame buffer objects anyway, because they are part of the OpenGL 3.1 core. The API for those parts will probably be similar to the one in the patches, but it has to fit into the "3.1 picture", so I'll have to think about it a bit. Thanks for pointing me to those patches, Cheers, S.

2 1

Re: [HOpenGL] GLU.Tessellator crashes
by Sven Panne 26 Apr '09

26 Apr '09

[ redirecting to the HOpenGL list ] Am Sonntag, 26. April 2009 15:53:31 schrieb Balazs Komuves: > I see that you are again working on the OpenGL binding, so I would like > to advocate the patches I wrote during the last year, which can be found > here: http://code.haskell.org/~bkomuves/hopengl_2009-03-13.patch I am just wading through my email backlog, and found a mail pointing me to those patches. Thanks for you work! > In particular, there is a bugfix in Shaders.hs I would like to see > committed, > and some additional features (for example framebuffer objects) to be at > least considered. The bug fixes should be in the main repository quite fast (or are already there), the API additions need some thought, but they hopefully won't take long, either. Generic vertex attribute arrays and FBOs are important nowadays. > Also, we were talking about having a separate branch of the OpenGL > library to allow fast and easy access to bugfixes and more experimental > features, with the long-term goal of eventually merging them with the > main branch. What's your opinion about this? It would be especially useful > if you decide not to put the FBO / Vertex-Attributes-in-Vertex-Arrays into > the main branch now. Branching has always a high organizational cost associated with it, and I currently don't see a need to do this for the features you mention. I definitely *will* branch the OpenGL package into a "legacy" version (i.e. the current pre-OpenGL-3.x version) and a shiny new OpenGL 3.1 version, which will not be backwards compatible (deprecated stuff removed). But before I'll do this, I'll have to figure out the right way to do this, as there are quite a few things to consider (relationship to the Haskell platform releases, repository locations, bug tracker, etc.). Cheers, S.

1 1

Re: [HOpenGL] Newbie: Difference between $= and <- operators?
by Jeff Heard 26 Apr '09

26 Apr '09

the $= only works for OpenGL state variables, whereas <- won't work for them. The difference is that $= is implemented by every member of the SettableStateVar class differently, so that there may be extra functionality going on under the hood. The <- operator on the other hand always has the same meaning (relatively speaking -- it's possible to override this), in that it is a substitude for a <- someAction is the same as someAction >>= \a -> {- the rest of the do expression -} -- Jeff 2009/3/20 Mark Spezzano <mark.spezzano(a)chariot.net.au>: > Hi, > > > > What is the difference between the $= operator and the <- operator > > > > Both seem to read “assign to” but surely there is a difference. > > > > What should I use when? > > > > I want to create an animation that reads some coordinate (state-ful) data. > > > > Should I use $= or <- ? > > > > Cheers, > > > > Mark Spezzano > > > > No virus found in this outgoing message. > Checked by AVG. > Version: 7.5.557 / Virus Database: 270.11.20/2012 - Release Date: 19/03/2009 > 12:26 PM > > _______________________________________________ > HOpenGL mailing list > HOpenGL(a)haskell.org > http://www.haskell.org/mailman/listinfo/hopengl > >

2 1

GLU.Tessellator crashes
by Jules Bean 26 Apr '09

26 Apr '09

Hi, I've just written some code which uses 'tessellate' from Graphics.Rendering.OpenGL.GLU.Tessellation and whilst it works exactly as expected on simple data sets, it gives a bus error on larger ones (not that large - e.g. 150 points). This might be a bug in my OS's glu implementation, but I'm also inclined to suspect a bug in all the peeks and pokes HOpenGL uses to handle the data for the callbacks. I don't actually use the callback data (I've set all the data to (0 :: Int) only because there is no storable instance for ()). Does anyone have a success story with this function? Has anyone used it successfully on larger polygons? Jules

3 7