From: Per Hermansson <hermansson.per@bredband.net>
To: printing-architecture@lists.linux-foundation.org
Subject: [Printing-architecture] GSOC'09: Common Printing Dialog
Date: Thu, 26 Mar 2009 12:02:29 +0100 [thread overview]
Message-ID: <49CB60C5.8010608@bredband.net> (raw)
Hi,
My name is Per Hermansson and I'm a student from the Royal institute of
technology in Sweden. I'm interested in developing the common printing
dialog. Designing a printing dialog with usability in mind seems like an
important task which if done correct would benefit a lot of people. I
consider myself to be experienced in C/C++ developing and have developed
with GTK. Since I've recently switched to KDE I hope to also learn a bit
about Qt. After some investigation about the idea, I've come up with the
following questions I hope someone here can answer:
Since designing the interface is a major component would it be possible
to implement the dialog with both Qt and GTK for one summer? I guess
this depends on skill level (but e.g. abstracting the dialog model would
make it easier).
Except for the printing dialog and the cpdapi implementation I guess
that some kind of abstraction is needed so that the underlying print
method is decoupled from D-Bus in order to use the api for systems
without D-Bus?
Also, if two students are chosen for the project what would be a good
measure for success in modifying other application to use the dialog?
Finally is the cpdapi used (or experimented with) by any applications
today that you know of?
/Per
next reply other threads:[~2009-03-26 11:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 11:02 Per Hermansson [this message]
2009-03-26 16:25 ` [Printing-architecture] GSOC'09: Common Printing Dialog Alex Wauck
2009-03-26 19:15 ` Till Kamppeter
2009-03-26 20:45 ` Per Hermansson
2009-03-26 23:48 ` Till Kamppeter
2009-03-27 0:28 ` Alex Wauck
2009-03-28 13:11 ` Per Hermansson
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=49CB60C5.8010608@bredband.net \
--to=hermansson.per@bredband.net \
--cc=printing-architecture@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.