does anyone have use for something like this?
i have made a simple tex-env-combine language to fill a hole in a larger project i am doing, but i can easily break it out into a separate lib. very much like nvparse RC1.0 syntax but even simpler…eg:
(don’t take that program seriously)
i’ve found it very helpful if you have the app load (and reload, on demand) the programs from disk - no recompiling. useful for fallback shaders - can u buy an openGL card without tex-env-combine these days?
if anyone’s interested i’ll put a page up - or have u all already made your own?
I’ve also done something like this for my current project, but i found RC1.0 syntax a little overkill for something so simple. Mine also allows control over which texture unit to use. Your example setup in my syntax would be:
It’ll also handle texture_env_dot3, texture_env_crossbar and nv_texture_env_combine4. It was fun to write. I did it mostly to give myself a crash course on lex/flex and yacc/bison, but it has since been proven to be a very valuable tool for all my projects. Who wants to type all that endless glTexEnv calls anyway? It can handle that as well As a command line switch it’ll generate C code for all the calls.
good to see another gl coder on this side of the world
fenris - despite your disavowal of RC1.0 syntax, i’ve gotta say what we’ve done looks pretty similar. not that there’s too many options doing something like this… wonder how many others have reinvented the same wheel in the same way?
fenris, could you put your stuff up on the web? It would be a great timesaver for our project as well (http://reaper3d.sf.net). It has all the features I am looking for.
(I have a very primitive thing working, but never finished it, got busy with other details instead.)