gimp-print-devel

Re: [Gimp-print-devel] Tonight's stuff

[Michael N. <mit...@cs...>]

"S. Miller" wrote:
> 
> Robert L Krawitz wrote:
> >
> > Karl tells me that the new print.c won't compile even against gimp
> > 1.1.11.  That's bad.  I'm going to leave it there for now, but
> > probably pull it tomorrow night or so.  Try to compile it, and let me
> > know the results and what gimp version you're running.
> >
> It also failed against 1.1.15.

Hi all,

just to introduce myself to the list:

I'm the evil guy (TM) who hacked the gimp-specific ui stuff into gimp-print
which makes it impossible to compile against anything older than 1.1.17.

However, it seems that Steve has already started separating the ui out
of print.c, so with a little work we should be able to solve this
in a way that it compiles with both latest cvs gimp as well as with
older 1.1.x or even 1.0 versions.

bye,
--Mitch

[Gimp-print-devel] Re: Opinions

[Dave H. <da...@mi...>]

Suprise! It no longer compiles with Gimp 1.0!

gcc -O6 -funroll-all-loops -Wall -I/usr/local/include
-I/usr/local/glib/include -I/usr/lib/glib/include
-I/usr/X11R6/include  -DLPC_COMMAND=\"/usr/sbin/lpc\"
-DLPR_COMMAND=\"/usr/bin/lpr\" -DLOCALEDIR=\"/usr/local/share/locale\"
-c print.c -o print.o
print.c: In function `do_print_dialog':
print.c:772: warning: implicit declaration of function `gimp_dialog_new'
print.c:773: `gimp_plugin_help_func' undeclared (first use in this
function)
print.c:773: (Each undeclared identifier is reported only once
print.c:773: for each function it appears in.)
print.c:786: warning: assignment makes pointer from integer without a
cast
print.c:851: warning: type mismatch in implicit declaration for built-in
function `fabs'
print.c:856: warning: implicit declaration of function
`gimp_table_attach_aligned'
print.c:954: warning: implicit declaration of function
`gimp_option_menu_new'
print.c:963: warning: assignment makes pointer from integer without a
cast
print.c:1049: warning: implicit declaration of function
`gimp_scale_entry_new'
print.c:1053: warning: assignment makes pointer from integer without a
cast
print.c:1062: warning: assignment makes pointer from integer without a
cast
print.c:1119: warning: assignment makes pointer from integer without a
cast
print.c:1133: warning: assignment makes pointer from integer without a
cast
print.c:1147: warning: assignment makes pointer from integer without a
cast
print.c:1161: warning: assignment makes pointer from integer without a
cast
print.c:1175: warning: assignment makes pointer from integer without a
cast
print.c:1189: warning: assignment makes pointer from integer without a
cast
print.c:1203: warning: assignment makes pointer from integer without a
cast
print.c:1217: warning: assignment makes pointer from integer without a
cast
print.c:1278: warning: assignment makes pointer from integer without a
cast
make: *** [print.o] Error 1

I'll look at this tomorrow and get the #ifdef's out again!!

Dave

-- 
Dave Hill, Kempston, Bedford UK		da...@mi...
Sicth munce ago, I cutn't evun spel enjuneer, and now I are one!

Re: [Gimp-print-devel] Tonight's stuff

[S. M. <sm...@rn...>]

Robert L Krawitz wrote:
> 
> Karl tells me that the new print.c won't compile even against gimp
> 1.1.11.  That's bad.  I'm going to leave it there for now, but
> probably pull it tomorrow night or so.  Try to compile it, and let me
> know the results and what gimp version you're running.
> 
It also failed against 1.1.15.

Steve

-----------------------------------------
Just because I have a short attention span
doesn't mean I
------------------------------------------

[Gimp-print-devel] Epson 1200 for sale

[Robert L K. <rl...@al...>]

Might just be tempting, except that I hardly need another printer
sitting around...although doubtless it would help get the 1200/740/750
stuff going better.

Path: newsflash!news-feed1.tiac.net!news.maxwell.syr.edu!europa.netcrusader.net!24.30.200.2!cyclone-east.rr.com!news.rr.com!news-east.rr.com!portc05.blue.aol.com!audrey04.news.aol.com!not-for-mail
From: spo...@ao... (SportzPhoto)
Newsgroups: rec.photo.marketplace
Subject: FS Epson 1200 Printer
Lines: 5
NNTP-Posting-Host: ladder07.news.aol.com
X-Admin: ne...@ao...
Date: 28 Feb 2000 01:52:36 GMT
Organization: AOL http://www.aol.com
Message-ID: <200...@ng...>
Xref: newsflash rec.photo.marketplace:203719

Like new condition, outstanding high resolution prints up to 11x17. Parallel
or USB connectivity, includes original box, manuals, software and 2 brand
new unopened Ink cartridges.

                                      250.00 plus shipping

Re: [Gimp-print-devel] Tonight's stuff

[Karl H. K. <kh...@kh...>]

On Sun, Feb 27, 2000 at 08:44:21PM -0500, Robert L Krawitz wrote:
> Karl tells me that the new print.c won't compile even against gimp
> 1.1.11.  That's bad.  I'm going to leave it there for now, but
> probably pull it tomorrow night or so.  Try to compile it, and let me
> know the results and what gimp version you're running.

I just upgraded to 1.1.17 and it now compiles fine.


--=20
Karl Heinz Kremer                                      kh...@kh...
                                                http://www.khk.net

[Gimp-print-devel] HP DeskJet 690 C

[David M. <arc...@db...>]

This message was sent from Geocrawler.com by "David Monniaux" <mon...@ar...>
Be sure to reply to that address.

My mother has an HP DeskJet 690 C. Running Linux
and Gimp on her machine, I tried two methods to
print color images:
- output PostScript Level 2 and run it through
Ghostscript
- use Gimp-Print's DeskJet 6xx driver.

Neither of these solutions is satisfactory. Black
and white printing works more or less, but colors
come out wrong (also, the Ghostscript driver
drenchs the paper in ink sometimes).

It is difficult for me to conduct extensive
trials, since this is not my printer. Has any
improvement been done on this driver ?


Geocrawler.com - The Knowledge Archive

[Gimp-print-devel] Tonight's stuff

[Robert L K. <rl...@al...>]

I've checked in some stuff that might improve print quality at 1440
dpi (reduced grain).  It should improve print quality for the
740/900/750/1200 printers in all softweave modes.

The new stuff may be flaky if density is set too high, and it seems to
be a bit erratic at 1440x720 two-pass.  Basically, I've changed the
way it does oversampling; previously it simply dropped every other
dot, but what it does now is reduce density by 1/2.  This isn't quite
the same thing (particularly on the 6-color printers), due to some
nonlinear stuff going on in there.

As for the new printers, the code was doing its
eliminate-every-other-dot thing in 720 dpi softweave, due to the fact
that the printed spacing is 1/360".  That's simply a bug.  The new
code may, however, improve handling of variable dot size printers in
general, since the dots might be small enough to usefully achieve
1/1440" spacing.

Karl tells me that the new print.c won't compile even against gimp
1.1.11.  That's bad.  I'm going to leave it there for now, but
probably pull it tomorrow night or so.  Try to compile it, and let me
know the results and what gimp version you're running.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Re: [Gimp-print-devel] print.c does not compile

[Robert L K. <rl...@al...>]

   Date: Sun, 27 Feb 2000 18:32:46 -0500
   From: Karl Heinz Kremer <kh...@kh...>

   The version of print.c that was checked in just minutes ago does not=20
   compile. I'm getting the following error messages:

Is this compiled against Gimp 1.0?  That doesn't surprise me.  Revert
back to 1.67 for now.  We'll probably drop this new one.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

[Gimp-print-devel] Variable dot size Epson printers (740, 900, 750, 1200)

[Robert L K. <rl...@al...>]

Has anyone using any of these printers noticed anomalously light
output that cannot be corrected by increasing density with any of
these printers?

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

[Gimp-print-devel] print.c does not compile

[Karl H. K. <kh...@kh...>]

The version of print.c that was checked in just minutes ago does not=20
compile. I'm getting the following error messages:

print.c: In function `query':
print.c:358: warning: statement with no effect
print.c:358: warning: statement with no effect
print.c: In function `run':
print.c:423: warning: statement with no effect
print.c:423: warning: statement with no effect
print.c:456: `STATUS_CANCEL' undeclared (first use in this function)
print.c:456: (Each undeclared identifier is reported only once
print.c:456: for each function it appears in.)
print.c: In function `do_print_dialog':
print.c:772: warning: implicit declaration of function `gimp_dialog_new'
print.c:773: `gimp_plugin_help_func' undeclared (first use in this function)
print.c:786: warning: assignment makes pointer from integer without a cast
print.c:856: warning: implicit declaration of function `gimp_table_attach_a=
ligned'
print.c:954: warning: implicit declaration of function `gimp_option_menu_ne=
w'
print.c:963: warning: assignment makes pointer from integer without a cast
print.c:1049: warning: implicit declaration of function `gimp_scale_entry_n=
ew'
print.c:1053: warning: assignment makes pointer from integer without a cast
print.c:1062: warning: assignment makes pointer from integer without a cast
print.c:1119: warning: assignment makes pointer from integer without a cast
print.c:1133: warning: assignment makes pointer from integer without a cast
print.c:1147: warning: assignment makes pointer from integer without a cast
print.c:1161: warning: assignment makes pointer from integer without a cast
print.c:1175: warning: assignment makes pointer from integer without a cast
print.c:1189: warning: assignment makes pointer from integer without a cast
print.c:1203: warning: assignment makes pointer from integer without a cast
print.c:1217: warning: assignment makes pointer from integer without a cast
print.c:1278: warning: assignment makes pointer from integer without a cast
print.c: In function `get_system_printers':
print.c:2831: warning: unused variable `name'
make: *** [print.o] Error 1                              =20


