Gutenprint and the Common Printing Dialog

View: New views
12 Messages — Rating Filter:   Alert me  

Gutenprint and the Common Printing Dialog

by Till Kamppeter-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

to make printing easier for the user we are developing a new Common
Printing Dialog at OpenPrinting. It should be provided by the desktop
environment and used by all applications, so that if a user knows how to
print with application A he also knows how to print with application B.
For the dialog user interface there is also a used a design from
OpenUsability. See

https://www.linuxfoundation.org/en/OpenPrinting/CommonPrintingDialog

and the pages linked from there, especially

http://www.mmiworks.net/eng/publications/labels/openPrinting.html

To make the printer drivers getting the best out of the dialog's
functionality we have put together a set of PPD file extensions with
which the driver developer can control the way how options appear on the
dialog.

As Gutenprint has very many options it is expecially important for it to
present them the right way in the dialog. The extensions allow
multi-language-internationalized PPDs, numerical options (int, float)
being shown as true numerical options, option/choice icons, option tags
(which categories does and option belong to? With which keywords one
would search for that option?), and even hints to tell the dialog which
widgets it should use for a particular option.

And these extensions are not a completely new specification. As far as
possible we use PPD extensions from CUPS, especially the Globalized PPDs
and the Custom Options.

The specifications for the PPD extensions and the Common Printing Dialog
are agreed on with printer manufacturers and the Common Printing Dialog
will soon be added to the desktop environments (the implementation work
is currently done by two Google Summer of Code students). So I highly
recommend that Gutenprint adopts the PPD extensions, at least for the
more commonly used CUPS raster driver. Having the extensions in use will
not break anything, Old dialogs will simply ignore them.

    Till

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Robert Krawitz-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

   Date: Tue, 22 Jul 2008 16:45:53 +0200
   From: Till Kamppeter <till.kamppeter@...>

   To make the printer drivers getting the best out of the dialog's
   functionality we have put together a set of PPD file extensions
   with which the driver developer can control the way how options
   appear on the dialog.

   As Gutenprint has very many options it is expecially important for
   it to present them the right way in the dialog. The extensions
   allow multi-language-internationalized PPDs, numerical options
   (int, float) being shown as true numerical options, option/choice
   icons, option tags (which categories does and option belong to?
   With which keywords one would search for that option?), and even
   hints to tell the dialog which widgets it should use for a
   particular option.

We've supported numerical options for a while, and Mike and I are
debugging the multi-language PPD files right now.  What are the other
things?  They may not be hard to implement.

   And these extensions are not a completely new specification. As far
   as possible we use PPD extensions from CUPS, especially the
   Globalized PPDs and the Custom Options.

   The specifications for the PPD extensions and the Common Printing
   Dialog are agreed on with printer manufacturers and the Common
   Printing Dialog will soon be added to the desktop environments (the
   implementation work is currently done by two Google Summer of Code
   students). So I highly recommend that Gutenprint adopts the PPD
   extensions, at least for the more commonly used CUPS raster
   driver. Having the extensions in use will not break anything, Old
   dialogs will simply ignore them.

--
Robert Krawitz                                     <rlk@...>

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

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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Till Kamppeter-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Robert Krawitz wrote:
> We've supported numerical options for a while, and Mike and I are
> debugging the multi-language PPD files right now.  What are the other
> things?  They may not be hard to implement.
>

Great, what we still need are at least option tags and Quick Preset buttons.

Note that the keywords for the Quick Preset buttons in the specs will
probably change, to sync with the CUPS PPD specs.

    Till

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Robert Krawitz-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

   Date: Wed, 23 Jul 2008 11:06:10 +0200
   From: Till Kamppeter <till.kamppeter@...>

   Robert Krawitz wrote:
   > We've supported numerical options for a while, and Mike and I are
   > debugging the multi-language PPD files right now.  What are the other
   > things?  They may not be hard to implement.

   Great, what we still need are at least option tags and Quick Preset buttons.

   Note that the keywords for the Quick Preset buttons in the specs will
   probably change, to sync with the CUPS PPD specs.

Can you give me the specs (or do you want to take a cut at it yourself)?

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Michael R Sweet :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Robert Krawitz wrote:

>    Date: Wed, 23 Jul 2008 11:06:10 +0200
>    From: Till Kamppeter <till.kamppeter@...>
>
>    Robert Krawitz wrote:
>    > We've supported numerical options for a while, and Mike and I are
>    > debugging the multi-language PPD files right now.  What are the other
>    > things?  They may not be hard to implement.
>
>    Great, what we still need are at least option tags and Quick Preset buttons.
>
>    Note that the keywords for the Quick Preset buttons in the specs will
>    probably change, to sync with the CUPS PPD specs.
>
> Can you give me the specs (or do you want to take a cut at it yourself)?

For presets:

     http://www.cups.org/documentation.php/sped-ppd.html#APPrinterPreset

for everything else:

     https://www.linuxfoundation.org/en/OpenPrinting/PPDExtensions

