Re: [Gimp-developer] gimp plugin and gdb?
On Fri, Jul 23, 2004 at 06:15:03PM +1200, Joseph Heled wrote: While starting each plugin as a separate process has it's advantages, gdb interaction is certainly not one of them. For example, right now I bring the plugin dialog up, then look up in the process list for it, and attach it to the gdb session. Is there an easier way? But the real problem is that by the time the plugin dialog is up lots of interesting stuff has already happened. So, how can I debug run() itself in a reasonable way? (I can think of several ugly hacks to make run() stop and wait until I attach to it, but I still hope there is something I overlooked and there is a simple solution for that). Check out the developer FAQ: http://developer.gimp.org/faq.html#id2778982 So yes, you overlooked some key things. ;) -Yosh ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp plugin and gdb?
Joseph Heled wrote: But the real problem is that by the time the plugin dialog is up lots of interesting stuff has already happened. So, how can I debug run() itself in a reasonable way? (I can think of several ugly hacks to make run() stop and wait until I attach to it, but I still hope there is something I overlooked and there is a simple solution for that). Please read http://developer.gimp.org/debug-plug-ins.txt . This file is also contained in the devel-docs/ directory in the source tree. Philip ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp plugin and gdb?
Exactly what I needed! Thanks a lot. I never wondered what's in that mysterious MAIN(). Now I know at least some of the answer :) -Joseph Manish Singh wrote: Check out the developer FAQ: http://developer.gimp.org/faq.html#id2778982 So yes, you overlooked some key things. ;) -Yosh ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] TWAIN plugin for Mac OS X Win32
I've been working on porting the formerly Win32-only TWAIN plugin to Mac OS X [1]. Patched version configures, builds and runs on Mac OS X 10.3; I can successfully scan from a CanoScan U1240U using a TWAIN SANE bridge [2], but it crashes when scanning with an EPSON Perfection 1250 using EPSON's TWAIN driver. Also 'Cancel' doesn't seem to work quite right. To get out of #ifdef hell I isolated the platform-specific bits into their own file, though it's still a little scary in there. I've tried not to break the Win32 side, but I don't yet have a Win32 build environment set up to test it. The directions I found on the wiki are pretty daunting... [1] http://bugzilla.gnome.org/show_bug.cgi?id=147962 [2] http://www.ellert.se/twain-sane/ -- brion vibber (brion @ pobox.com) signature.asc Description: OpenPGP digital signature
[Gimp-developer] gimp-plugin-template: install
Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? Thanks, Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] gimp-plugin-template: install
Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? Thanks, Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] plugin: can it tell when it is called to generate a thumnail?
The topic says it all. When the Open dialog needs to generate a preview thumbnail, it calls the open plugin non interactively. However, if the plugin knew that only a small thumbnail is needed, it can use in many cases the one stored in the file. This can result in a speed up of many orders of magnitude when raw files are the target. -Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 16 bit Gimp?
Hi, Quoting Joseph Heled [EMAIL PROTECTED]: There is actually lots of the functionality I need support (and some I need to do) in the gimp already, if only the gimp was 16 bits ready. So, I wonder, any estimate how far in the future it is? Any estimate that you get will be unreliable, most likely, given the track record of the project. That said, I'll give you one. End of 2005. That is, 2.2.0 in September 2004, GEGL 1.0 (the minimum of functionality the GIMP core needs to use it) sometime around February 2005 (pure guess), and then 6 months to actually use it, followed by a 3 month pre-release cycle. That gives a release around Christmas 2005. Of wourse, this might well be complete fiction. Cheers, Dave. -- Dave Neary Lyon, France ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
On Friday 23 July 2004 09:04 am, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? You can type ./configure --help for a list of parameters that influence the installation. Maybe ./configure --prefix=/home/myname/gimp_plugins/ or similar does what you need (install where you have write-access to). Markus. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Good news
One thing we decided at the GimpCon meeting was, we need more people who proof read the manual. In that regard, I suggest we make a little plan, when some people doing proof reading. I think it's a bad idea to say something like: Here is the manual, please keep proof reading, even though it will be updated constantly. I suggest we tell the proof readers, which pages they can proof read. Those pages shouldn't change to much in the future. This applies at least for the toolbox if I remember correctly. The WIKI is up and I added a new table at the bottom of our project page to know which one proof reads which language. Please feel free to add you there, so we know which person to contact to proof read which written content. Another point which we're looking forward to, is some technical help from SuSE. Kenneth Wilmer from SuSE was present at the first GIMP meeting. After GUADEC, Dave and I were spaeking with Kenneth and he forwarded us to other SuSE people. Actually, I'm looking forward to work with the SuSE people, which will speed up the development of the whole manual. Greetings, -- Roman Joost www: http://www.romanofski.de email: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Gimp-developer] compose - decompose nitpicking
Sven Neumann wrote: Huh? At the moment compose doesn't know anything about decompose. Why shouldn't it work on layers not produced by decompose? Well, I'm a bit behind the times on this one. I haven't used compose much for the past 3-4 months, and as I recall this issue was there then, but it doesn't seem to be there now. The issue that *is* there now is that compose shows a bunch of pixbuf-related libgimp-critical error messages whenever I try to run it, but of course that's a different thing. Best, -- Bill __ __ __ __ Sent via the KillerWebMail system at primate.ucdavis.edu ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] compose - decompose nitpicking
Hi, William Skaggs [EMAIL PROTECTED] writes: The issue that *is* there now is that compose shows a bunch of pixbuf-related libgimp-critical error messages whenever I try to run it, but of course that's a different thing. The new code in gimppixbuf.c made a wrong assumption. Good that I had added a warning for the case that the assumption was violated. I've fixed the problem now by adding code that handles grayscale previews. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi Joseph, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? configure --prefix=~/gimp-2.0 should work. But if you would like to install your plug-in in the GIMP user directory (in $HOME/.gimp-2.0/plug-ins), I don't know how to do that. Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] CV: http://dneary.free.fr/CV/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
David Neary wrote: Hi Joseph, Joseph Heled wrote: Can someone tell me how to configure gimp-plugin-template so that it installs locally(~/gimp-2.0) instead of the global /usr/local? configure --prefix=~/gimp-2.0 should work. But if you would like to install your plug-in in the GIMP user directory (in $HOME/.gimp-2.0/plug-ins), I don't know how to do that. which is exactly my problem. configure sets this from GIMP_LIBDIR=`$PKG_CONFIG --variable=gimplibdir gimp-2.0` And gives no way to override it. I think this is a configure mistake. -Joseph Cheers, Dave. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] OT: noise equivalence in HSV components
HSV is the wrong colorspace to use for this purpose. The LA*B* colorspace was designed to do what you are trying to accomplish: supposedly, equal distances in LA*B* coordinate space correspond to equal distances in human perceptual space -- although I understand that there is debate about whether this is really true. I might be wrong, but this will not solve it either. I assume the AB (color information) might be in the same units, but I don't think Luminosity is. (and I can make the argument that Hue and Saturation are in the same units as well, the problem being how to fit Value in) -Joseph ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
