All of lore.kernel.org
 help / color / mirror / Atom feed
From: Till Kamppeter <till.kamppeter@gmail.com>
To: Alex Wauck <alex.wauck@gmail.com>, Peter Sikking <peter@mmiworks.net>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Coding the Common Printing Dialog and its interface
Date: Wed, 30 Apr 2008 22:40:41 +0200	[thread overview]
Message-ID: <4818D949.5040605@gmail.com> (raw)
In-Reply-To: <b801b6f40804301312m3a97c2eie3257cd339865be@mail.gmail.com>

Peter, can you help Alex here?

Peter, can you also subscribe to the printing-architecture mailing list, 
as here the discussion about the implementation of the Common Printing 
Dialog will happen. Subscription via

https://lists.linux-foundation.org/mailman/listinfo/printing-architecture

    Till

Alex Wauck 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


  reply	other threads:[~2008-04-30 20:40 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 [this message]
2008-05-01 15:44     ` Alex Wauck
2008-05-01 16:58       ` Till Kamppeter
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=4818D949.5040605@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.