--
______________________________________________________________________
Michael R Sweet                        Senior Printing System Engineer

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Till Kamppeter-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Michael R Sweet wrote:

> Robert Krawitz wrote:
>>    Date: Wed, 23 Jul 2008 11:06:10 +0200
>>    From: Till Kamppeter <till.kamppeter@...>
>>
>>    Robert Krawitz wrote:
>>    > We've supported numerical options for a while, and Mike and I are
>>    > debugging the multi-language PPD files right now.  What are the
>> other
>>    > things?  They may not be hard to implement.
>>
>>    Great, what we still need are at least option tags and Quick Preset
>> buttons.
>>
>>    Note that the keywords for the Quick Preset buttons in the specs
>> will    probably change, to sync with the CUPS PPD specs.
>>
>> Can you give me the specs (or do you want to take a cut at it yourself)?
>
> For presets:
>
>     http://www.cups.org/documentation.php/sped-ppd.html#APPrinterPreset
>
> for everything else:
>
>     https://www.linuxfoundation.org/en/OpenPrinting/PPDExtensions
>

Robert, I will update the part about the Quick Presets in my specs to
use the *APPrinterPreset keyword as described on
http://www.cups.org/documentation.php/sped-ppd.html#APPrinterPreset. For
the time being use only "*<option> <value>" items in the presets to let
the buttons appear with all print jobs, as for now the applications do
not supply document type information.

    Till

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Robert Krawitz-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

   Date: Wed, 23 Jul 2008 18:50:29 +0200
   From: Till Kamppeter <till.kamppeter@...>
   MIME-Version: 1.0
   CC: Michael R Sweet <msweet@...>, gimp-print-devel@...
   Content-Type: text/plain; charset=UTF-8; format=flowed

   Michael R Sweet wrote:
   > Robert Krawitz wrote:
   >>    Date: Wed, 23 Jul 2008 11:06:10 +0200
   >>    From: Till Kamppeter <till.kamppeter@...>
   >>
   >>    Robert Krawitz wrote:
   >>    > We've supported numerical options for a while, and Mike and I are
   >>    > debugging the multi-language PPD files right now.  What are the
   >> other
   >>    > things?  They may not be hard to implement.
   >>
   >>    Great, what we still need are at least option tags and Quick Preset
   >> buttons.
   >>
   >>    Note that the keywords for the Quick Preset buttons in the specs
   >> will    probably change, to sync with the CUPS PPD specs.
   >>
   >> Can you give me the specs (or do you want to take a cut at it yourself)?
   >
   > For presets:
   >
   >     http://www.cups.org/documentation.php/sped-ppd.html#APPrinterPreset
   >
   > for everything else:
   >
   >     https://www.linuxfoundation.org/en/OpenPrinting/PPDExtensions

   Robert, I will update the part about the Quick Presets in my specs to
   use the *APPrinterPreset keyword as described on
   http://www.cups.org/documentation.php/sped-ppd.html#APPrinterPreset. For
   the time being use only "*<option> <value>" items in the presets to let
   the buttons appear with all print jobs, as for now the applications do
   not supply document type information.

Exactly how much information are we expected to provide with presets?

I do not like providing paper types with presets.  The right paper
type is a matter of what's loaded in the printer, not what the user
wants to do.  Specifying the wrong paper type can lead to trouble.  In
addition, there are many different kinds of photo paper that may have
to be treated differently.  For example, on Epson "glossy" paper may
mean Premium Glossy, Premium Luster, Premium Semigloss, the old
standby Glossy Photo Paper, and some of these papers come in multiple
weights, each of which may (optimally) require different settings.

--
Robert Krawitz                                     <rlk@...>

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

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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Till Kamppeter-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Robert Krawitz wrote:

> Exactly how much information are we expected to provide with presets?
>
> I do not like providing paper types with presets.  The right paper
> type is a matter of what's loaded in the printer, not what the user
> wants to do.  Specifying the wrong paper type can lead to trouble.  In
> addition, there are many different kinds of photo paper that may have
> to be treated differently.  For example, on Epson "glossy" paper may
> mean Premium Glossy, Premium Luster, Premium Semigloss, the old
> standby Glossy Photo Paper, and some of these papers come in multiple
> weights, each of which may (optimally) require different settings.
>

You are right. The exact selection of the presets has to be done by the
printer manufacturer and/or the driver developer, not by the OS,
printing system, or application developer. Presets can contain hints
about for which document type they are suitable, but they should stay
freely definable.

So I think we should take only the keyword itself and the syntax for the
key/value pairs into the Common Printing Dialog specs, but not the names
for the presets and also not which set of options each button sets. So
for GutenPrint you could simply make one preset button for each choice
of the "StpQuality" option and let it set "StpQuality" to the
appropriate value and all quality fine tuning options (at least the
enumerated choice and boolean ones) to the neutral/auto value.

Robert, Mike, WDYT?

    Till

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Parent Message unknown Re: Gutenprint and the Common Printing Dialog

