[Gimp-developer] directory listing in script-fu
Hi all I want to create a script-fu for the generation of a navigation menu for photo-album VCD's. Now my problem is that I want to load all images in a certain directory, perform some actions on them and put them together into a new image which has to become the navigation menu. I tried opendir (as many did) but I (also) found out it isn't implemented in gimp-SIOD. So I searched a solution to know what files are in a specified directory, the only possible solution I found was a plug-in called file-glob which, according to Sven Neumann's reply on a message in the gimp-developer list at 24 Feb 2000, should be located in the plugin registry on the Gimp website. Sven mentioned this plugin again in another message in Dec 2001, and in both messages he is bringing up the question about adding the file-glob plugin into the distribution. I have Gimp 1.2.3 and 1.3 but I can't find the plugin to be included in my distribution. I even can't find the plugin in the plugin registry on the Gimp website. Can anyone help me out? I am looking for the file-glob plugin or another solution for getting to know what files are in a directory. Thanks in advance! Robin Roevens -- 100% MS FREE Absolutely no component of Microsoft was used in the generation or posting of this e-mail. So it is virus free ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] gimp 1.3.13 python plugins play hide-and-seek
Problem #1: This has happened to me under both Mandrake 9.0/cooker and a fresh install of Mandrake 9.1/cooker. I install from gimp-1.3.13.tar.bz2 with ./configure --enable-python $ which python /usr/bin/python $ python -V Python 2.2.2 After the make install I run gimp-1.3 and I have about 3 or 4 python plugins. I reboot the machine and now I have one python plugin, Misc - sphere. Whirlpinch, foggify, etc no longer like me :( All the python plugins start with #!/usr/bin/env python Looks ok: $ /usr/bin/env python Python 2.2.2 (#2, Feb 5 2003, 10:40:08)... Problem #2: Under Mkd9.1 my gimp 1.3.13 only has a handfull of image formats (BMP, FITS, FLI, Fax G3, SGI, XCF, xjt). I have libpng3, libpng3-devel, libjpeg62, libjpeg62-devel, etc installed on this machine. This worked on my previous mdk9.0 compile. Problem #3: A large percentage of the script-fu plugins do not work, for example script-fu - patterns - land results in ERROR: unbound vaiable (errobj plug-in-solid-noise). Is this normal on gimp 1.3.13? Sincerely, Michael ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems
Hi, Nathan Carl Summers [EMAIL PROTECTED] writes: The last time I checked, in-process tool plugin loading worked with only a handful of mild issues to be resolved. I have no doubt that it can be in perfect working order in less than two weeks. sorry, last time I checked, tools in GIMP were still an udocumented and buggy mess. The fact that part of this mess has been moved outside of the core and wrapped by obscure proxy objects has not improved this situation. There are still lots of bugs in the current tools, there is noone who fully understands how this stuff is supposed to work. What needs to be done for the next release is a major cleanup of the tools. Part of this cleanup should be a proper documentation on how to write a GIMP tool. I believe that it doesn't make sense to even think about pluggable tools before this has happened. I'd rather start the tool cleanup by moving GimpToolControl back into the core and I'd like to remove the cheesey hacks that were added all over the place. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] directory listing in script-fu
Hi, Robin Roevens [EMAIL PROTECTED] writes: Can anyone help me out? I am looking for the file-glob plugin or another solution for getting to know what files are in a directory. Didn't you send this very same mail some months ago already? Is is really that difficult to use Google? The glob plug-in has a website: http://www.bangsplat.org/gimp/ Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems
On 30 Mar 2003, Sven Neumann wrote: Hi, Nathan Carl Summers [EMAIL PROTECTED] writes: What needs to be done for the next release is a major cleanup of the tools. I agree. Part of this cleanup should be a proper documentation on how to write a GIMP tool. Providing source for a sample tool was supposed to be on the list I sent. I don't know why I didn't remember to put it on last thing. I believe that it doesn't make sense to even think about pluggable tools before this has happened. While we should have a good specification of the tool api, not thinking about plugging issues would be counterproductive. Many of the existing issues are related to the nonextensiblity of the current api. I'd rather start the tool cleanup by moving GimpToolControl back into the core I think that we should get the advice of the win32 developers because of the braindead behaviour of winbloat's dynamic linker before we move anything. Note that tool plugins will need to make calls to GimpToolModule code and GimpToolControl code and who knows what else. and I'd like to remove the cheesey hacks that were added all over the place. Which cheesey hacks are you refering to? Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp 1.3.13 python plugins play hide-and-seek
[EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: Problem #1: This has happened to me under both Mandrake 9.0/cooker and a fresh install of Mandrake 9.1/cooker. I install from gimp-1.3.13.tar.bz2 with ./configure --enable-python $ which python /usr/bin/python $ python -V Python 2.2.2 After the make install I run gimp-1.3 and I have about 3 or 4 python plugins. I reboot the machine and now I have one python plugin, Misc - sphere. Whirlpinch, foggify, etc no longer like me :( All the python plugins start with #!/usr/bin/env python Looks ok: $ /usr/bin/env python Python 2.2.2 (#2, Feb 5 2003, 10:40:08)... Problem #2: Under Mkd9.1 my gimp 1.3.13 only has a handfull of image formats (BMP, FITS, FLI, Fax G3, SGI, XCF, xjt). I have libpng3, libpng3-devel, libjpeg62, libjpeg62-devel, etc installed on this machine. This worked on my previous mdk9.0 compile. Problem #3: A large percentage of the script-fu plugins do not work, for example script-fu - patterns - land results in ERROR: unbound vaiable (errobj plug-in-solid-noise). Is this normal on gimp 1.3.13? I think you have a problem with your installation. Basically all these errors boil down to a lot of my plugins are missing. You should check if the paths to the plugins in the preferences are correct and/or delete your .gimp-1.3 - directory. Is it possible that you had multiple versions of the Gimp installed in different prefixes? Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] directory listing in script-fu
Hi, On Sunday 30 March 2003 22:14, Sven Neumann wrote: Didn't you send this very same mail some months ago already? Is is really that difficult to use Google? The glob plug-in has a website: http://www.bangsplat.org/gimp/ Well, yes I did, in the gimp-users mailing list.. not getting any answers for, indeed, some months. Assuming it was not the right mailing list to post that kind of questions, I reposted my message, in gimp-developer this time, with some slight changes in it to actualize it. I did use Google many times and searched all combinations I could imagine using the words file-glob, gimp, plugin, script-fu, directory, listing etc.. to find something usefull, the only things I found where your messages in the mailing-list archives and alot of perl-things.. But in those mails you were talking about the plugin being in the plugin registry. I hoped to find it there, but I didn't.. Anyway, thanks for the URL, I didn't manage to find that page with Google. And I still don't, what search string do I have to use to actualy find that page? Greetings Robin Roevens -- 100% MS FREE Absolutely no component of Microsoft was used in the generation or posting of this e-mail. So it is virus free ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems
Hi, Nathan Carl Summers [EMAIL PROTECTED] writes: While we should have a good specification of the tool api, not thinking about plugging issues would be counterproductive. Many of the existing issues are related to the nonextensiblity of the current api. My point is that we should first clean up the internal API and provide a framework that allows an experienced GIMP developer to create a new tool without loosing his/her mind. Once that is done, we can think about exporting this API so make pluggable tools possible. Unfortunately an attempt was made to provide an API for pluggable tools before cleaning up the internal API. Part of this API is to expose internal structures and objects that were never designed for this. I don't think we should release with this API. We would do ourselves a favor by dropping pluggable tools for now. Note that tool plugins will need to make calls to GimpToolModule code and GimpToolControl code and who knows what else. That's exactly why I propose to remove the possibility to have pluggable tools (of course only short term). The current API boils down to make calls to who knows what. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] blizzards, mononucleosis, and tool plug-in TODOitems
Sven Neumann ([EMAIL PROTECTED]) wrote: My point is that we should first clean up the internal API and provide a framework that allows an experienced GIMP developer to create a new tool without loosing his/her mind. Yesss!! pleze! Bye, Simon -- [EMAIL PROTECTED] http://www.home.unix-ag.org/simon/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