--=20
Karl Heinz Kremer                                      kh...@kh...
                                                http://www.khk.net

Re: [Gimp-print-devel] Random Success...

[Robert L K. <rl...@al...>]

   Date: Sun, 27 Feb 2000 14:32:53 -0500
   From: Karl Heinz Kremer <kh...@kh...>

   On Sun, Feb 27, 2000 at 01:21:12PM -0500, Robert L Krawitz wrote:
   > When it did finally work, did you then powercycle it to verify that it
   > still worked?

   Of course I did... I also restarted Gimp, did some heavy compiling
   to fill the memory with random data, rebooted the machine and it
   just worked :-( I am pretty sure that it's not the printer, I suspect
   some memory problem, or not correctly initialized data. I run=20
   gcc with extensive warnings and came up with some problems that
   probably should be fixed, but I doubt that this would behave=20
   so random. I've created a patch file that's attached to this mail.

Well, we should fix all the warnings that we can, certainly, and those
look fairly innocent.  I presume you've already ensured that both the
ones that worked and the ones that didn't were the same size, printed
on the same place on the paper...

   On a different subject: My cat just configured some key shortcuts
   by walking over the keyboard :-)

Re: [Gimp-print-devel] Random Success...

[Karl H. K. <kh...@kh...>]

On Sun, Feb 27, 2000 at 01:21:12PM -0500, Robert L Krawitz wrote:
> When it did finally work, did you then powercycle it to verify that it
> still worked?