by Till Kamppeter-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Michael R Sweet wrote:

> Till Kamppeter wrote:
>> Robert Krawitz wrote:
>>> Exactly how much information are we expected to provide with presets?
>>>
>>> I do not like providing paper types with presets.  The right paper
>>> type is a matter of what's loaded in the printer, not what the user
>>> wants to do.  Specifying the wrong paper type can lead to trouble.  In
>>> addition, there are many different kinds of photo paper that may have
>>> to be treated differently.  For example, on Epson "glossy" paper may
>>> mean Premium Glossy, Premium Luster, Premium Semigloss, the old
>>> standby Glossy Photo Paper, and some of these papers come in multiple
>>> weights, each of which may (optimally) require different settings.
>>>
>>
>> You are right. The exact selection of the presets has to be done by
>> the printer manufacturer and/or the driver developer, not by the OS,
>> printing system, or application developer. Presets can contain hints
>> about for which document type they are suitable, but they should stay
>> freely definable.
>>
>> So I think we should take only the keyword itself and the syntax for
>> the key/value pairs into the Common Printing Dialog specs, but not the
>> names for the presets and also not which set of options each button
>> sets. So for GutenPrint you could simply make one preset button for
>> each choice of the "StpQuality" option and let it set "StpQuality" to
>> the appropriate value and all quality fine tuning options (at least
>> the enumerated choice and boolean ones) to the neutral/auto value.
>>
>> Robert, Mike, WDYT?
>
> The preset naming convention is no longer enforced in Mac OS X, so
> the only important thing is the com.apple.print.preset.graphicsType
> attribute so the presets can be filtered based on the document type.
>

For the document type filtering, can we say that no filter means that
the preset is valid for all document types (as a preset valid for no
document type does not make sense)?

How is com.apple.print.preset.graphicsType interpreted? would
XXX.graphicsType or only graphicsType also work?

    Till

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Michael R Sweet :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Till Kamppeter wrote:
> ...
> For the document type filtering, can we say that no filter means that
> the preset is valid for all document types (as a preset valid for no
> document type does not make sense)?

Yes, if there is no graphicsType then the preset applies to all
document types.

> How is com.apple.print.preset.graphicsType interpreted? would
> XXX.graphicsType or only graphicsType also work?

We use the full name and do not look for other names that happen to
end in graphicsType, since those would be different attributes...

--
______________________________________________________________________
Michael R Sweet                        Senior Printing System Engineer

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Till Kamppeter-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Michael R Sweet wrote:

> Till Kamppeter wrote:
>> ...
>> For the document type filtering, can we say that no filter means that
>> the preset is valid for all document types (as a preset valid for no
>> document type does not make sense)?
>
> Yes, if there is no graphicsType then the preset applies to all
> document types.
>
>> How is com.apple.print.preset.graphicsType interpreted? would
>> XXX.graphicsType or only graphicsType also work?
>
> We use the full name and do not look for other names that happen to
> end in graphicsType, since those would be different attributes...

So to assure compatibility with Mac OS X clients we should simply use
com.apple.print.preset.graphicsType and let the Common Printing Dialog
under Linux look for the same keyword. This way we can have
cross-platform PPDs.

If an application does not give any document type hint, should we then
simply show all presets, regardless whether they have graphicsType filters?

    Till


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel

Re: Gutenprint and the Common Printing Dialog

by Robert Krawitz-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

   Date: Thu, 24 Jul 2008 14:31:39 +0200
   From: Till Kamppeter <till.kamppeter@...>

   Robert Krawitz wrote:
   > Exactly how much information are we expected to provide with presets?
   >
   > I do not like providing paper types with presets.  The right paper
   > type is a matter of what's loaded in the printer, not what the user
   > wants to do.  Specifying the wrong paper type can lead to trouble.  In
   > addition, there are many different kinds of photo paper that may have
   > to be treated differently.  For example, on Epson "glossy" paper may
   > mean Premium Glossy, Premium Luster, Premium Semigloss, the old
   > standby Glossy Photo Paper, and some of these papers come in multiple
   > weights, each of which may (optimally) require different settings.

   You are right. The exact selection of the presets has to be done by
   the printer manufacturer and/or the driver developer, not by the
   OS, printing system, or application developer. Presets can contain
   hints about for which document type they are suitable, but they
   should stay freely definable.

   So I think we should take only the keyword itself and the syntax
   for the key/value pairs into the Common Printing Dialog specs, but
   not the names for the presets and also not which set of options
   each button sets. So for GutenPrint you could simply make one
   preset button for each choice of the "StpQuality" option and let it
   set "StpQuality" to the appropriate value and all quality fine
   tuning options (at least the enumerated choice and boolean ones) to
   the neutral/auto value.

Sounds reasonable.  Right now the Epson driver is the only one that
supports quality settings; the others don't.

However, I don't want to do this before the -beta4 release -- right
now the PPD files are in a lot of flux.  Maybe after that, for the
-rc1.

--
Robert Krawitz                                     <rlk@...>

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

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

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel