Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Sven Neumann [EMAIL PROTECTED] writes: Note to the gimp-print developers: You should consider to stop using scanf() and similar locale-dependant functions to read your config files. Setting LC_NUMERIC to C is a workaround but it's rather ugly and easy to forget. What should be used instead (given that Standard C does not have locale objects)? -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] no ppd file usable with gimp2.0pre4?
Sven Neumann [EMAIL PROTECTED] writes: Hi, Roger Leigh [EMAIL PROTECTED] writes: Sven Neumann [EMAIL PROTECTED] writes: Note to the gimp-print developers: You should consider to stop using scanf() and similar locale-dependant functions to read your config files. Setting LC_NUMERIC to C is a workaround but it's rather ugly and easy to forget. What should be used instead (given that Standard C does not have locale objects)? http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-strtod http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-dtostr http://developer.gnome.org/doc/API/2.0/glib/glib-String-Utility-Functions.html#g-ascii-formatd I wish we were able to use Glib :-( -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Displaying image using GTK
Sven Neumann [EMAIL PROTECTED] writes: Hi, [EMAIL PROTECTED] ( Marc) (A.) (Lehmann ) writes: which is a severe shortcoming of the build environment (AFAIK, Msys uses cygwin which is awfully slow due to a large number of reasons). MSYS does not depend on cygwin, BTW. It's entirely standalone. They both have to implement fork() using Windows calls though, which can never be efficient. This sounds like if you had a clue on what is causing the slowliness of running configure on Cygnus. I recently compiled the Blinkenlights software on Windows and noticed this shortcoming as well. I wondered what might be the cause and if there are ways to work around it. Are there any? From what I've observed, it's mostly due to a very slow implementation of fork(). It takes well over a second per fork, so gcc is slow due to forking the compiler, preprocessor, assembler, collect2 etc. configure is even slower (it takes over half an hour to run the gimp-print configure script, c.f. 20 secs on Linux) since it forks over 5000 processes. -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848. Please sign and encrypt your mail. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: PS vs. PDF
Leonard Rosenthol [EMAIL PROTECTED] writes: With a bunch of work, you can use GS to print to Windows - but not to every printer (I don't believe GIMP-print, for example, works on Windows). There's nothing fundamental stopping you. I've built it under Cygwin and run the testsuite, and there were no suprises. It could probably be used as a native Windows driver, if someone cares to write the glue to use libgimpprint and create a nice GUI interface. I've not tested recent 4.3.x releases, so I'm not sure if the loadable family driver modules and embedded mxml XML interpreter function correctly, but there's no reason why they shouldn't. -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: new-xcf [Re: Gimp-developer Digest, Vol10, Issue 18]
Manish Singh [EMAIL PROTECTED] writes: I don't see a compelling argument to use zip/jar. It's complexity that doesn't buy us anything over ar. $ ar t gimp1.2-print_4.2.5-4_i386.deb debian-binary control.tar.gz data.tar.gz The Debian dpkg .deb package format uses an ar archive with gzip compressed members. It's very robust, and it's simple to extract information from any of the members as needed. e.g. $ ar p gimp1.2-print_4.2.5-4_i386.deb control.tar.gz | tar xfz - ./md5sums $ cat md5sums 3698d1f4ce3025bc8c0af73aad39c351 usr/lib/gimp/1.2/plug-ins/print a9e993933c62cf972a07ba60d099a5be usr/share/doc/gimp1.2-print/html/FAQ.html 0f06e25e158d58be369f6c81c74f350f usr/share/doc/gimp1.2-print/html/print-color.png 8af9040e743fdea01d048a9625be3f37 usr/share/doc/gimp1.2-print/html/print-main.png 9bcaba3b091edb324a4e3658d3b4c17b usr/share/doc/gimp1.2-print/html/print-setup.png bdb27f0b9e600cbf067b34d26b62727b usr/share/doc/gimp1.2-print/samples/colorbars4.png cd6014ab378eeebbaee1723b78ef4459 usr/share/doc/gimp1.2-print/samples/colorsweep.png a9e993933c62cf972a07ba60d099a5be usr/share/doc/gimp1.2-print/FAQ.html d41331233e7703ff0c7f365a1f1fa2a4 usr/share/doc/gimp1.2-print/README.Debian 37ae0a31af00c0fa8569104c96927391 usr/share/doc/gimp1.2-print/copyright 9581201d2bf1fc7b5fcf4c3463d79854 usr/share/doc/gimp1.2-print/changelog.gz 7b58392e6bc678907651c89bdb134763 usr/share/doc/gimp1.2-print/README.gz 5fa90d8012eebb8038dd991d46155ff5 usr/share/doc/gimp1.2-print/changelog.Debian.gz -- Roger Leigh Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] + restoring mouse position after use cornernavigation tool
Sven Neumann [EMAIL PROTECTED] writes: I'm not sure if warping the mouse cursor would be an improvement in useability. Usually doing so is considered a bad thing by user interface guidelines. OpenLook on SunOS used to do this by default. It was fast, but took a lot of getting used to. You have to find the cursor after every move, which is annoying. Dropping the mouse cursor where you consider it needed next is doubly annoying if the user wants to do something else (perhaps unrelated to your program). -- Roger Leigh Liberty and Livelihood - Support the Countryside Alliance Printing on GNU/Linux? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] autoconf macro for gimptool
If you write a plugin as a single C file, gimptool can be used to
build and install it. However, things get a little harder when you
want to use make to build a bigger plugin, such as the Print plugin.
You might find the following macros useful, perhaps with a little
tweaking. They are modified versions of macros used in gimp-print.
Just put GIMP_PLUG_IN_DIR in configure.ac, and then you can use
gimp_plug_in_PROGRAMS = myplugin
myplugin_SOURCES = foo.c foo.h bar.c bar.h baz.c baz.h
in a Makefile.am, and use the automake/libtool framework instead of
custom install rules using gimptool (which won't be pretty when using
libtool). You can also use --enable-user-install to install into a
home directory instead. autoconf = 2.50 is required.
Regards,
Roger
begin m4 macros
# This file is part of the GIMP-*- Autoconf -*-
# gimptool support.
# Copyright 2000-2002 Roger Leigh
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program; if not, write to the Free Software
# Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
# 02111-1307, USA.
## Table of Contents:
## 1. User install
## 1. Plug-in directory
## --- ##
## 1. User install ##
## --- ##
# GIMP_PLUG_IN_INSTALL
#
# Install in system or home directory
AC_DEFUN([GIMP_PLUG_IN_INSTALL],
[dnl
AC_MSG_CHECKING([whether to install GIMP plugins in home directory])
AC_ARG_ENABLE([user-install],
[AC_HELP_STRING([--enable-user-install],
[install GIMP plugins in home directory @:@no@:@])],
[case ${enableval} in
yes) USER_INSTALL=yes ; AC_MSG_RESULT([yes]) ;;
no) USER_INSTALL=no ; AC_MSG_RESULT([no]) ;;
*) AC_MSG_RESULT([unknown])
AC_MSG_ERROR([bad value ${enableval} for --enable-user-install])
;;
esac],
[AC_MSG_RESULT([no])
USER_INSTALL=no])
if test x$USER_INSTALL = xyes ; then
PLUG_IN_PATH=bin
else
PLUG_IN_PATH=admin-bin
fi
])
## ##
## 2. Plug-in directory ##
## ##
# GIMP_PLUG_IN_DIR
#
# Locate the GIMP plugin directory using gimptool
AC_DEFUN([GIMP_PLUG_IN_DIR],
[dnl Extract directory using --dry-run and sed
AC_REQUIRE([GIMP_PLUG_IN_INSTALL])
if test x${BUILD_GIMP} = xyes ; then
AC_PATH_PROG(GIMPTOOL, gimptool)
AC_MSG_CHECKING([for GIMP plug-in directory])
# create temporary plug-in to install
touch tmpplugin
chmod 755 tmpplugin
GIMPTOOL_OUTPUT=`$GIMPTOOL --dry-run --install-${PLUG_IN_PATH} tmpplugin`
rm tmpplugin
gimp_plug_indir=`echo $GIMPTOOL_OUTPUT | sed -e 's/.* \(.*\)\/tmpplugin/\1/'`
AC_MSG_RESULT([$gimp_plug_indir])
else
gimp_plug_indir=$libdir/gimp/1.2/plug-ins
fi
AC_SUBST(gimp_plug_indir)
])
end m4 macros
--
Roger Leigh
Liberty and Livelihood - Support the Countryside Alliance
Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/
GPG Public Key: 0x25BFB848 available on public keyservers
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Dependencies between gimp-1.2.4 and gimp-print
On Fri, Jun 21, 2002 at 06:20:57PM +0200, Sven Neumann wrote: I was told that latest versions of gimp-print don't build the gimp plug-in by default and thus do not need depend on gimp to be installed. That is correct. This is not yet in an official release though (it will be in 4.2.2). Regards, Roger -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] glib version question
On Tue, Jan 22, 2002 at 03:10:54PM -0500, Carol Spears wrote: what is a good, generic, quick way to find which version of glib you have installed on your computer? roger@whinlatter:~$ pkg-config --modversion glib 1.2.10 roger@whinlatter:~$ pkg-config --modversion glib-2.0 1.3.11 roger@whinlatter:~$ glib-config --version 1.2.10 -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers msg01813/pgp0.pgp Description: PGP signature
Re: [Gimp-developer] Raphael's edits, was Re: test this howto now
On Mon, Jan 21, 2002 at 12:16:44PM -0800, Jeff Trefftzs wrote: A good Compiling the GIMP from a Tarball HOW-TO seems like a really good idea. I think this outline covers the main points, but certainly could use some rearranging. I hereby offer it up for tweaks and adjustments. This may be useful, but is meant as a followup to the posts about documenting building from CVS. In the gimp-print source, there is a file `doc/README.maintaining' that describes how to use the autotools to build from CVS. It covers how to set up a checked-out CVS (or tarball) tree, and use configure (but that's documented fully in README). It also goes into how all the autotools work together, and how to set up the build scripts manually, or with autogen.sh automatically. Additionally, it describes briefly how to hack configure.in and Makefile.am's. I lost the message about documenting building from CVS, but you might find parts of this useful (there's little point in writing the same thing twice). Some parts are specific to gimp-print, but you can eaily cut them out or modify them. I spotted a couple of typos just now, and I also have an updated copy for autoconf 2.52 and automake 1.5. See: http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/gimp-print/print/doc/README.maintaining?rev=1.8content-type=text/vnd.viewcvs-markup or the source. Regards, Roger -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers msg01799/pgp0.pgp Description: PGP signature
Re: [Gimp-developer] Raphael's edits, was Re: test this howto now
On Mon, Jan 21, 2002 at 10:12:55PM +0100, Sven Neumann wrote: Hi, Roger Leigh [EMAIL PROTECTED] writes: In the gimp-print source, there is a file `doc/README.maintaining' that describes how to use the autotools to build from CVS. It covers how to set up a checked-out CVS (or tarball) tree, and use configure (but that's documented fully in README). It also goes into how all the autotools work together, and how to set up the build scripts manually, or with autogen.sh automatically. Additionally, it describes briefly how to hack configure.in and Makefile.am's. this file is traditionally called HACKING. Is this documented anywhere? I can't see anything about this in the GNU Coding Standards. Thanks, Roger -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers msg01803/pgp0.pgp Description: PGP signature
[Gimp-developer] gimptool and DESTDIR support
Way back in January I submitted a patch to add DESTDIR support to gimptool, primarily for using it in Makefiles, as you can't install a plugin to any location except it's final destination. This prevents installing it into an alternate location, for example when packaging it for Debian. I regard this as a quite serious deficiency in gimptool which limits its usefulness. My patch was applied to the CVS head, but not to the 1.2 branch and now it has been lost now gimptool.in has been replaced with gimptool-1.3.in. Please would you consider the following two patches for inclusion into the GIMP. The first adds DESTDIR support to 1.2 gimptool.in, the second to 1.3 gimptool-1.3.in. The former includes a fix for the manpage too, but there is no manpage in 1.3. I made the patches against the CVS GIMP_1_2_3_PRE2 and HEAD branches. Regards, Roger 1.2 patch: -- diff -urN gimp.orig/gimptool.1.in gimp/gimptool.1.in --- gimp.orig/gimptool.1.in Thu Dec 6 16:55:31 2001 +++ gimp/gimptool.1.in Thu Dec 6 16:53:51 2001 @@ -193,6 +193,9 @@ .B CFLAGS to get the preferred flags to pass to the C compiler for plug-in building. .TP 8 +.B DESTDIR +to add a prefix to the install/uninstall path. +.TP 8 .B LDFLAGS to get the prefered flags for passing to the linker. .TP 8 diff -urN gimp.orig/gimptool.in gimp/gimptool.in --- gimp.orig/gimptool.in Thu Dec 6 16:55:31 2001 +++ gimp/gimptool.inThu Dec 6 16:53:48 2001 @@ -256,7 +256,7 @@ shift if test x$1 != x; then if test -f $install_dir/$1; then - cmd=rm -f $install_dir/$1 + cmd=rm -f $DESTDIR$install_dir/$1 test $quiet = yes || echo $cmd test $donothing = yes || exec $cmd else @@ -272,7 +272,7 @@ shift if test x$1 != x; then if test -r $1; then - cmd=$install_cmd $1 $install_dir/$1 + cmd=$install_cmd $1 $DESTDIR$install_dir/$1 test $quiet = yes || echo $cmd test $donothing = yes || exec $cmd else 1.3 patch: -- diff -urN gimp.orig/gimptool-1.3.in gimp/gimptool-1.3.in --- gimp.orig/gimptool-1.3.in Thu Dec 6 16:59:41 2001 +++ gimp/gimptool-1.3.inThu Dec 6 17:00:24 2001 @@ -244,7 +244,7 @@ shift if test x$1 != x; then if test -f $install_dir/$1; then - cmd=rm -f $install_dir/$1 + cmd=rm -f $DESTDIR$install_dir/$1 test $quiet = yes || echo $cmd test $donothing = yes || exec $cmd else @@ -260,7 +260,7 @@ shift if test x$1 != x; then if test -r $1; then - cmd=$install_cmd $1 $install_dir/$1 + cmd=$install_cmd $1 $DESTDIR$install_dir/$1 test $quiet = yes || echo $cmd test $donothing = yes || exec $cmd else -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ GPG Public Key: 0x25BFB848 available on public keyservers ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Re: [Gimp-print-devel] ANNOUNCE: Gimp-Print 4.1.8
On Thu, Jun 07, 2001 at 10:01:40PM -0400, Robert L Krawitz wrote: 10) The Gimp plugin should now build on systems not using GNU make. Has anyone confirmed this? I never got any reply from the BSD users who had problems (I wanted ones Makefile.in, but he never sent it) and Murray never confirmed that my fixes worked (although I thought they were OK). -- Roger Leigh ** Registration Number: 151826, http://counter.li.org ** Need Epson Stylus Utilities? http://gimp-print.sourceforge.net/ For GPG Public Key: finger [EMAIL PROTECTED] or see public keyservers. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
