From: Till Kamppeter <till.kamppeter@gmail.com>
To: Alex Wauck <alex.wauck@gmail.com>
Cc: printing-architecture@lists.linux-foundation.org,
Peter Sikking <peter@mmiworks.net>
Subject: Re: [Printing-architecture] Coding the Common Printing Dialog and its interface
Date: Thu, 01 May 2008 18:58:13 +0200 [thread overview]
Message-ID: <4819F6A5.3040400@gmail.com> (raw)
In-Reply-To: <b801b6f40805010844ka80fd30o64e1df4b525e00e2@mail.gmail.com>
Peter, what is the importance of your column height restrictions? Or is
it only an aspect ratio restriction (see Alex' problems below)?
Josef, you as expert on automatic dialog creation, can you help Alex
here? AFAIR there was only a restriction on the aspect ratio of the
columns and not on the absolute height.
Till
P. S.: Josef can you also subscribe to printing-architecture, as this is
the central discussion place for the implementation of the Common
Printing Dialog. Subscription via
https://lists.linux-foundation.org/mailman/listinfo/printing-architecture
Alex Wauck wrote:
> Another comment:
> Forcing the columns to be a particular height is not particularly easy
> in Qt (I don't know how difficult it is in GTK+), and it leads to
> unexpected behavior when resizing the dialog. Specifically, some resize
> operations are not possible, and the user may not like that. Is it
> really necessary to force column height? Perhaps that part of the spec
> should be relaxed to a preferred or minimum height instead of a required
> height. I got it to work in Qt by subclassing QGridLayout, but it's a
> bit of a hack, and a real solution would likely be much more difficult.
>
> Alex
>
> On Wed, Apr 30, 2008 at 3:12 PM, Alex Wauck <alex.wauck@gmail.com
> <mailto:alex.wauck@gmail.com>> wrote:
>
> One comment so far: in the "dialog specification" section, it only
> mentions the three columns in the middle part of the dialog. Then,
> in the "Dialog Zones Specification" section, it adds a zone that
> spans columns 2 and 3. That has very different consequences for the
> implementation than simply having three columns. It looks like the
> level 3 dialog always has that zone, so perhaps the first
> specification should mention it?
>
> Alex
>
>
> On Wed, Apr 30, 2008 at 1:33 PM, Till Kamppeter
> <till.kamppeter@gmail.com <mailto:till.kamppeter@gmail.com>> wrote:
>
> Till Kamppeter wrote:
>
> 3. How the OpenUsability dialog itself has to look like and
> how it is
> operated.
>
> - See Peter Sikking's blog
>
> http://www.mmiworks.net/eng/publications/labels/openPrinting.html
> - Peter is working with a student on the specs.
>
>
> Peter has started to write down the specs here:
>
> http://wiki.openusability.org/printing/index.php/Specification
>
> Till
>
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Printing-architecture mailing list
> Printing-architecture@lists.linux-foundation.org
> https://lists.linux-foundation.org/mailman/listinfo/printing-architecture
next prev parent reply other threads:[~2008-05-01 16:58 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 21:54 [Printing-architecture] Coding the Common Printing Dialog and its interface Till Kamppeter
2008-04-25 1:19 ` Marcelo Ricardo Leitner
2008-04-25 11:51 ` Till Kamppeter
2008-04-25 23:07 ` Marcelo Ricardo Leitner
2008-04-27 11:05 ` Till Kamppeter
2008-05-01 15:46 ` Lars Uebernickel
2008-05-01 17:05 ` Till Kamppeter
2008-05-01 17:51 ` Lars Uebernickel
2008-05-01 17:59 ` Till Kamppeter
2008-04-30 18:33 ` Till Kamppeter
2008-04-30 20:12 ` Alex Wauck
2008-04-30 20:40 ` Till Kamppeter
2008-05-01 15:44 ` Alex Wauck
2008-05-01 16:58 ` Till Kamppeter [this message]
2008-05-01 23:48 ` Olaf Meeuwissen
2008-05-02 3:17 ` Alex Wauck
2008-05-02 5:59 ` Olaf Meeuwissen
2008-05-04 11:06 ` peter sikking
2008-05-05 6:17 ` Josef Spillner
2008-05-01 16:33 ` Lars Uebernickel
2008-05-01 17:57 ` 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=4819F6A5.3040400@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=alex.wauck@gmail.com \
--cc=peter@mmiworks.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.