From: Till Kamppeter <till.kamppeter@gmail.com>
To: Josef Spillner <spillner@kde.org>,
"printing-summit@lists.freestanda"
<printing-summit@lists.freestandards.org>
Cc: printing-architecture@lists.freestandards.org
Subject: Re: [Printing-architecture] Printer dialog generation
Date: Mon, 28 Aug 2006 12:24:37 +0200 [thread overview]
Message-ID: <44F2C465.1080907@gmail.com> (raw)
In-Reply-To: <200608281158.32769.spillner@kde.org>
The printing dialog is one of the main subjects of the upcoming FSG
OpenPrinting Summit in Lexington, KY, which I am organizing together
with the Free Standards Group:
http://www.freestandards.org/en/OpenPrinting/SummitLexington
There is already work in progress about printing dialogs and usability
at OpenUsability.org. This work started on the OSDL Printing Summit in
Atlanta, which I organized together with the OSDL in April this year.
The subject will be continued on the upcoming Summit:
http://www.freestandards.org/en/OpenPrinting/SummitLexington#Printing_Dialog
So I recommend to discuss this on the printing-summit mailing list (I
have cross-posted it to there now), and also on the Summit itself.
Josef, you are also invited to attend the Summit, to meet the printing
and desktop developers and also the OpenUsability team.
Till
Josef Spillner wrote:
> Hello,
>
> a few weeks ago I talked to some people about the possibility of having print
> dialogs generated from a formal schema and some GUI generation hints.
> [I hope this is the correct list for such topics.]
>
> I'm involved with research in this area, particularly in ad-hoc usage of web
> services, but most of the concepts apply to any schema-based GUI generation.
> A schema in the world of printing would be a data model which includes
> choices about the paper size, printer capabilities and document-specific
> options.
>
> Creating type-safe dialogs which represent the schema are not an issue, there
> are proven concepts and we have work in progress code for KDE, for example.
> However, creating GUIs which follow HCI standards and are at least basically
> usable is a challenge. Layouting algorithms in particular are not well
> explored yet and almost always need human correction.
>
> As someone not coming from the world of printers, I find PPD files slightly
> weird, to put it mildly. They contain both information about printers and
> interaction code akin to an embedded programming language. However, they seem
> to contain all the necessary information needed for user configuration,
> especially multi-language strings.
>
> Now there are a few questions to those who could help:
> * What are the issues with current print dialogs that could or should be
> solved with GUI generation?
> * Are there other printer description formats I should have a look at?
> * Is there any work being done in this area already?
>
> Josef
>
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.freestandards.org
> http://lists.freestandards.org/mailman/listinfo/printing-architecture
>
next prev parent reply other threads:[~2006-08-28 10:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 9:58 [Printing-architecture] Printer dialog generation Josef Spillner
2006-08-28 10:24 ` Till Kamppeter [this message]
2006-08-28 11:35 ` Michael Sweet
2006-08-28 11:56 ` Till Kamppeter
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=44F2C465.1080907@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=printing-architecture@lists.freestandards.org \
--cc=printing-summit@lists.freestandards.org \
--cc=spillner@kde.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.