Sign up now! · Forgot password?
RSS/Atom feed Twitter

Gimp plug-ins

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

4 of 6 messages available
Toggle history

Please log in to manage your subscriptions.

20020401200103.2ED9D1F0E2@l... 07 Oct 20:15
  Gimp-user digest, Vol 1 #312 - 1 msg Seth Burgess 01 Apr 23:08
20020414190102.22C341F07C@l... 07 Oct 20:15
  Gimp-user digest, Vol 1 #326 - 6 msgs Seth Burgess 15 Apr 01:04
   Gimp-user digest, Vol 1 #326 - 6 msgs Carol Spears 15 Apr 07:50
    Gimp plug-ins Akkana 15 Apr 19:21
Seth Burgess
2002-04-01 23:08:31 UTC (over 19 years ago)

Gimp-user digest, Vol 1 #312 - 1 msg

Hi Tom,

This is probably a question better asked in the gimp-devel list.

As far as status as far as separation that would allow a KDE gui to be written, let me give what I think I know :)

There's different levels of completeness here.

Much of the code now just depends on glib (no gtk+). The GUI code is becoming more and more separated. Its off in its own directories now. For this portion of the code, it would just take someone motivated to write the KDE (qt) front end. Also, plug-ins have always been pretty separated.

However, some things we know still have an interdependance. Tools are one of those things (unless something changed when I wasn't looking). They'd probably need some rewriting to enable another toolkit. Tool code has traditionally been some of the less easy-to-grasp code in there (tile code notwithstanding), but thats getting far better too. Gimp-Perl wouldn't work terribly well, and there's probably others I'm not thinking off that would break as well.

Really the plan for having an independant library you can write your own front end for is the 2.0 GIMP release. 1.4 will be moving in that direction, and we do have a number of libraries now, but probably won't reach it. 1.4's release (if history serves) is probably a year or 2 out. 2.0 is still a way off.

And of course this depends on a KDE hacker wanting to do something with it. A long time ago, there was some ugly fighting between gnome and kde people over gimp, which if I recall correctly left a bad taste in KDE's mouth for using any of GIMP's source. I've not checked on Krayon's progress recently, but they opted for that choice back a long time ago (called KImageShop then). KDE folk may reconsider, who knows.

Happy GIMPing,

Seth Burgess sjburges@gimp.org

I think he might be asking when gimp will be able to "hook-in" to KDE such that KDE themes, etc, will appy to gimp as with other KDE "aware" apps. In other words, when will gimp be a "KDE-aware" app or will it continue to be an X app on Linux?

Peace.....

Tom

___

Seth Burgess
2002-04-15 01:04:40 UTC (over 19 years ago)

Gimp-user digest, Vol 1 #326 - 6 msgs

okay, many of the perl plug-ins that i use a lot need the pdl. seems like this has been a problem since i moved up to perl 5.5. i don't really know what it is.

i do know that if you are running perl 5.5 or above and you don't have the pdl installed, there are several useful scripts that you will not have access to via a gimp menu. a couple of the guides scripts, color2alpha and terral text are the plug-ins that i have the most recent experience with.

Carol,

None of the scripts you mentioned use PDL. One of them isn't a script (color2alpha commonly installed is in C. There is one colourtoalpha thats a gimp-perl, but its not installed by default).

You're having another problem. What are your symptoms?

Seth

___

Carol Spears
2002-04-15 07:50:23 UTC (over 19 years ago)

Gimp-user digest, Vol 1 #326 - 6 msgs

they all work for me.

i have been running into people who cannot find these scripts in the menu. i tell them to get the pdl and magically they work.

ask terral what it took to get terral text working on his computer.

in fact, when we were trying to get terral text around to show his girl friend, we found that redhat had compiled their gimp rpm without the pdl and he had to install the tarball to get it.

so. prolly you are right and installing the pdl does something else magically .... but doing that always works to get those plug-ins to appear in the menus.

carol

On 2002-04-14 at 1604.40 -0700, Seth Burgess typed this mail:

okay, many of the perl plug-ins that i use a lot need the pdl. seems like this has been a problem since i moved up to perl 5.5. i don't really know what it is.

i do know that if you are running perl 5.5 or above and you don't have the pdl installed, there are several useful scripts that you will not have access to via a gimp menu. a couple of the guides scripts, color2alpha and terral text are the plug-ins that i have the most recent experience with.

Carol,

None of the scripts you mentioned use PDL. One of them isn't a script (color2alpha commonly installed is in C. There is one colourtoalpha thats a gimp-perl, but its not installed by default).

You're having another problem. What are your symptoms?

Seth

___

Akkana
2002-04-15 19:21:28 UTC (over 19 years ago)

Gimp plug-ins

Seth Burgess writes:

None of the scripts you mentioned use PDL. One of them isn't a script

Carol Spears writes:

i have been running into people who cannot find these scripts in the menu. i tell them to get the pdl and magically they work.

ask terral what it took to get terral text working on his computer.

in fact, when we were trying to get terral text around to show his girl friend, we found that redhat had compiled their gimp rpm without the pdl and he had to install the tarball to get it.

so. prolly you are right and installing the pdl does something else magically .... but doing that always works to get those plug-ins to appear in the menus.

In case anyone is interested in more info on one specific case:

I'm on a Redhat 7.2 system. rpm -qa | grep gimp gives me this: gimp-perl-1.2.1-7
gimp-devel-1.2.1-7
gimp-data-extras-1.2.0-2
gimp-1.2.1-7
xsane-gimp-0.77-4

But those aren't actually the gimp I'm using: I have source tarballs of 1.2.2 (yes, I'm planning to upgrade :-) and 1.3.5, which are built and installed to /usr/local, which is early in my path so those are what I actually run. I haven't uninstalled the RPMs because it breaks dependencies, I have a big disk and you can't have too many gimps. :-)

/usr/local/lib/gimp/1.2/plug-ins has a long list of plugins, including lots of perl ones. These came from the 1.2.2 source (the ones from the RPM are in /usr/lib/gimp/1.2/plug-ins). Lots of these are perl, and almost none of the perl plug-ins showed up in the menus, until I followed Carol's advice and downloaded PDL-2.3.2-1.i386.rpm, which was not installed on my Redhat system (and Redhat doesn't seem to offer and RPM for it). Installing that, and removing my pluginrc, made the perl plugins magically show up in my gimp menus.

Now admittedly, 1.2.2 isn't the latest, and maybe 1.2.3 (downloading now) wouldn't have needed this PDL RPM. But meanwhile, I'm grateful for Carol's advice, which has given me access to a bunch of plugins that didn't work before.

BTW, I have the gimp-date-extras-1.2.0 tarball but I'm not sure I've ever done a build and make install from there. Would that have solved the problem without needing PDL? If so, that would be useful to know, since right now it looks like the extras are, well, extra. :-)

...Akkana