Re: [Gimp-developer] 2 Questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Good morning, On Tuesday 11 May 2004 10:53, Dave Neary wrote: > The proper way to do this, I suppose, would be to get rid of the "color" > option from the text tool options, and just use the foreground in the same > way as the other paint tools use it (keep it in the context, but don't set > it by default). Exactly. This is how it used to be and this is how it should be. The extra color option in the text options is not needed. Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoKM1bv5p9h9J588RAohFAKD6PMKglAj8kH7XkAU+5eC6iRPZYQCg9HEG qTlXMRx/Du6lrPuHZ9ATUW0= =5FAv -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Sven, On Tuesday 11 May 2004 12:13, Sven Neumann wrote: > As I already explained in a previous mail, Dave is wrong here and the > color button is needed. The way it used to be there wasn't the concept > of editable text layers. With the introduction of text layers the > color button became necessary. I have seen your Mail later, sorry. Does that mean, that this color must default to black as well? There can be an extra color button in that dialog, no worries, but couldn't it default to the picked foreground color when this text layer is created in the first place? Or is that how it is supposed to be? Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoKjnbv5p9h9J588RAuIIAJ0eYsJf/uOWX+5rtNyXPHAbChf1DQCfd3N0 Uy+JpWEYANgpjcVML1EFX4w= =nTPO -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] 2 Questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 G'day, Since I migrated to Gimp 2.0.1. I noticed are a few little things you have apparently changed but I don't really understand why. Here are but 2: 1. Whenever I click on the 'Insert Text' Button, the foreground color as well as the color for the text itself changes to black. Though it is possible to use another color it is much more complicated than before (1.2.2). Why? I often pick a color out of the picture with this little colorpickertool and then insert text in this color that matches another in the picture. Black is the least I would use. But now this is complicated and rather a pain. Does this change have any purpose I just don't see? Anyway, if it doesn't, can you change that back in the next release? 2. The new 'Crop' tool is not as simple as the old. Formerly there used to be a border that opens and you could drag the corners around until they finally matched what you wanted and then you pressed the crop button. There was a shortcut too. (Ctrl+c?) Now the shortcut seems to be gone and there are no longer dragable corners. You have to use rectangular selection instead which doesn't have this. (Or does it?) And when I choose 'crop' in the menu, there is a new selection just slightly smaller than the picture over almost the entire crop. I can't really see the purpose for that. The cropped image seems to be slightly larger than the area I actually selected too. I hope you understand those thoughts being constructive criticism or stupidity on my side. It is not meant to be bad or something and I have the greatest respect and thanks for all the developers of gimp. Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAn91Qbv5p9h9J588RAr+RAKCppqAyyK4RwhNrJX0Uguw5bbvZqQCgoqS1 6PKRDul5+C/uw39oB5zN+uA= =fUom -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 2 Questions
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, On Monday 10 May 2004 22:59, Sven Neumann wrote: > The foreground color is not supposed to change. If it really does, > that would be a bug. However I don't seem to able to reproduce this. Well, it does here. I can reproduce it every time. 0. Load Gimp and load any picture (tried with RGB and Greyscale) 1. press O 2. pick a color from the picture 3. close the little color chooser window 4. press T or click the Text button - -> The forgroundcolor is black again and so is the text. As I said, I use version 2.0.1, which works fine, besides this. If it really is a bug. It wouldn't be so bad if I could choose a new color from the textcolorwidget but there is only the color dialog which is inconvenient. I prefer 'o'. > I am sorry but the crop tool didn't change at all. You should still be > able to drag the corners just as in GIMP 1.2. We only added a > convenient way to crop the image to the size of the current selection > (Image->Crop Image) but that's not really related. Ooops. I just didn't see it in the menu where expected and I assumed it is gone or rather it has changed that way. It does indeed work as usual which is great and I apologize. Even the shortcut works and I should have noticed that. However, it might be confusing for some users to have two crop possibilities instead of one distinct way. Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAoAfzbv5p9h9J588RArbqAJ9qCu/NBk7lCBZ78JwR4GQQ9BE1fACfUg7I cQAYDQLLFHIXAcMGf5jeqJA= =GerS -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Gimp2 plugin porting problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 G'day! I started porting one of my favourite plugins for gimp 1.2 to the new 2.0.1. The sources are already compiling against the new headers and everything looks fine. Unfortunately, the gimp isn't loading the plugin properly. There is just a message like this: (gimp-2.0:6432): LibGimpBase-WARNING **: gimp-2.0: wire_read(): error However, the Gimp is starting normally without crashing but the plugin is not available. I suspect, there might be a problem with compiler options or some registering issue but I double checked it all (well, as far as I know which doesn't mean a lot). Does anybody have a clue what I could do? Stephan My system is: RedHat Linux 9 gcc 3.2.2 gnome2.2.0 -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAlTQlbv5p9h9J588RAnmfAJ9Q9aOVTAKlYb/84CyL/3a87qgPpACcDMWp dpwU659smJQX3NmmJe/XpOo= =6LW9 -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp2 plugin porting problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 02 May 2004 20:39, Sven Neumann wrote:
Hi Sven,
> Start gimp with the --verbose command-line option and check if it's
> seeing your plug-in at all.
Did that. The Plugin is recognized. Just the loading fails ist sais:
...
INIT: gimp_real_restore
Plugin »/home/stephan/.gimp-2.0/plug-ins/refocus« wird abgefragt
(gimp-2.0:6855): LibGimpBase-WARNING **: gimp-2.0: wire_read(): error
...
(Sorry for the german gibberish. To lazy to change local...)
> We didn't change the way that plug-ins are
> registered, so I don't know what could be causing this. I'd have to
> have a look at the source.
The plugin in question is 'refocus' by Ernst Lippe. The whole lot is quite a
fair bit but this is query():
MAIN ()
void query (void)
{
static GimpParamDef args[] = {
{GIMP_PDB_INT32, "run_mode", "Interactive, non-interactive"},
{GIMP_PDB_IMAGE, "image", "Input image (unused)"},
{GIMP_PDB_DRAWABLE, "drawable", "Input drawable"},
{GIMP_PDB_INT32, "mat_size", "Size of matrix"},
{GIMP_PDB_FLOAT, "radius", "Circle radius"},
{GIMP_PDB_FLOAT, "gauss", "Parameter for Gaussian convolution"},
{GIMP_PDB_FLOAT, "correlation", "Correlation"},
{GIMP_PDB_FLOAT, "noise", "Noise to Signal ratio"},
};
static GimpParamDef *return_vals = NULL;
static gint nargs = (gint) (sizeof (args) / sizeof (args[0]));
static gint nreturn_vals = 0;
gimp_install_procedure ("plug_in_refocus",
"Refocus with FIR Wiener Deconvolution",
"refocus!",
"Ernst Lippe",
"Ernst Lippe",
"1999",
"/Filters/Enhance/Refocus...",
"RGB*, GRAY*",
GIMP_PLUGIN,
nargs, nreturn_vals,
args, return_vals);
}
It is almost untouched by any modifications.
Looks just like in all the other plugins to me.
I assume the problem might be the Makefile:
...
CC = gcc
GCC3 = gcc
GIMPTOOL = /usr/local/bin/gimptool-2.0
GIMP_CFLAGS = -g -O2 -Wall -I/usr/local/include/gimp-2.0
- -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
- -I/usr/include/pango-1.0 -I/usr/X11R6/include -I/usr/include/freetype2
- -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
GIMP_CFLAGS_NOUI = -I/usr/local/include/gimp-2.0 -I/usr/include/glib-2.0
- -I/usr/lib/glib-2.0/include
GIMP_DATA_DIR = /usr/local/share/gimp/2.0
GIMP_LIBS = -L/usr/local/lib -lgimpui-2.0 -lgimpwidgets-2.0 -lgimp-2.0
- -lgimpcolor-2.0 -lgimpmath-2.0 -lgimpbase-2.0 -Wl,--export-dynamic
- -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0
- -lpangox-1.0 -lpango-1.0 -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
GIMP_LIBS_NOUI = -L/usr/local/lib -lgimp-2.0 -lgimpcolor-2.0 -lgimpmath-2.0
- -lgimpbase-2.0 -lgobject-2.0 -lglib-2.0
GIMP_PLUGIN_DIR = /usr/local/lib/gimp/2.0
GLIB_CFLAGS = -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
GLIB_GENMARSHAL = glib-genmarshal
GLIB_LIBS = -lglib-2.0
GLIB_MKENUMS = glib-mkenums
GOBJECT_QUERY = gobject-query
GTKDOC = false
GTK_CFLAGS = -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
- -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include
- -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
GTK_LIBS = -Wl,--export-dynamic -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0
- -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0
- -lgmodule-2.0 -ldl -lglib-2.0
HTML_DIR = ${datadir}/gtk-doc/html
LAPACK_INCLUDE_DIR = ${top_srcdir}/lib
LAPACK_LIB_DIR = ${top_srcdir}/lib
MAKEINFO = makeinfo
PACKAGE = refocus
PKG_CONFIG = /usr/bin/pkg-config
RANLIB = ranlib
VERSION = 0.9.0
#GTK_DOC_DIR = #gtk-doc
GTK_DOC_DIR =
...
Can you see anything wron in the compiler or linker options?
I had to change ./configure's options to override the old gimp settings.
Thanks a lot!
Stephan
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFAlUNrbv5p9h9J588RAu5PAKDGjM0LsNW7++ePX5MBtPPmKmEMuwCfT+bP
aH7xXsGWuH/E/LfN7O/rHoc=
=GcAq
-END PGP SIGNATURE-
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp2 plugin porting problems
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
G'day!
On Sunday 02 May 2004 21:32, Jean-Luc wrote:
> There is a patch for refocus on sourceforge.
> If was built for 1.3 but I have applied it and, with this patch applied,
> the plugin works for me [tm] with gimp 2.0.1.
>
> You can find the patch at:
> http://sourceforge.net/tracker/?atid=535004&group_id=72588&func=browse
Thank you for your efforts and for that clue.
I applied this patch which did pretty much the same stuff I did, apart from
some changes in the Makefile. However, it still doesn't work. The same
problem. I could find out some more information though that might be helpful.
In the src of refocus, there is a test-matrix module compiled, which is not
installed by default. I just copied it to the plugin directory to see, what
happens. And it is loaded, performs some tests and exits. But it is not a
proper plugin. It simply contains a main like this..
int
main (int argc, const char *argv[]) {}
Nothing else. No GimpPlugInInfo and no query(). Gimp2 loads and executes it.
Is that supposed to happen?
It is built using the same Makefile as refocus itself and uses the very same
routines too. I tried including a similar main() in the refocus source but it
still doesn't load.
The next thing I tried was executing those binaries directly. And here it is
the opposite. The modified refocus binary executes and prints my included
'hello world'. The untouched test-matrix binary just throws a segmentation
fault. That brings me to the conclusion that although the Makefile looks
identical, there must be some difference in the way those binaries are
created.
I also tried a strace which showed nothing suspicious. The plugin is loaded
with the same function and return code as all the others.
I start to find all that rather interesting but i am still anoyed that I have
to run two gimps at the same time now. The old one to do refocus and the new
one for everything else. It's consuming lots of memory too so I would really
like to see refocus working with 2.0. Any ideas or hints what to do or check
next? Hoping it is alright for Ernst I include the src/Makefile and both
sources.
Thanks a lot!
Stephan
src/Makefile:
# Makefile.in generated automatically by automake 1.4-p5 from Makefile.am
# Copyright (C) 1994, 1995-8, 1999, 2001 Free Software Foundation, Inc.
# This Makefile.in is free software; the Free Software Foundation
# gives unlimited permission to copy and/or distribute it,
# with or without modifications, as long as this notice is preserved.
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY, to the extent permitted by law; without
# even the implied warranty of MERCHANTABILITY or FITNESS FOR A
# PARTICULAR PURPOSE.
SHELL = /bin/sh
srcdir = .
top_srcdir = ..
prefix = /usr/local
exec_prefix = ${prefix}
bindir = ${exec_prefix}/bin
sbindir = ${exec_prefix}/sbin
libexecdir = ${exec_prefix}/libexec
datadir = ${prefix}/share
sysconfdir = ${prefix}/etc
sharedstatedir = ${prefix}/com
localstatedir = ${prefix}/var
libdir = ${exec_prefix}/lib
infodir = ${prefix}/info
mandir = ${prefix}/man
includedir = ${prefix}/include
oldincludedir = /usr/include
DESTDIR =
pkgdatadir = $(datadir)/refocus
pkglibdir = $(libdir)/refocus
pkgincludedir = $(includedir)/refocus
top_builddir = ..
ACLOCAL = aclocal-1.8
AUTOCONF = autoconf
AUTOMAKE = automake-1.8
AUTOHEADER = autoheader
INSTALL = /usr/bin/install -c
INSTALL_PROGRAM = ${INSTALL} $(AM_INSTALL_PROGRAM_FLAGS)
INSTALL_DATA = ${INSTALL} -m 644
INSTALL_SCRIPT = ${INSTALL}
transform = s,x,x,
NORMAL_INSTALL = :
PRE_INSTALL = :
POST_INSTALL = :
NORMAL_UNINSTALL = :
PRE_UNINSTALL = :
POST_UNINSTALL = :
CC = gcc
GCC3 =
GIMPTOOL = /usr/bin/gimptool-2.0
GIMP_CFLAGS = -I/usr/include/gimp-2.0 -I/usr/include/glib-2.0
- -I/usr/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
- -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include
- -I/usr/include/freetype2
GIMP_CFLAGS_NOUI = -I/usr/include/gimp-2.0 -I/usr/include/glib-2.0
- -I/usr/lib/glib-2.0/include
GIMP_DATA_DIR = /usr/share/gimp/2.0
GIMP_LIBS = -Wl,--export-dynamic -lgimpui-2.0 -lgimpwidgets-2.0 -lgimp-2.0
- -lgimpmath-2.0 -lgimpcolor-2.0 -lgimpbase-2.0 -lgtk-x11-2.0 -lgdk-x11-2.0
- -latk-1.0 -lgdk_pixbuf-2.0 -lm -lpangoxft-1.0 -lpangox-1.0 -lpango-1.0
- -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0
GIMP_LIBS_NOUI = -lgimp-2.0 -lgimpmath-2.0 -lgimpcolor-2.0 -lgimpbase-2.0
- -lglib-2.0
GIMP_PLUGIN_DIR = /usr/lib/gimp/2.0
GLIB_CFLAGS = -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
GLIB_GENMARSHAL = glib-genmarshal
GLIB_LIBS = -lglib-2.0
GLIB_MKENUMS = glib-mkenums
GOBJECT_QUERY = gobject-query
GTKDOC = false
GTK_CFLAGS = -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
- -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/usr/X11R6/include
- -I/usr/include/freetype2 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
GTK_LIBS = -Wl,--export-dynamic -lg
Re: [Gimp-developer] Gimp2 plugin porting problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Monday 03 May 2004 17:02, Ernst Lippe wrote: > I think that I have found cause of the Stephan's problem. > My plugin used GTK-2, so in the makefiles I had to use some > tricks to get the correct include path and libraries. I could > not directly use the output of the old gimptool, because that used > the wrong GTK versions. Hello Ernst! yes, that seems right. gimptool caused problems during configure and I tried several workarounds that seemed to work in the first place but this was some kind of wishful thinking. > I did not have time to look at the patch at sourceforge, but it seems like > Stephan is linking with the old version of the libgimp libraries. The > obvious solution is to simply use the outputs from gimptool-2 instead of my > hacked version. I am afraid that I don't have the time right now to suggest > a good solution (anyhow I don't have Gimp-2 installed, so I can't test any > modifications). I just checked with ldd as Sven suggested and here's the output: libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0x40033000) libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0x40288000) libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0x402f7000) libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0 (0x4031) libm.so.6 => /lib/tls/libm.so.6 (0x40324000) libpangoxft-1.0.so.0 => /usr/lib/libpangoxft-1.0.so.0 (0x40346000) libpangox-1.0.so.0 => /usr/lib/libpangox-1.0.so.0 (0x40367000) libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0x40374000) libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0x403a7000) libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0x403dc000) libdl.so.2 => /lib/libdl.so.2 (0x403e1000) libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0x403e5000) libgimp-1.2.so.0 => /usr/lib/libgimp-1.2.so.0 (0x4044f000) libc.so.6 => /lib/tls/libc.so.6 (0x4200) libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0x4047) libXrandr.so.2 => /usr/X11R6/lib/libXrandr.so.2 (0x4054e000) libXi.so.6 => /usr/X11R6/lib/libXi.so.6 (0x40553000) libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0x4055b000) libXft.so.2 => /usr/X11R6/lib/libXft.so.2 (0x40569000) libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0x4057b000) libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0x40583000) libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0x405aa000) libz.so.1 => /usr/lib/libz.so.1 (0x405fc000) /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x4000) libglib-1.2.so.0 => /usr/lib/libglib-1.2.so.0 (0x4060a000) libexpat.so.0 => /usr/lib/libexpat.so.0 (0x4062f000) I understand it links against libgimp-1.2 which is apparently wrong. Jean-Luc meanwhile sent me a compiled binary and refocus is running now with my gimp2 which is great and I can continue my work. However, I will try to work more on the problem and I will post a solution when I found it. Thank you so far! Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAlmMGbv5p9h9J588RAjg/AJ9n3HGRpjihmhl12IJ35hCZuo3ZyQCggxBt 2DR9ndRyEMxbhdvOqSyaNUU= =SQrB -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Gimp Menu Reorganization
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 05 May 2004 13:47, Sven Neumann wrote: > I'm looking forward to see the results. Now is a really good time for > discussing usability issues. We are willing to do quite some changes > to the user interface for GIMP 2.2. Just a question about that: Where are those usability issues discussed? The Wiki? Here? Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAmNm2bv5p9h9J588RAsOcAKCIdgm39s0rFrDXBDvdCyqgb3s3GwCgiK65 +6clvI+5FyzlhlIjC7D6fvE= =yZaU -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
[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] 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
-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
Re: [Gimp-developer] Need some feedbacks about this plugin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Saturday 22 May 2004 02:19, Nicolas BENOIT wrote: > I am currently trying to write a good documentation, but it isn't that > easy... As I am not a 2D graphist, I just don't know which examples > might be usefull and how the doc should be written. Well, just something that works, brings strange or useful results and is not too complicated. So that you can see at a glance, what's going on. > I thought about templates for formulas, but I didn't add that to the > plugin yet. Yes. Something like that. > What did you try to do first? Well, once I saw all those text fields with letters in it I first changed 'g' to 'g=g+1' It produced an error. > The target 'install-bin' isn't defined... Personnally, I always use the > 'install' target. Well, I guess, I'll try to work this out. IIRC there's a macro for that. But as long as you explain what to do, that should be OK for the development and beta phase. Later I would insert something. I imagine many people using gimp without necessarily having root privileges. And not all of them know (or want/should to know) about those technical details. I think this is the developer's job. Greetings... Stephan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAr3zBbv5p9h9J588RAj2zAKDH5EuyrniTDzKLIShSNyCuzfb+IQCfb87P jHcBPBMozXKFWjU2nDhxr4Y= =I/TF -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
