These are problems that I've had with GIMP since I started...
Web-o-tine, a Script-FU version of Perl-o-tine, does not work properly in Puppy/Grafpup. But that script was only tested in Windows, not Linux.
So on to Perl-o-tine...the problem is that GIMP doesn't seem to be loading my Perl-o-tine plug-in.
It's supposed to show up under Filter/web
What is GIMP missing to get perl plugins working in it?
This is very important because some of the web sites I work on are using sliced images, including the Linux Arts web site. The perl-o-tine plugin is what slices the images and puts them back together in HTML.
The only problem is the perl plugins aren't loading.
Any help would be GREATLY appreciated.
Perl-o-tine plugins not loading in GIMP (continued)
Perl-o-tine plugins not loading in GIMP (continued)
I posted this on the Grafpup board, and am posting this here too.
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
There's a few possibilities here. Gimp plugins have to be compiled for the specific series that you are using or the program will simply ignore them. In other words, if you are running Gimp-2.0.6 (from the Puppy Repository) you could use a plugin compiled against Gimp-2.0.3, but not one compiled against Gimp-2.3.5. With me so far?
The next thing that can cause errors like this is where you place the plugin at. The easiest and most reliable place to put it is inside your home directory in .gimp-2.x (x for whatever series of Gimp you're using). The location of all the system wide Gimp plugins depends on the prefix it was compiled for. The first two Grafpup releases had Gimp compiled for /usr, so the plugins directory was in /usr/lib/gimp/2.x. The latest version has Gimp compiled for /usr/local, so the plugins directory is in /usr/local/lib/gimp/2.2. I added /usr/lib to the system profile so I could compile some programs for Grafpup and for Vector and only have to do it once. I'd recommend sticking with the first location I mentioned.
I'm not sure how the perl plugins work and whether I'd have to explicitly set a configure option to enable it. I'll have to read the docs again. If there is an actual problem with using Perl plugins I'll fix it before the final Grafpup-1.0.1 release. I'll take a closer look at the plugin you're trying to use and get back to you.
Nathan
The next thing that can cause errors like this is where you place the plugin at. The easiest and most reliable place to put it is inside your home directory in .gimp-2.x (x for whatever series of Gimp you're using). The location of all the system wide Gimp plugins depends on the prefix it was compiled for. The first two Grafpup releases had Gimp compiled for /usr, so the plugins directory was in /usr/lib/gimp/2.x. The latest version has Gimp compiled for /usr/local, so the plugins directory is in /usr/local/lib/gimp/2.2. I added /usr/lib to the system profile so I could compile some programs for Grafpup and for Vector and only have to do it once. I'd recommend sticking with the first location I mentioned.
I'm not sure how the perl plugins work and whether I'd have to explicitly set a configure option to enable it. I'll have to read the docs again. If there is an actual problem with using Perl plugins I'll fix it before the final Grafpup-1.0.1 release. I'll take a closer look at the plugin you're trying to use and get back to you.
Nathan
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
I don't think you're going to like what I have to say next. The only version I can find on the net of the perl-o-tine script is made for Gimp-1.1, so it probably won't ever wirk with any Gimp-2.x. It might be possible to get an older version of Gimp and the GImp-perl package and run the script that way, but it would have to install into a seperate prefix if you wanted to run it alongside a newer version of Gimp. This might entail compiling it from source, as a package compiled for /usr or /usr/local could very well cause problems for another Gimp installation and you might end up with two unusable Gimps.
I don't have a lot of time for compiling right now but if you want to give it a try, it would be easier to compile it without printing or python.
You'll need both the Gimp package and the Gimp-perl package as the 1.x series did not have Gimp-perl by default (if memory serves).
Nathan
I don't have a lot of time for compiling right now but if you want to give it a try, it would be easier to compile it without printing or python.
Code: Select all
./configure --prefix=/usr/local/gimp10 --disable-print --disable-python
Nathan
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
There appears to be another script called py-slice that can do the same things. Unfortunately it requires Python and Gimp-python. I didn't compile Python support into Gimp for Grafpup and I'm sure Barry didn't compile it into Gimp-2.0.6 for Puppy. It might be possible to add it as an extra option. I did build Gimp with Python for Vector, so I might be able to use that to create an addon package.
One of the problems with this is that I've been getting some reports that the Python package doesn't work anyway. I had been thinking of removing it, as I'm not a fan of Python anyway. I really wish people would just code in C so it can be turned into a binary.
Nathan
One of the problems with this is that I've been getting some reports that the Python package doesn't work anyway. I had been thinking of removing it, as I'm not a fan of Python anyway. I really wish people would just code in C so it can be turned into a binary.
Nathan
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
For anyone who might be following this thread but not it's parallell on the Grafpup board i wanted to post the following news on the topic. I've compiled Python and PyGTK from source using Puppy and will have the package available soon. I've also gotten Gimp-2.2.9 re-compiled using Puppy and it now will have the option of using the Python scripts (with an addon package). This version of Gimp will be fully compatible with Puppy-107 as Barry is upgrading freetype for that release.
Nathan
Nathan
- Nathan F
- Posts: 1764
- Joined: Wed 08 Jun 2005, 14:45
- Location: Wadsworth, OH (occasionally home)
- Contact:
Most of this appears to be solved now, with the exception of the Perl module which is going to take a lot of work. Most of the Perl scripts do have equivelents in Python or scheme, however, so there are working alternatives for this now.
The current Gimp package that I've compiled for Grafpup (Gimp-2.2.9, current version for Puppy is 2.0.6) will be fully compatible with Puppy-107, as Barry is upgrading libfreetype. I have also compiled Python and PyGTK, plus a package containing all of the Python extensions for Gimp.
The Perlotine plugin that kicked this all off has two alternatives that both work with this version of Gimp, PySlice and Webotine. Webotine is fully compatible with Gimp-2.0.6 also.
I'd like to contribute some of the work I've done on Gimp back into Puppy. It's up to Barry which Gimp package will go into the repository at ibiblio, but I might make some Gimp extensions available as dotpups for Puppy users as well.
Nathan
The current Gimp package that I've compiled for Grafpup (Gimp-2.2.9, current version for Puppy is 2.0.6) will be fully compatible with Puppy-107, as Barry is upgrading libfreetype. I have also compiled Python and PyGTK, plus a package containing all of the Python extensions for Gimp.
The Perlotine plugin that kicked this all off has two alternatives that both work with this version of Gimp, PySlice and Webotine. Webotine is fully compatible with Gimp-2.0.6 also.
I'd like to contribute some of the work I've done on Gimp back into Puppy. It's up to Barry which Gimp package will go into the repository at ibiblio, but I might make some Gimp extensions available as dotpups for Puppy users as well.
Nathan