Need a glfxGetPrograms function.

[GoogleCodeExporter]

I desperately need to be able to retrieve a list of all programs within an 
effect. I would really love to join your development team to help implement 
these features.

Original issue reported on code.google.com by ad...@ovgl.org on 2 Jan 2013 at 10:54

[GoogleCodeExporter]

I'll add it to the next release as well.
These two features are simple enough and won't take too much of my time, but if 
you have bigger ideas for which I really don't have that much time (like making 
a re-entrant parser), then I'll be happy to hear them and add you to the 
project.

Original comment by max.snif...@gmail.com on 2 Jan 2013 at 11:20

[GoogleCodeExporter]

I actually have quite a few ideas. Maybe using subroutines to optimize 
performance. There are a lot missing functions that need to be implemented. The 
makefile does not install headers. I would like to add a cmakelists.txt file. 
The documentation is non existent. Would be nice if it compiled with standard 
C. There are also a lot of things about the way glfx is structured that are 
less than appealing such as using a FILE object to store and parse the shader 
source code. Also no offense but the logo looks awful. lol

These are just a few things off the top of my head. I would really like to see 
glfx become the de facto standard GLSL effect library. It would make OpenGL 
much more user friendly. I was going to write my own library to handle effects 
like this because it's an important part of the game library I'm working on but 
it just makes a lot more sense to improve glfx then to start from scratch. So I 
would really really like to help you as glfx is a crucial building block to my 
own work. However, at the moment it is no where near complete enough for me to 
actually use.

Original comment by ad...@ovgl.org on 2 Jan 2013 at 12:02

[GoogleCodeExporter]

Let's go one by one.

1. All Linux related stuff is on Etay. I never even looked at it. But I 
understand your point, and I'll ask him about the status on that. Either way, 
he'll probably be busy (just as me) doing other stuff, so bringing the Linux 
build into shape might be a good place to start.
2. Documentation is in the downloads section. If you think that there are 
important things missing in it, then by all means let me know.
3. No offense taken for the logo :) It's just something simple that Etay came 
up with long ago. Better logos are welcome.
4. I don't think that there's something seriously wrong with the FILE 
structure. Moreover, it's flex's native environment. Don't get me wrong, 
parsing from memory is probably better (and not that hard with flex), it's just 
not as pressing. First it would be much more important to do a re-entrant 
parser.

I'll add you to the project. See what you can do.

Original comment by max.snif...@gmail.com on 2 Jan 2013 at 1:03

[GoogleCodeExporter]

Do I need to inform you or ETay before making a commit?

Original comment by ad...@ovgl.org on 2 Jan 2013 at 1:45

[GoogleCodeExporter]

No need. I'll add you to the mailing list.

Original comment by max.snif...@gmail.com on 2 Jan 2013 at 3:58

[GoogleCodeExporter]

Original comment by ad...@ovgl.org on 4 Jan 2013 at 10:53

• Changed state: Fixed