Of course I did... I also restarted Gimp, did some heavy compiling
to fill the memory with random data, rebooted the machine and it
just worked :-( I am pretty sure that it's not the printer, I suspect
some memory problem, or not correctly initialized data. I run 
gcc with extensive warnings and came up with some problems that
probably should be fixed, but I doubt that this would behave 
so random. I've created a patch file that's attached to this mail.

On a different subject: My cat just configured some key shortcuts
by walking over the keyboard :-)

Karl Heinz
-- 
Karl Heinz Kremer                                      kh...@kh...
                                                http://www.khk.net

Re: [Gimp-print-devel] Can Stylus print closer than 23mm to top of page?

[Robert L K. <rl...@al...>]

   Date: Sun, 27 Feb 2000 23:08:09 +0800
   From: Nick Urbanik <ni...@vt...>
   CC: gim...@li...

   As you say, it's really slow, so I downloaded and compiled 3.1, excited by
   the prospect of support for our Epson 440, and by begin able to print an
   A4 photo in less than 2.5 hours!!!

Could you try to print a much smaller image, at the top left of the
page (top = 0, left = 0)?  Say, something about 2"x2".

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Re: [Gimp-print-devel] opinions

[Robert L K. <rl...@al...>]

OK, I'm putting in the experimental print.c (version 1.68) for now.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Re: [Gimp-print-devel] opinions

[Robert L K. <rl...@al...>]

   From: sh...@al...
   Date: Mon, 28 Feb 2000 02:07:49 +0900

   > Somebody in the core Gimp team made massive changes to the dialog box
   > (in 3.0!).

   Mmm.  I don't like it when someone drives over my part of the noosphere
   either.

