From: Till Kamppeter <till.kamppeter@gmail.com>
To: peter sikking <peter@mmiworks.net>
Cc: "Petrie, Glen" <glen.petrie@eitc.epson.com>,
printing-architecture@lists.linux-foundation.org,
printing-summit@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Another Common Dialog
Date: Fri, 17 Apr 2009 20:38:48 +0200 [thread overview]
Message-ID: <49E8CCB8.4000201@gmail.com> (raw)
In-Reply-To: <1F40945E-38C1-4ADC-B54C-DEF213F8A625@mmiworks.net>
peter sikking wrote:
> Glen,
>
>> Have you ever considered creating/defining a Common Status/Monitoring
>> Dialog.
>
> for printing: sure that is the next project, together with
> printer installation.
>
>> CUPS may have something already but does it support multi-function
>> devices sub-units like fax, scan, memory card, etc and can it provide
>> the status/monitoring information on a sub-unit by sub-unit basis or
>> as a roll-up for the entire MFD or both????
>
> for users printing, faxing, scanning, memory card reading are
> totally unrelated activities. so it follows that faxing, scanning,
> memory card reading is never going to be seen in a printing dialog
> and also not in a status/monitoring dialog.
>
I would say so, too. The scanner should appear in scanning applications,
memory cards should simply get auto-mounted and appear on the desktop
(at least for locally connected devices, for network devices they should
appear when scanning for file system shares in the network). Sending
faxes should be done by a print queue where the printing dialog shows an
appropriate widget for the fax number. A dialog to put these functions
together is not needed. It can even get counter-intuitive if an MF
device and a scan-only device is connected to the same machine.
Till
next prev parent reply other threads:[~2009-04-17 18:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 18:21 [Printing-architecture] Another Common Dialog Petrie, Glen
[not found] ` <4B3C1712-1367-404C-B77B-E7C5E5110C28@apple.com>
2009-04-16 21:35 ` [Printing-architecture] [Printing-summit] " Petrie, Glen
2009-04-16 21:50 ` Till Kamppeter
2009-04-17 18:21 ` [Printing-architecture] " peter sikking
2009-04-17 18:38 ` Till Kamppeter [this message]
2009-04-17 18:54 ` peter sikking
2009-04-17 18:58 ` Petrie, Glen
2009-04-17 19:32 ` Hal V. Engel
2009-04-17 20:55 ` Till Kamppeter
2009-04-18 9:57 ` peter sikking
[not found] ` <200904172344.n3HNivf6025718@dsl092-065-009.bos1.dsl.speakeasy.net>
2009-04-18 9:39 ` [Printing-architecture] [Printing-summit] " peter sikking
[not found] ` <alpine.LNX.2.00.0904211009120.29424@nelson.suse.de>
2009-04-21 9:09 ` peter sikking
2009-04-21 9:14 ` peter sikking
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=49E8CCB8.4000201@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=glen.petrie@eitc.epson.com \
--cc=peter@mmiworks.net \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-summit@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.