After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 641893 - "Color Range Mapping" plug-in missing since 2.4
"Color Range Mapping" plug-in missing since 2.4
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: Plugins
git master
Other All
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2011-02-09 02:50 UTC by Owen Swerkstrom
Modified: 2018-05-24 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
patch with upgraded plug-in (18.56 KB, patch)
2011-02-09 02:50 UTC, Owen Swerkstrom
none Details | Review
screenshot of a use case (306.53 KB, image/png)
2011-02-09 20:09 UTC, Owen Swerkstrom
  Details
patch for released 2.6.x versions (21.47 KB, patch)
2011-08-22 21:00 UTC, Owen Swerkstrom
none Details | Review

Description Owen Swerkstrom 2011-02-09 02:50:33 UTC
Created attachment 180434 [details] [review]
patch with upgraded plug-in

This plug-in was extremely useful and its functionality is not available in any existing plug-in.  The old plug-in no longer loads in newer versions of GIMP, either.

So, I dug up the old code and did some refactoring and cleanup.  A shiny new version of the plug-in now builds and runs happily, restoring functionality I and many others have been sorely missing for a while now.

If there are any objections at all to this patch, please email me; I will bend over backwards to get this feature back.  Just tell me what to do.
Comment 1 Michael Schumacher 2011-02-09 17:28:10 UTC
This has been re-implemented as a PDB procedure in Script-Fu - you don't mention if this suits your needs, so please report back if you were aware of this.
Comment 2 Owen Swerkstrom 2011-02-09 19:54:29 UTC
(In reply to comment #1)
> This has been re-implemented as a PDB procedure in Script-Fu - you don't
> mention if this suits your needs, so please report back if you were aware of
> this.

I searched all over the Script-Fu Procedure Browser, but didn't find anything (other than my "plug-in-colorrangemap") that does the job.  What command/procedure are you referring to?
Comment 3 Owen Swerkstrom 2011-02-09 20:09:12 UTC
Created attachment 180505 [details]
screenshot of a use case

Here's an example of the plug-in in action.  If GIMP has some other way of doing this, I haven't been able to find it.  Note the anti-aliased edges being dealt with correctly, and not having to guess at color wheel angles or set up gradients.
Comment 4 Owen Swerkstrom 2011-03-30 15:07:28 UTC
Any news?  Even if you don't understand why this feature is important to me, can somebody either commit this or let me know why not?  Thanks...
Comment 5 Martin Nordholts 2011-03-30 16:49:43 UTC
Personally I am only interested in a GEGL version of this plug-in, but others might have a different opinion.
Comment 6 Owen Swerkstrom 2011-03-30 19:46:27 UTC
Thanks for the response.  I don't know if I will find the time, but I would be willing to dive in and make a GEGL version.  Should I just try to learn by example from the various operations in app/gegl?  Is there a Gimp-oriented reference or guidelines anywhere for GEGL development?
Comment 7 Mukund Sivaraman 2011-05-07 01:46:52 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > This has been re-implemented as a PDB procedure in Script-Fu - you don't
> > mention if this suits your needs, so please report back if you were aware of
> > this.
> 
> I searched all over the Script-Fu Procedure Browser, but didn't find anything
> (other than my "plug-in-colorrangemap") that does the job.  What
> command/procedure are you referring to?

See bug #558454 and bug #436145.

There was a good reason why this plug-in was removed.
Comment 8 Owen Swerkstrom 2011-05-11 19:29:39 UTC
That's some disheartening reading.  I'm sorry several devs think it's "broken" but don't care to "fix" it.  I've got my copy, which I've "fixed" and works exactly as desired, and nobody else cares, at least nobody who matters, so I guess we're set.

I appreciate strict, clean code too, but I'd rather have a rich tool set built "with" (not "for") the community with a few warts in it than one that's super-tidy inside and missing useful stuff.

I'm obviously a fan of GIMP and the work you guys do, so thanks anyway.
Comment 9 Owen Swerkstrom 2011-08-22 21:00:26 UTC
Created attachment 194418 [details] [review]
patch for released 2.6.x versions

I've gotten some interest in getting this running with non-git code, so here is a version of my patch which applies cleanly against 2.6.x.

There is some demand for this feature; it's not just me.  :^)
Comment 10 Martin Nordholts 2011-08-23 04:50:54 UTC
Thank you for your efforts. But, ff we accept this patch, we will create more work for ourselves when we move to GEGL, and we don't want more work I'm afraid. If you would GEGL based patch that would be a lot more interesting.
Comment 11 Owen Swerkstrom 2011-08-23 17:36:40 UTC
I'd be glad to reimplement this in GEGL (when I have a bit of time).  Is there some documentation you'd recommend for a GEGL virgin?  I can go by example, are there some GEGL plug-ins (with UI) that you'd suggest I use as a guideline?  Thanks.
Comment 12 Alexandre Prokoudine 2014-11-13 01:32:59 UTC
Owen,

I'm sorry that we let this slip. There's some initial information about porting GIMP filters to GEGL here:

http://wiki.gimp.org/wiki/Hacking:Porting_filters_to_GEGL

We usually discuss technical specifics on our IRC channel. Don't hesitate to drop by, although it's best to stick there for a while because of timezones and suchlike.
Comment 13 Owen Swerkstrom 2014-11-14 17:24:06 UTC
Cool!  I'll have to dig in to that documentation and maybe finally revive this feature properly.  :^)  Just a week or two ago I was wishing I still had this.  Thanks Alexandre!
Comment 14 GNOME Infrastructure Team 2018-05-24 12:57:23 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/359.