Turns out that it was a case of miscommunication here.  The person who
actually made the changes thought I had finished with 3.0, and so he'd
be free to make changes.  I still don't think he should have done that
without discussing it with me.

   > It's generally an improvement, although I have some
   > quibbles over it.

   That's the worst kind.  Too good to ignore, but, not as good as if you'd
   done it yourself.  At least, from your point of view.

Well, the short term issue is that the Gimp's sliders aren't as good
as GTK's.

   > I think that the 1.0 compatibility is important, since 1.2 is not out
   > yet, and users of 1.0 really need a better printing solution than what
   > they presently have.

   We won't know if it's compatible or not until someone actually tries it,
   which is more likely to happen if it's checked in.

OK, I'll put it in.  We'll back it out if there's a problem.

   > In any event, this kind of fixed dialog is hardly what I envision, and
   > when Steve last commented it sounded like he had some good ideas about
   > cleaning up the dialog and in general improving the situation.

   Can he implement them on top of the new version?

Same issue.  Steve's working on the GUI and shouldn't have the rug
yanked out from under him.  The problem is that they're more than just
cosmetic changes;

Re: [Gimp-print-devel] Random Success...

[Robert L K. <rl...@al...>]

   Date: Sun, 27 Feb 2000 11:07:02 -0500
   From: Karl Heinz Kremer <kh...@kh...>

   I just tried to run a test using all print modes on my stc740. The
   first image I tried caused the "blank page" problem even though I
   knew that the printer was doing fine yesterday. So I assumed that
   it must have been the small changes Robert checked in since then.
   Therefore I'm going back to the version I had yesterday and tried
   it again withe same result. It did not work with the test image
   that I'm always using. So I loaded the colors.tif file and tried
   to print this: Success. It worked.

   Then I loaded the penguin again and it printed fine. Where are we
   using /dev/random to determine the success or failure of a print?

Grr.  I REALLY don't like this kind of stuff.

   BTW: I did powercycle the printer a few times when it was not
   working just to make sure that none of my other jobs (ghostscript
   with uniprint driver) left the printer in a funny state.

When it did finally work, did you then powercycle it to verify that it
still worked?

Something about this gives me the willies, especially with those magic
commands whose function we don't understand.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Re: [Gimp-print-devel] opinions

[<sh...@al...>]

> Somebody in the core Gimp team made massive changes to the dialog box
> (in 3.0!).

Mmm.  I don't like it when someone drives over my part of the noosphere
either.

> It's generally an improvement, although I have some
> quibbles over it.

That's the worst kind.  Too good to ignore, but, not as good as if you'd
done it yourself.  At least, from your point of view.

> I've made the changes in my sandbox.  I'm not at all confident that
> this will compile under Gimp 1.0 any more.  So my question is, should
> I check the changes in or not (Steve, would you like to review them
> first)?

Changes are pretty easy to back out of CVS.  Even after further revisions are
made.  Why not?

> I think that the 1.0 compatibility is important, since 1.2 is not out
> yet, and users of 1.0 really need a better printing solution than what
> they presently have.

We won't know if it's compatible or not until someone actually tries it,
which is more likely to happen if it's checked in.
 
> In any event, this kind of fixed dialog is hardly what I envision, and
> when Steve last commented it sounded like he had some good ideas about
> cleaning up the dialog and in general improving the situation.

Can he implement them on top of the new version?

Eric

Re: [Gimp-print-devel] Bug in unprint.c

[<sh...@al...>]

> There is a bug in the current version of unprint.c: When the
> UNPRINT environment variable is not defined the software runs
> into a segfault. Apply this patch and it will work:

Actually, I fixed that about 3 hours ago, but I hadn't committed it yet
because I had other changes in progress which (temporarily) introduced
far more serious bugs.  I'll commit a new version in a few minutes.

Eric

Re: [Gimp-print-devel] Random Success...

[Karl H. K. <kh...@kh...>]

=2E.. I forgot to mention that this was with softweave 720dpi and=20
variable dot size.=20

I also forgot to mention that the new code that I compiled and
installed while gimp was still running also works once I got it
to work with one image.

Karl Heinz

--=20
Karl Heinz Kremer                                      kh...@kh...
                                                http://www.khk.net

[Gimp-print-devel] Random Success...

[Karl H. K. <kh...@kh...>]

