On Wed, Sep 24, 2008 at 09:13:10PM +0200, Martin Christensen wrote: > I quite agree that what interface is concerned, plugins should integrate > into Rawstudio like the current tools do today.
This really limits you to only two choices; eihter a distributed objects model, or an .so approach. (Ok, I know there are a few more ways to do it but these are the easy ones.) > As for the rest of your post, Einar, it is very C-centric, and I think > that we should beware of painting ourselves into that corner. Well, it is Unix specific, but things like shared memory should be possible in almost any language. Anyway, my reasoning is that the so- file + shared memory approach gives plugins the possibility to do fast updates, so that sliders etc can be done realtime. I fully agree with you that for small personal hacks C(++) may be too cumbersome, but it would not take much effort to write a simple pipelining tool that implements your config+image pipeline on top of this. Going the other way and trying to build a fast interactive plugin on top of pipelines is a lot harder. -- Einar Ryeng _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
