RSS/Atom feed Twitter
Site is read-only, email is disabled

Why modules interface?

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

3 of 4 messages available
Toggle history

Please log in to manage your subscriptions.

DE924A789E3C124F8C8A319F273... 07 Oct 20:21
  Why modules interface? Austin Donnelly 22 Jan 10:54
   Why modules interface? Michael Natterer 22 Jan 16:59
    Why modules interface? Kai-Uwe Behrmann 22 Jan 17:30
Austin Donnelly
2003-01-22 10:54:44 UTC (almost 22 years ago)

Why modules interface?

I want to add some features (changeing the gamma of the display ...) to filmgimp.

There already is a module called "cdisplay-gamma" which can do this. You don't need to write any code, just use this pre-existing module.

However, I'll still answer the rest of your questions:

I liked to implement this as removeable plug-ins but they are (as far as I expect) not selfcalling. The application I'm planning needs to start instandly with filmgimp.

By "selfcalling", I assume you mean that it starts automatically.

1. Is the modules interface the best way for this?

Yes, because changing the gamma of the display requires tight integration with the display code.

2. What are all the differences between plug-ins and modules?

Plugins run in their own process, so if there is a bug in a plugin, it should not crash the gimp. Modules run in the same process as the main gimp, so a bug in the module can crash the entire thing.

The only reason you should use a module is if your code needs to be called so frequently that the overhead of being in a separate process is too much. Or, if you need to share state with the main gimp application (eg because you are extending the main UI directly, like the colour selectors do).

Hope this helps, Austin

Michael Natterer
2003-01-22 16:59:40 UTC (almost 22 years ago)

Why modules interface?

"Austin Donnelly" writes:

I want to add some features (changeing the gamma of the display ...) to filmgimp.

There already is a module called "cdisplay-gamma" which can do this. You don't need to write any code, just use this pre-existing module.

The best idea IMHO would be to drop this silly film-gimp code duplication and help coding on gimp 1.4 (which already has this feature).

ciao,
--mitch

Kai-Uwe Behrmann
2003-01-22 17:30:17 UTC (almost 22 years ago)

Why modules interface?

Am 22.01.03, 16:59 +0100 schrieb Michael Natterer:

"Austin Donnelly" writes:

I want to add some features (changeing the gamma of the display ...) to filmgimp.

There already is a module called "cdisplay-gamma" which can do this. You don't need to write any code, just use this pre-existing module.

The best idea IMHO would be to drop this silly film-gimp code duplication and help coding on gimp 1.4 (which already has this feature).

Of course one programm would be fine for developing together. At the moment many people await the gimp-2.0 with gegl and 16bit, floats, cmyk, CIE Lab ...

Filmgimp is near to the above mentioned colordepths. Therefore I decided to programm for it.

ciao,
--mitch

regards
Kai-Uwe