I am just looking at some of the GEMgl stuff, and noticed there are no helpfiles for any of them. It seems that it would be quite useful to make a help template for these functions, then generate them automatically, since the objects themselves were auto-generated. It would be very nice to have these help patches already generated from the OpenGL reference, and also included a link, perhaps.
I just committed GLdefine-help.pd as a start. Any thoughts on that?
.hc
----------------------------------------------------------------------------
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
The GEMgl objects really require a working knowledge of OpenGL, and it would be a bit much to redo much of the standard texts in the help patches. Just put a link to: http://www.glprogramming.com/blue/
That should cover most of the objects - even the ones that can't possibly work in Pd/GEM.
On Mon, Mar 23, 2009 at 6:20 PM, Hans-Christoph Steiner hans@eds.orgwrote:
I am just looking at some of the GEMgl stuff, and noticed there are no helpfiles for any of them. It seems that it would be quite useful to make a help template for these functions, then generate them automatically, since the objects themselves were auto-generated. It would be very nice to have these help patches already generated from the OpenGL reference, and also included a link, perhaps.
I just committed GLdefine-help.pd as a start. Any thoughts on that?
.hc
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
I think it would be pretty easy to scrap that page and stick the key text bits into the help page. Something like "NAME", "C SPECIFICATION", "PARAMETERS", and "DESCRIPTION". I imagine that this stuff doesn't change very often.
Ideally there would be working examples for each function, but that's a big project. What else should go on that help page?
.hc
On Mar 23, 2009, at 7:18 PM, chris clepper wrote:
The GEMgl objects really require a working knowledge of OpenGL, and it would be a bit much to redo much of the standard texts in the help patches. Just put a link to: http://www.glprogramming.com/blue/
That should cover most of the objects - even the ones that can't possibly work in Pd/GEM.
On Mon, Mar 23, 2009 at 6:20 PM, Hans-Christoph Steiner hans@eds.org wrote:
I am just looking at some of the GEMgl stuff, and noticed there are no helpfiles for any of them. It seems that it would be quite useful to make a help template for these functions, then generate them automatically, since the objects themselves were auto- generated. It would be very nice to have these help patches already generated from the OpenGL reference, and also included a link, perhaps.
I just committed GLdefine-help.pd as a start. Any thoughts on that?
.hc
As we enjoy great advantages from inventions of others, we should be glad of an opportunity to serve others by any invention of ours; and this we should do freely and generously. - Benjamin Franklin
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
----------------------------------------------------------------------------
Access to computers should be unlimited and total. - the hacker ethic
Hans-Christoph Steiner wrote:
I think it would be pretty easy to scrap that page and stick the key text bits into the help page. Something like "NAME", "C SPECIFICATION", "PARAMETERS", and "DESCRIPTION". I imagine that this stuff doesn't change very often.
Ideally there would be working examples for each function, but that's a big project. What else should go on that help page?
i think the only reasonable solution is to have a single helpfile for all the openGL-wrapper objects, that points to a "real" ressource, like the blue book; and probably
anything else will just eat diskspace for naught. i don't think you can teach openGL by providing "working examples for each function"; you cannot use the GEMgl... objects without having a proper knowledge of openGL.
mfg.adsr IOhannes
I think a general help patch about the GEMgl objects would be nice. there are some special things people should be aware of, for example that you have to add the f for float in many of the objects: like GEMglVertex3f. I also think a couple of example patches would be good to have, like how to bind textures or vertexbuffer objects. otoh I think very few people ever used GEMgl objects, maybe if people start using them then there will be automatically some help/example patches? marius.
IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
I think it would be pretty easy to scrap that page and stick the key text bits into the help page. Something like "NAME", "C SPECIFICATION", "PARAMETERS", and "DESCRIPTION". I imagine that this stuff doesn't change very often.
Ideally there would be working examples for each function, but that's a big project. What else should go on that help page?
i think the only reasonable solution is to have a single helpfile for all the openGL-wrapper objects, that points to a "real" ressource, like the blue book; and probably
anything else will just eat diskspace for naught. i don't think you can teach openGL by providing "working examples for each function"; you cannot use the GEMgl... objects without having a proper knowledge of openGL.
mfg.adsr IOhannes
GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
Every other Pd object has its own help patch, so I don't understand why these wouldn't also. I think that it would be pretty straightforward to auto-generate help patches based on the blue book, then as people get inspired, they could add examples. I attached a quick example.
I don't remember all the details of every function I ever use, so I look things up a lot. Pd has a very handy and quick way to bring up a reference page, why wouldn't we use it?
.hc
On Mar 24, 2009, at 4:28 PM, marius schebella wrote:
I think a general help patch about the GEMgl objects would be nice. there are some special things people should be aware of, for example that you have to add the f for float in many of the objects: like GEMglVertex3f. I also think a couple of example patches would be good to have, like how to bind textures or vertexbuffer objects. otoh I think very few people ever used GEMgl objects, maybe if people start using them then there will be automatically some help/example patches? marius.
IOhannes m zmölnig wrote:
Hans-Christoph Steiner wrote:
I think it would be pretty easy to scrap that page and stick the key text bits into the help page. Something like "NAME", "C SPECIFICATION", "PARAMETERS", and "DESCRIPTION". I imagine that this stuff doesn't change very often.
Ideally there would be working examples for each function, but that's a big project. What else should go on that help page?
i think the only reasonable solution is to have a single helpfile for all the openGL-wrapper objects, that points to a "real" ressource, like the blue book; and probably anything else will just eat diskspace for naught. i don't think you can teach openGL by providing "working examples for each function"; you cannot use the GEMgl... objects without having a proper knowledge of openGL. mfg.adsr IOhannes _______________________________________________ GEM-dev mailing list GEM-dev@iem.at http://lists.puredata.info/listinfo/gem-dev
----------------------------------------------------------------------------
"Free software means you control what your computer does. Non-free software means someone else controls that, and to some extent controls you." - Richard M. Stallman