On 17/03/2008, Stefan Dösinger stefan@codeweavers.com wrote:
Do you mean the term "ffp replacement", or what the code is doing? I for one call our nvrc code an ffp replacement as well, however, there's no sharp border between programmable and fixed function functionality. I've seen articles which called GL_ARB_texture_env_combine "programmable" as well.
It's mostly a matter of where you integrate it into the code. At this point I don't really see the advantage of making it a different shader backend compared to integrating it into the existing fixed function code.