I think I said this before: I don't understand the weird interactions
between the moon phase, the outside temperature, the image contents
and my successrate when printing images via the plugin:

I just tried to run a test using all print modes on my stc740. The
first image I tried caused the "blank page" problem even though I=20
knew that the printer was doing fine yesterday. So I assumed that
it must have been the small changes Robert checked in since then.
Therefore I'm going back to the version I had yesterday and tried
it again withe same result. It did not work with the test image
that I'm always using. So I loaded the colors.tif file and tried
to print this: Success. It worked.

Then I loaded the penguin again and it printed fine. Where are we
using /dev/random to determine the success or failure of a print?

BTW: I did powercycle the printer a few times when it was not
working just to make sure that none of my other jobs (ghostscript
with uniprint driver) left the printer in a funny state.=20

Karl Heinz
--=20
Karl Heinz Kremer                                      kh...@kh...
                                                http://www.khk.net

Re: [Gimp-print-devel] Can Stylus print closer than 23mm to top of page?

[Robert L K. <rl...@al...>]

   Date: Sun, 27 Feb 2000 23:08:09 +0800
   From: Nick Urbanik <ni...@vt...>

   As you say, it's really slow, so I downloaded and compiled 3.1, excited by
   the prospect of support for our Epson 440, and by begin able to print an
   A4 photo in less than 2.5 hours!!!

   However, I've been singularly unsuccessful.
   System: Red Hat 6.1 with all updates, now gimp 1.0 removed, gimp 1.1.17
   working, PIII.

   When compiling it together with gimp 1.1.17, the make stopped at print.
   Note that print is a link to print-3.1.0 (is that okay?)

It's intended to build standalone.  You should simply unpack it, run
./configure, and make.

   I ran ./configure in print, then make, and it compiled.  I tried printing
   with 440 driver: no printer recognised, only File (the LPC_DEF and
   LPR_DEF names were undefined, as you see below)
   So I tried printing to file.  Never stopped.  Hmm, this has been such a
   long saga, I'm getting a bit misty on the order of my misfortune.  A more
   recent try resulted in feeding many pages through the printer, with one
   page getting a line or two of coloured text.  I was using the 440 printer
   with high quality setting.

   Next, I edited my makefile, added the stuff for the printer that was
   missing:

That's not the right place to fix this; we need to somehow fix it in
configure.in.

   It compiled.  I tried the 600 driver with 720 dpi highest quality.  The
   printer just fed many pages through with out any printing.

The 600 driver will not work.  You will need to use the 440 driver.

   I have 6000 photos of our lovely baby, and I'd love to be able to print
   them in less than 2.5 hours.  I've compiled 3.09, and am printing with the
   600 driver on 720 dpi Microweave.  It works, but vvvvvvveeeerrrrrrryyyyyy
   sssssssssllllllllllllllllllllllllllllooooooooooooooooowwwwwwwwwwwwwwwwwllllllllllllllyyyyyyyyyyyyy.

   Sorry to be stuck, but I'd really appreciate any pointers on how to get
   3.1 or stuff from CVS working, will try any suggestions.  I will feed back
   whatever works.

Try downloading the CVS stuff.  There's a little problem with most
Gimp installations, though.  You need to make sure that you have a
gimp.m4 in /usr/local/share/aclocal (or /usr/share/aclocal on some
systems); the Gimp doesn't always install it properly (it is in your
Gimp distribution).  You need to edit it according to the directions
in the README file.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

Re: [Gimp-print-devel] Can Stylus print closer than 23mm to top of page?

[Nick U. <ni...@vt...>]

Robert L Krawitz wrote:

>    Date: Sat, 19 Feb 2000 16:28:42 +0800
>    From: Nick Urbanik <ni...@vt...>
>
>    Robert L Krawitz wrote:
>
>    > Any suggestions on how to persuade my printer
>    >    to start printing closer to the top of the page?
>    >
>    > Are you using one of the softweave modes?  There's a known problem
>    > with that; the page edges aren't being calculated correctly.
>
>    I'm using the 720 dpi Microweave mode.  Is that a softweave mode?
>    What do you suggest I do?  Where do I start?  I'm using version
>    3.05.
>
> No the (very slow) microweave mode is not a softweave mode.  Do you
> mean that the printer feeds 23 mm before starting to print?

Yes.

As you say, it's really slow, so I downloaded and compiled 3.1, excited by
the prospect of support for our Epson 440, and by begin able to print an
A4 photo in less than 2.5 hours!!!

