> You're very welcome! But if you would like to have your filter included > in mainline Rawstudio, be prepared for some discussion ;-)
Thanks, I'm prepared :-) > Please make sure that you are using newest Rawstudio from subversion. > The filter code is currently being developed and is subject to change at > any time. Yup, I've been using that for a while.. can't wait to have the latest features. > If you have graphviz installed, you can try "Debug" -> "Filter Graph" > for an overview of the current filter chain. This seems to show only the default chain which is specified in application.c .. is that right? At least my installed plugin does not appear there unless I add it to the chain which I think I'm not supposed to do. > > If you look at the console when starting Rawstudio, you can currently > see some debug information about loaded plugins. Yeah, I managed to get my plugin show up there. >> 1) how the data moves between plugin and the program? > > Well. For the most part it doesn't. It mostly moves from filter to > filter. The application can use rs_filter_get_image() (and a handful of > other functions) to extract data from the last filter. What specifies in which order the plugins are processed? > > g_object_set() is used for setting processing parameters for most > filters. If the plugin is not marked "dirty" via setting the properties does it ever get computed (is get_image called for it)? My problem is that the plugin does the loaded but it does not affect the images.. I tried putting it in the filter chain in application.c and it seems to work (wow :-) but I can't make it do anything if I don't hardwire it in the filter chain. >> 2) how do I register a plugin so the program knows it's there > > It's quite simple. Just install it ;) Rawstudio will search the plugin > path for any plugins. > For an example of an plugin that build out-of-tree take a look at > RawSpeed. I think I'll have a look at that too :-) >> 3) how do I specify how the plugin shows up in the GUI? > > Currently plugins have no way of altering the GUI. So the GUI has to be built in the application itself? I think I'd like to have a color picker for the B&W filter to simulate color filters. >> BTW. The idea of being able to specify the processing flow (what image >> processors affect the image and in which order) is *great* > > Please note that this is only for the programmer - not for the end user. > And probably never will be. That's a shame.. I liked the idea in Lightzone. - Sampo _______________________________________________ Rawstudio-dev mailing list [email protected] http://rawstudio.org/cgi-bin/mailman/listinfo/rawstudio-dev
