Re: [Gimp-developer] Refocus the 2nd
Hi, Stephan Menzel <[EMAIL PROTECTED]> writes: > Do you think there's a chance to include refocus in the gimp release > at all? I think that it should be included with every gimp installation but I don't think that the only way to make this happen is to include a plug-in in the gimp source tree. If we put the tarball up on ftp.gimp.org the plug-in would very soon be included as a standard gimp plug-in by all distributions and binary installers. I don't follow refocus development closely but if is actively maintained and developed outside the GIMP source tree I'd prefer to keep it that way. Simply for the sake of keeping the GIMP source tree somewhat managable. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Refocus the 2nd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 20 May 2004 18:02, Sven Neumann wrote: > Don't get me wrong, there's nothing bad about using gimptool. Just > wanted to point out the advantages of using pkg-config. good point. I will change that according to your suggestions. Thank you. Do you think there's a chance to include refocus in the gimp release at all? Greetings... Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArRlYbv5p9h9J588RAkatAKD6SJVfDg8Z/RogyTDQGdzPQZAr8gCZAfQU S/FHP+cvQuccxPqkIIw1x6o= =ET7e -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] None
Hi, I have added a plug-in to the registry (http://registry.gimp.org/plugin?id=4177) that some may find useful: it does edge detection using the "difference of Gaussians" method, which is widely used in computational vision. Basically it works by calculating two Gaussian blurs with different radius, and then subtracting them. The implementation is pretty fast because it uses the method from gauss_rle for blurring. The motivation for doing this is that it seems to me that the existing edge detection plug-ins distributed with Gimp are rather weak in terms of output quality (their advantage is that, because they are all just 3x3 convolutions with different kernels, they are simple and very fast). I think that this DoG plug-in, and also the Thin Line plug-in from the registry (http://registry.gimp.org/plugin?id=2128) produce results that most users would be happier with. Any feedback is welcome. 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] Refocus the 2nd
Hi, Stephan Menzel <[EMAIL PROTECTED]> writes: > > pkg-config isn't related to automake. At least not more than gimptool. > > I know. But adjusting Makefile.am to use pkg-config would require be > much more knowledge of automake than simply changing it to use > gimptool-2.0. Sorry for the misunderstanding. Not really. Let me give you some examples... The standard way of using gimptool-2.0 from configure.in is to use AM_PATH_GIMP_2_0(2.0.1) The pkg-config way of doing this is: PKG_CHECK_MODULES(GIMP, gimp-2.0 gimpui-2.0 >= 2.0.1) Both macros do a version check and fill in the variables GIMP_CFLAGS and GIMP_LIBS. Additional info can be gathered by calling gimptool-2.0 directly, for example: CFLAGS=`gimptool-2.0 --cflags-noui` The pkg-config way of doing this is to use: CFLAGS=`pkg-config --cflags gimp-2.0` The advantage of using pkg-config is that it's not a GIMP specific solution. You need to learn the syntax just once and can use it for all those libraries that install .pc files. Don't get me wrong, there's nothing bad about using gimptool. Just wanted to point out the advantages of using pkg-config. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Refocus the 2nd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 20 May 2004 15:43, Sven Neumann wrote: > pkg-config isn't related to automake. At least not more than gimptool. I know. But adjusting Makefile.am to use pkg-config would require be much more knowledge of automake than simply changing it to use gimptool-2.0. Sorry for the misunderstanding. Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArL4abv5p9h9J588RAh1QAKDq0IpQpdFLQUmhi0qBHmcX7s+pIACfelIV R72qcIUmLa0ErBb2TyURiWM= =NXpG -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Refocus the 2nd
Hi, Stephan Menzel <[EMAIL PROTECTED]> writes: > as promised, I kept looking for the problem in porting refocus to > the Gimp 2. It seems like the gimptool was indeed the main issue, > but I got it running without switching to pkg-config as Sven > suggested. Thought it might be easier since I really dislike > automake. pkg-config isn't related to automake. At least not more than gimptool. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: Linux common ICC profile directory
Hi, GSR - FR <[EMAIL PROTECTED]> writes: > > /usr/share/color/icc and ~/.color/icc as intuitive paths. We > > decided to go along with this. > > Could a small change be done? Make the global dir a pair, > /usr/local/share/color/icc then /usr/share/color/icc to keep the now > traditional organization of admin made and system shipped files. It is certainly not a good tradition to have /usr/local in any standard paths. IMO the right solution is to add an environment variable to specify the search path and to have the default search path as suggested above (not including /usr/local !). However this discussion belongs to the OpenICC list and should better be continued there. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: Linux common ICC profile directory
[EMAIL PROTECTED] (2004-05-20 at 0124.38 +0200): > Marti Maria, developer of littlecms (www.littlecms.com), suggested > /usr/share/color/icc and ~/.color/icc as intuitive paths. We decided to > go along with this. Could a small change be done? Make the global dir a pair, /usr/local/share/color/icc then /usr/share/color/icc to keep the now traditional organization of admin made and system shipped files. I got the idea from, which could also be taken into account for a more detailed standard: http://freedesktop.org/Standards/basedir-spec/basedir-spec-0.6.html As side note, if anybody knows how to get a spec into freedesktop, that would be the best. The specs do not have to be huge at all, but being documented in such site would help to get them used. GSR ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Refocus the 2nd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 G'day, as promised, I kept looking for the problem in porting refocus to the Gimp 2. It seems like the gimptool was indeed the main issue, but I got it running without switching to pkg-config as Sven suggested. Thought it might be easier since I really dislike automake. I have a version now, which compiles clean and workes well without much hassle for me. The only issue is, that it seems I have lost [EMAIL PROTECTED]@ during my changes in the automakefiles which means 'make install-bin' doesn't work yet so you will have to copy 'src/refocus' to your plugindir manually. However, it worked with autoconf 2.58 and automake 1.8 as well as 1.4 for me. I placed it on my webspace for you to have a look, if anybody is interested. The code hasn't changed. But could anybody please test if it compiles and workes for you: http://www.chinguarime.net/refocus-0.9.0_gimp2.tar.gz Thank you very much. BTW: Would it be possible to include refocus in the regular gimp release? And if yes, what would be necessary? Thank you for your attention... Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArIvEbv5p9h9J588RAl79AKCcWKgUp1kS//JnGrPTRv35fuqmdQCfadH/ GdOBiZ34R8iC9OtOKRybCwY= =WS4L -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Need some feedbacks about this plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 G'day! On Monday 17 May 2004 23:23, Nicolas BENOIT wrote: > More about it: http://openair.free.fr/nbenoit/gimp-plugin-formulas.htm > > I don't want to waste your time, anyway, a feedback would be > appreciated. :) I just had a look at it and I can see heaps of potential. I find the alpha channel modification option useful in particular. However, as it is now it is merely a prototype. It definitely needs docs and lots of examples, preferably build in. Just to click and play around a bit to get a feeling for the concept. Most of my first formlas just produced error messages. It did compile clean, but I had to install it maually. make install-bin didn't seem to work. When are you planning a release? Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFArHlzbv5p9h9J588RAmr+AJ4qTQNwTfAPKsk3eKMHxRnItcm1qACgmzUW f/NnSiTH9elRdnfn3QxsSvE= =vz5N -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