However, I've been singularly unsuccessful.
System: Red Hat 6.1 with all updates, now gimp 1.0 removed, gimp 1.1.17
working, PIII.

When compiling it together with gimp 1.1.17, the make stopped at print.
Note that print is a link to print-3.1.0 (is that okay?)

mkdir .libs
gcc -g -O2 -Wall -o .libs/pagecurl pagecurl.o
../../libgimp/.libs/libgimpui.so -L/usr/lib -L/usr/X11R6/lib -lgtk -lgdk
-lgmodule -lglib -ldl -lXext -lX11 -lm ../../libgimp/.libs/libgimp.so
-lglib -lm -L/usr/lib -L/usr/X11R6/lib -lgtk -lgdk -rdynamic -lgmodule
-lglib -ldl -lXext -lX11 -lm -Wl,--rpath -Wl,/usr/local/lib
creating pagecurl
make[3]: Leaving directory `/home/gimp-1.1.17/plug-ins/pagecurl'
Making all in print
make[3]: Entering directory `/home/gimp-1.1.17/plug-ins/print-3.1.0'
cd . && aclocal
aclocal: configure.in: 12: macro `AM_PATH_GIMP' not found in library
make[3]: *** [../../aclocal.m4] Error 1
make[3]: Leaving directory `/home/gimp-1.1.17/plug-ins/print-3.1.0'
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory `/home/gimp-1.1.17/plug-ins'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gimp-1.1.17'
make: *** [all-recursive-am] Error 2

I ran ./configure in print, then make, and it compiled.  I tried printing
with 440 driver: no printer recognised, only File (the LPC_DEF and
LPR_DEF names were undefined, as you see below)
So I tried printing to file.  Never stopped.  Hmm, this has been such a
long saga, I'm getting a bit misty on the order of my misfortune.  A more
recent try resulted in feeding many pages through the printer, with one
page getting a line or two of coloured text.  I was using the 440 printer
with high quality setting.

Next, I edited my makefile, added the stuff for the printer that was
missing:

1449 # diff -u Makefile~ Makefile
--- Makefile~   Sun Feb 27 21:35:14 2000
+++ Makefile    Sun Feb 27 21:46:55 2000
@@ -65,8 +65,8 @@
 GIMP_LIBS = -L/usr/local/lib -lgimpui -lgimp -L/usr/lib -L/usr/X11R6/lib
-lgtk -lgdk -rdynamic -lgmodule -lglib -ldl -lXext -lX11 -lm
 GIMP_LIBS_NOUI = -L/usr/local/lib -lgimp -L/usr/lib -lglib
 LN_S = ln -s
-LPC_DEF =
-LPR_DEF =
+LPC_DEF = -DLPC_COMMAND=\"/usr/sbin/lpc\"
+LPR_DEF = -DLPR_COMMAND=\"/usr/bin/lpr\"
 LPSTAT_DEF =
 LP_DEF =
 MAKEINFO = makeinfo
@@ -90,7 +90,7 @@
 INCLUDES =     -I$(top_srcdir)
$(GIMP_CFLAGS)         -I$(includedir)


-AM_CPPFLAGS =          -DLOCALEDIR=\""$(localedir)"\"          -Wall
+AM_CPPFLAGS =          -DLOCALEDIR=\""$(localedir)"\"
-Wall          -DLPR_COMMAND=\"/usr/bin/lpr\"
-DLPC_COMMAND=\"/usr/sbin/lpc\"


 print_LDADD = $(GIMP_LIBS)
@@ -127,11 +127,11 @@
 print-ps.o print-util.o print.o
 print_DEPENDENCIES =
 print_LDFLAGS =
-CXXFLAGS = -g -O2
+CXXFLAGS = -g -O2 -Wall
 CXXCOMPILE = $(CXX) $(DEFS) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS)
$(AM_CXXFLAGS) $(CXXFLAGS)
 CXXLD = $(CXX)
 CXXLINK = $(CXXLD) $(AM_CXXFLAGS) $(CXXFLAGS) $(LDFLAGS) -o $@
-CFLAGS = -g -O2
+CFLAGS = -g -O2 -Wall
 COMPILE = $(CC) $(DEFS) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS)
$(AM_CFLAGS) $(CFLAGS)
 CCLD = $(CC)
 LINK = $(CCLD) $(AM_CFLAGS) $(CFLAGS) $(LDFLAGS) -o $@

It compiled.  I tried the 600 driver with 720 dpi highest quality.  The
printer just fed many pages through with out any printing.

I have 6000 photos of our lovely baby, and I'd love to be able to print
them in less than 2.5 hours.  I've compiled 3.09, and am printing with the
600 driver on 720 dpi Microweave.  It works, but vvvvvvveeeerrrrrrryyyyyy
sssssssssllllllllllllllllllllllllllllooooooooooooooooowwwwwwwwwwwwwwwwwllllllllllllllyyyyyyyyyyyyy.

Sorry to be stuck, but I'd really appreciate any pointers on how to get
3.1 or stuff from CVS working, will try any suggestions.  I will feed back
whatever works.

--
Nick Urbanik, Dept. of Electrical & Communications Engineering
Hong Kong Institute of Vocational Education (Tsing Yi)
email: ni...@vt..., ni...@io...
Tel:   (852) 2436 8660, (825) 2436 8492   Fax: (852) 2436 8643
pgp ID: 7529555D fingerprint: 53 B6 6D 73 52 EE 1F EE EC F8 21 98 45 1C 23 7B

[Gimp-print-devel] Bug in unprint.c

[Karl H. K. <kh...@kh...>]

There is a bug in the current version of unprint.c: When the
UNPRINT environment variable is not defined the software runs
into a segfault. Apply this patch and it will work:

diff -u -r1.36 unprint.c
--- unprint.c   2000/02/24 13:28:23     1.36
+++ unprint.c   2000/02/27 14:54:17
@@ -1112,7 +1112,7 @@
     pstate.nozzles=3D96;

     UNPRINT=3D getenv("UNPRINT");
-    if (!strcmp(UNPRINT,"canon")) {
+    if (UNPRINT !=3D NULL && !strcmp(UNPRINT,"canon")) {
       pstate.extraskip=3D1;
       parse_canon(fp_r);
     } else {=20

This is a very common problem: strcmp() can not handle NULL
pointers. I usually check all environement variables that a
program uses during startup and set char * variables that I=20
then use. This makes sure that all variables are initialized
to at least an empty string.

Karl Heinz
--=20
Karl Heinz Kremer                                      kh...@kh...
                                                http://www.khk.net

[Gimp-print-devel] opinions

[Robert L K. <rl...@al...>]

Somebody in the core Gimp team made massive changes to the dialog box
(in 3.0!).  It's generally an improvement, although I have some
quibbles over it.  In any event, I'm less than thrilled that I wasn't
notified that this was happening, and actually I was asked about it
beforehand and I replied that I preferred if the person involved would
work with Steve on this.  In the event, that didn't happen.  So far I
haven't heard back from any of the parties involved.  As you can
imagine, I'm none too thrilled about this.  I'd rather that the person
who did this join our group, work with Steve, and work on sharing
improvements between 3.1 and 3.0.

I've made the changes in my sandbox.  I'm not at all confident that
this will compile under Gimp 1.0 any more.  So my question is, should
I check the changes in or not (Steve, would you like to review them
first)?  They are all in print.c, although they're hardly localized.
I think that the 1.0 compatibility is important, since 1.2 is not out
yet, and users of 1.0 really need a better printing solution than what
they presently have.

In any event, this kind of fixed dialog is hardly what I envision, and
when Steve last commented it sounded like he had some good ideas about
cleaning up the dialog and in general improving the situation.  I'm
not interested in a turf battle over this, although I think it would
have been polite to submit the changes in the form of a patch and ask
my opinion first, and given that I had specifically said that I wanted
anyone doing this to work with Steve, I'm disappointed.

(I have my own issues with the Gimp's release engineering -- if
they're in a feature freeze to the point that they're refusing a new
file format, why are they so eager for minor interface improvements to
the print plugin anyway?  All of this is simply going to delay 1.2,
which means that it will be all the more necessary for us to push
ahead with new printers and other stuff that the Gimp folks don't seem
to care much about.)

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton

[Gimp-print-devel] New stuff

[Robert L K. <rl...@al...>]

I added a center button (to center the image on the page) and
activated the right and bottom entry boxes.  I also changed the
precision to 2 places after the decimal, since we're using integer
points internally and .001" is misleading.

Also, I took another swing at the Epson positioning code.  Maybe it
will work correctly now in the Ghostscript driver.  It's certainly
less convoluted.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton