All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Weghorn <m.weghorn@posteo.de>
To: peter sikking <peter@mmiworks.net>
Cc: printing-architecture@lists.linux-foundation.org
Subject: Re: [Printing-architecture] Status and future of the Common Printing Dialog (CPD)
Date: Mon, 28 Mar 2016 21:49:59 +0200	[thread overview]
Message-ID: <56F98AE7.7060705@posteo.de> (raw)
In-Reply-To: <B8C7B89F-7C26-44DC-8756-40462551859F@mmiworks.net>

Hi Peter,

thank you very much for your reply. It helps me to understand better how
things around the CPD developed and why things are as they are now.

Thank you also for your advice regarding different designs for desktop,
mobile and tablet. That confirms my impression that the Common Mobile
Print Dialog might not be the right thing for us now on the desktop.

Regards,
Michael

On 2016-03-27 18:04, peter sikking wrote:
> hi Michael,
> 
>> Could somebody possibly say something about the current status of the
>> Common Printing Dialog? Is further activity planned or has it been
>> abandoned?
> 
> I led the interaction design work on that project, which again
> led and directed the implementation. I guess you have read all
> my blog posts, linked from [1].
> 
> work on the CPD seized years ago. 2011 sounds about right.
> 
> all the right people were in place, had done substantial
> amounts (some even a ton) of work on it (usability, design,
> implementation) and were ready to move forward. there was
> serious work left to do in the design, followed by development.
> 
> it was just that the parties who would reap all the value of
> this would not support it with what matters: budget. having
> paid for a good part of the design work out of my own pocket,
> that riled me.
> 
> when canonical did a hostile fork of the project, all the able
> people walked away and then there was… (nothing for all I know).
> 
> ps Micheal: desktop, mobile (keys & touch) and tablet are 4 different
> worlds for interaction designers. for your desktop context, you need
> desktop designs.
> 
> [1]
> http://www.linuxfoundation.org/collaborate/workgroups/openprinting/commonprintingdialog
> 
> 
>     --ps
> 
>         designs interaction for creatives +
>         solutions with a wide impact on society
> 
>         teacher, mentor, author, lecturer
>         http://mmiworks.net/peter
> 

  reply	other threads:[~2016-03-28 19:49 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-26 15:03 [Printing-architecture] Status and future of the Common Printing Dialog (CPD) Michael Weghorn
2016-03-26 15:42 ` Richard Hughes
2016-03-26 17:01   ` John Layt
2016-03-26 18:19     ` Michael Weghorn
2016-03-27 16:04 ` peter sikking
2016-03-28 19:49   ` Michael Weghorn [this message]
2016-03-29  9:23   ` Richard Hughes
2016-03-29 11:36     ` peter sikking
2016-03-29 12:19       ` Richard Hughes
2016-03-29 13:31         ` Till Kamppeter
2016-03-29 18:41         ` peter sikking
  -- strict thread matches above, loose matches on Subject: below --
2016-03-26 19:31 Ira McDonald
2016-03-26 22:19 ` Michael Weghorn
2016-03-26 22:21 ` Richard Hughes
2016-03-26 22:59   ` Ira McDonald

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=56F98AE7.7060705@posteo.de \
    --to=m.weghorn@posteo.de \
    --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.