From: Sven Neumann <[EMAIL PROTECTED]>
Date: 25 May 2004 10:54:00 +0200
Robert L Krawitz <[EMAIL PROTECTED]> writes:
> If we do this right, then we can change libgimpprint to our heart's
> content and the GIMP plugin will go merrily on its way, without ever
> having to be recompiled or relinked. When the GIMP supports 16 bits,
> only the plugin needs to change, and that would be owned by the GIMP.
> If we add color management, then as long as we don't rely on the GIMP
> for any of that there should be no problem. Then when we go to 5.2 or
> even 6.0 or whatever GIMP users shouldn't have to worry about an
I doubt that you can foresee any changes that might be needed in
the future so I am not completely sharing your optimistic view on
this. But in general it seems like the right thing to
do. Nevertheless I'd like to have a look at the proposed
libgimpprint-gtk2 API before it's finalized. Could you please post
a header file here?
Certainly we'll do so if/when we do this (it was a proposal). My hope
is that the GIMP isn't going to have a lot of changes that would
require changes to this hypothetical libgimpprint-gtk2. For example,
if you were to support floating point channel values, the plugin could
convert those to 16-bit unsigned integers.
Robert Krawitz <[EMAIL PROTECTED]>
Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail [EMAIL PROTECTED]
Project lead for Gimp Print -- http://gimp-print.sourceforge.net
"Linux doesn't dictate how I work, I dictate how Linux works."
Gimp-developer mailing list