<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to feature-requests</title><link>https://sourceforge.net/p/pogl/feature-requests/</link><description>Recent changes to feature-requests</description><atom:link href="https://sourceforge.net/p/pogl/feature-requests/feed.rss" rel="self"/><language>en</language><lastBuildDate>Sun, 11 May 2025 19:54:44 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/pogl/feature-requests/feed.rss" rel="self" type="application/rss+xml"/><item><title>#3 Add support for ARB_draw_instanced and ARB_instanced_arrays</title><link>https://sourceforge.net/p/pogl/feature-requests/3/?limit=25#75c9</link><description>&lt;div class="markdown_content"&gt;&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;: open --&amp;gt; closed&lt;/li&gt;
&lt;/ul&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">mohawk</dc:creator><pubDate>Sun, 11 May 2025 19:54:44 -0000</pubDate><guid>https://sourceforge.netb8c0d2df56603725ea2e9968ea186a60260b4bb8</guid></item><item><title>#2 OpenGL ES support</title><link>https://sourceforge.net/p/pogl/feature-requests/2/?limit=25#fea7</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;There's a &lt;a class="" href="https://sourceforge.net/p/glew/mailman/glew-coders/thread/4C6972AA.3090603@nvidia.com"&gt;discussion with patches about glew and gles integration&lt;/a&gt;. Unfortunately, the conlusion of this thread is not really in favor of gles integration: &lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;I'd be a bit concerned on mobile platforms that the full desktop GLEW would be trying to load all kinds of irrelevant desktop extensions for OpenGL ES, and resulting in a much larger footprint than necessary.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;And there's no mention of gles in &lt;a class="" href="http://glew.sourceforge.net/log.html"&gt;glew changelog&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;I'm beginning to wonder if supporting gles as part of pogl is the right solution. May be a new set of bindings would be better...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ddumont</dc:creator><pubDate>Tue, 11 Nov 2014 19:01:53 -0000</pubDate><guid>https://sourceforge.net5a4a91df0b9d6c3b81265a08c435471b84ec30e7</guid></item><item><title>#2 OpenGL ES support</title><link>https://sourceforge.net/p/pogl/feature-requests/2/?limit=25#1b20/dc14</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;The current POGL bindings are hand generated XS wrappers that cover OpenGL functionality up to OpenGL 2.x-ish.  This has the problem that they are determined at build time and not at run time so there is a possible issue of functionality that might be available (or not) at build time but differs at run time.&lt;/p&gt;
&lt;p&gt;The planned solution is to use the GLEW library to generated the POGL bindings that would be able to be determined at run time.  This gives dynamic bindings and full support for all  features and extensions up through OpenGL 4.x.&lt;/p&gt;
&lt;p&gt;I'm not familiar enough with the modern OpenGL vs OpenGL ES stuff to understand how this would need to change for the use of OpenGL ES rather than OpenGL.  Maybe a similar strategy to the GLEW one could be used there.&lt;/p&gt;
&lt;p&gt;Regarding GLUT, that was added in an attempt to move POGL from the original X11 base implementation to one that is portable across platforms.  While it did achieve that goal, it also added a false requirement on FreeGLUT to perl modules using OpenGL.&lt;/p&gt;
&lt;p&gt;The plan for the POGL update is to spin off the user interface/context generation part into separate modules with a generic plugin type approach.  That would allow one to use any of a number of options for platform interfaces: X11, GLUT, GLFW, Qt, wxWidgets, or any other library that can provide the needed graphic context.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Marshall</dc:creator><pubDate>Tue, 11 Nov 2014 15:45:30 -0000</pubDate><guid>https://sourceforge.net65fae1e30e8862585c6679d3fac013f1654b1cc5</guid></item><item><title>#2 OpenGL ES support</title><link>https://sourceforge.net/p/pogl/feature-requests/2/?limit=25#1b20</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hmm, I think that GLES is already a subset of existing OpenGL API. (See &lt;a href="http://en.wikipedia.org/wiki/OpenGL_ES" rel="nofollow"&gt;http://en.wikipedia.org/wiki/OpenGL_ES&lt;/a&gt; and &lt;a href="http://web.eecs.umich.edu/~sugih/courses/eecs487/common/notes/APITables.xml" rel="nofollow"&gt;http://web.eecs.umich.edu/~sugih/courses/eecs487/common/notes/APITables.xml&lt;/a&gt; )&lt;/p&gt;
&lt;p&gt;On linux, gles is provided by libGLESv2.so.2 . POGL is not linked to that library. &lt;/p&gt;
&lt;p&gt;I think (well, I hope), that supporting GLES would require:&lt;br /&gt;
- be able to link POGL to libGLESv2.so instead of libglut.so&lt;br /&gt;
- be able to #ifdef out all OpenGL only function definitions in XS files&lt;/p&gt;
&lt;p&gt;Of course, I may be completely wrong...&lt;/p&gt;
&lt;p&gt;What do you think ?&lt;/p&gt;
&lt;p&gt;All the best&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">ddumont</dc:creator><pubDate>Tue, 11 Nov 2014 11:23:41 -0000</pubDate><guid>https://sourceforge.net85f6cb71c4e38c5fdaf8c29a61b7722d12e2c05e</guid></item><item><title>#3 Add support for ARB_draw_instanced and ARB_instanced_arrays</title><link>https://sourceforge.net/p/pogl/feature-requests/3/?limit=25#242c</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Actually MESA had them in 7.11 already. Intel support came later.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">orafu</dc:creator><pubDate>Mon, 02 Dec 2013 17:29:07 -0000</pubDate><guid>https://sourceforge.net284496bcfe15d84ff31ac4eb47f27e4a3a90471f</guid></item><item><title>Add support for ARB_draw_instanced and ARB_instanced_arrays</title><link>https://sourceforge.net/p/pogl/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Hello,&lt;/p&gt;
&lt;p&gt;the title summarizes it.&lt;/p&gt;
&lt;p&gt;For the visualization of algorithms, particle systems or molecules, often many objects of the same shape need to be drawn.&lt;/p&gt;
&lt;p&gt;The extensions for instanced drawing apparently push OpenGLs ability to draw many objects of the same shape. &lt;a class="" href="http://sol.gfxile.net/instancing.html" rel="nofollow"&gt;One test&lt;/a&gt; measured a speedup of a factor 2 to 18 on two 2009-vintage video cards from Nvidia and AMD, depending on instance polygon count and the polygon caching capacity of the hardware. The test indicates that the speedup may even improve on newer hardware.&lt;/p&gt;
&lt;p&gt;I expect that POGL will get even greater performance benefits, because rendering the same object many times without these extensions requires many API calls, and as POGL is an additional layer on top of the OpenGL API it has additional overhead for API calls.&lt;/p&gt;
&lt;p&gt;It looks like an implementation needs to support only 2 - 3 additional functions: ARB_draw_instanced adds DrawArraysInstancedARB() and DrawElementsInstancedARB() and ARB_instanced_arrays adds VertexAttribDivisorARB(). (ARB_instanced_arrays is not strictly needed, but it means that the vertex shader code becomes much simpler as vertex attribute arrays can be used to transmit per-instance data, rather than textures (or uniforms, which also kill performance benefits).)&lt;/p&gt;
&lt;p&gt;In my eyes the most important missing feature for visualization.&lt;/p&gt;
&lt;p&gt;Note that even Intel HD Graphics since SandyBridge support these extensions. MESA had them since version 9.0, including support in the Intel driver.&lt;/p&gt;
&lt;p&gt;Best regards&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">orafu</dc:creator><pubDate>Mon, 02 Dec 2013 17:11:32 -0000</pubDate><guid>https://sourceforge.neted7a15fdb5a3038a43c6a18ea6e3605c8d00fc2d</guid></item><item><title>Add support for ARB_draw_instanced and ARB_instanced_arrays</title><link>https://sourceforge.net/p/pogl/feature-requests/3/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Ticket 3 has been modified: Add support for ARB_draw_instanced and ARB_instanced_arrays&lt;br/&gt;
Edited By: mohawk (mohawk111)&lt;br/&gt;
Status updated: 'open' =&amp;gt; 'closed'&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">orafu</dc:creator><pubDate>Mon, 02 Dec 2013 17:11:32 -0000</pubDate><guid>https://sourceforge.net70014e44af501082d29a9cd54dec2681fc56061d</guid></item><item><title>OpenGL ES support</title><link>https://sourceforge.net/p/pogl/feature-requests/2/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Howdy all!&lt;/p&gt;
&lt;p&gt;I think the title of the feature request says it all : D I know next to nothing about OpenGL in general, and I imagine that this request might be tough as nails, since there's no GLUT on embedded systems, but I'm more than willing to learn the codebase and try doing some of the footwork myself if you folk think that GLES support is possible.&lt;/p&gt;
&lt;p&gt;As for why, GLES support is essential for running things on the raspberry pi, or, more importantly to me, creating no-java-just-perl android apps.&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Brian Fraser</dc:creator><pubDate>Thu, 22 Aug 2013 02:40:22 -0000</pubDate><guid>https://sourceforge.net1258e3c383355fdf5250ecf9ecf6bf9c6a05294e</guid></item><item><title>add ability to specify OpenGL compile/link options</title><link>https://sourceforge.net/p/pogl/feature-requests/1/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Transferred from bug #52350 for OpenGL: OpenGL fails to compile...&lt;br /&gt;
&amp;gt; ...&lt;br /&gt;
&amp;gt; The point is, I can have both 32-bit and 64-bit libraries as well as&lt;br /&gt;
&amp;gt; both 32-bit and 64-bit perls _and_ no clues about correct library paths&lt;br /&gt;
&amp;gt; in Config. Or, as I discovered another day, I can have broken Mesa in&lt;br /&gt;
&amp;gt; /usr/lib for backwards compatibility and working libGL in /usr/X11/lib&lt;br /&gt;
&amp;gt; so that I have to do some clever dance with LD_RUN_PATH.&lt;br /&gt;
&amp;gt; &lt;br /&gt;
&amp;gt; So, letting one specify the correct -I, -L and LD_RUN_PATH through the&lt;br /&gt;
&amp;gt; environment could be the best solution for automatic testing (as a&lt;br /&gt;
&amp;gt; bonus, you may harvest the configuration data from tester reports).&lt;/p&gt;
&lt;p&gt;This would allow the OpenGL module to build whenever the&lt;br /&gt;
user can specify the neede compile, link, and load options.&lt;br /&gt;
This is particularly important when there are more than one&lt;br /&gt;
set of applicable libraries on a system:  32bit, 64bit, wgl,&lt;br /&gt;
glx, agl...&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Marshall</dc:creator><pubDate>Tue, 12 Jul 2011 17:42:08 -0000</pubDate><guid>https://sourceforge.netd23d0115c14416cac69ff76ba157f1be5fab221f</guid></item></channel></rss>