[of-dev] ofxShader addon
pierre at digitalstar.net
Sun Jul 11 07:35:53 PDT 2010
OK that sounds great....
looking forward to working off the git versions...
The only issue with the manager class is that you need to tell it which
directory to monitor for updates. If this is just the /data dir, it's
not a problem. But if people keep their shaders elsewhere, you then need
to coordinate with the ofxShader where that dir is, and that's where the
problems arise, because the manager needs to share this path info.
Anyway I'll get an example up soon just to start with.
On 11/07/10 14:55, Zachary Lieberman wrote:
> ofxShader will be part of the core in 007, same with ofxFboTexture.
> As for a manager class, can you write something that works against the
> current ofxShader?
> We'll start a branch in github for 007 dev and get both the latest FBO
> and latest shader stuff up, so that we all can know where to find the
> latest, and if you want to work with it or push it in different
> directions, you can work off the git.
> take care,
> On Sun, Jul 11, 2010 at 4:54 AM, Pierre Proske <pierre at digitalstar.net
> <mailto:pierre at digitalstar.net>> wrote:
> I was just reading this post:
> and I saw that Kyle has done a little work on
> ofxShader....something which I was planning to do (well, I've made
> my own changes).
> My question is, in the light of the addons refresh - is ofxShader
> going to be integrated into the core? Otherwise, where will the
> latest version be kept (I'm worried its going to turn into another
> ofxFBO with multiple versions).
> My interest is because, firstly, the addon needed a bit of an
> update, and secondly, I've made a basic framework for an
> ofxShaderManager addon, that keeps track of all currently loaded
> shaders and also monitors the shader directory, so that if you
> make a change to a shader text file, it notices the changes,
> recompiles the shaders and links the program anew. This enables
> you to make changes to the shader while the app is running, which
> saves a lot of time. I thought I could build on top of ofxShader,
> but I think I will need to re-write parts of it to accomodate a
> global shader path, a little like the ofDataPath. If it gets too
> complicated, I might just make a new ofxShader2, but I'd like to
> avoid that if possible.
> of-dev mailing list
> of-dev at dev.openframeworks.cc <mailto:of-dev at dev.openframeworks.cc>
> of-dev mailing list
> of-dev at dev.openframeworks.cc
More information about the of-dev