From: Till Kamppeter <till.kamppeter@gmail.com>
To: Till Kamppeter <till.kamppeter@gmail.com>
Cc: printing-architecture@lists.linux-foundation.org,
printing-summit@lists.linux-foundation.org,
Michael R Sweet <msweet@apple.com>
Subject: Re: [Printing-architecture] [Printing-summit] Preview for CPD
Date: Thu, 16 Apr 2009 19:49:21 +0200 [thread overview]
Message-ID: <49E76FA1.2020300@gmail.com> (raw)
In-Reply-To: <49E76EA6.10306@gmail.com>
We should also try to get the best for the live preview. For example it
should render only the visible page (and the CPDAPI should support that).
Till
Till Kamppeter wrote:
> I also agree with the use of a default image, once, while waiting for a
> live preview and second, on systems not capable of generating previews
> due to restricted resources, and also for the case that the client
> application does not support live preview (for example it did not get
> changed towards the printing dialog but Lars' stage-1-CPDAPI-patched GTK
> or Qt is used).
>
> Till
>
> Ira McDonald wrote:
>> Hi,
>>
>> I agree with Glen's suggestion - default images for preview
>> should ALWAYS be the fallback - for the limited-resource
>> embedded environment REAL preview images are NOT a
>> good idea.
>>
>> I also agree with Mike (and Glen) that displaying the default
>> image WHILE generating the real preview image is a friendly
>> design approach.
>
>
next prev parent reply other threads:[~2009-04-16 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 14:45 [Printing-architecture] Preview for CPD Petrie, Glen
[not found] ` <49E768BF.6030404@apple.com>
2009-04-16 17:23 ` [Printing-architecture] [Printing-summit] " Petrie, Glen
2009-04-16 17:29 ` Ira McDonald
2009-04-16 17:45 ` Till Kamppeter
2009-04-16 17:49 ` Till Kamppeter [this message]
2009-04-17 18:08 ` [Printing-architecture] " peter sikking
2009-04-17 18:54 ` Petrie, Glen
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=49E76FA1.2020300@gmail.com \
--to=till.kamppeter@gmail.com \
--cc=msweet@apple.com \
--cc=printing-architecture@lists.linux-foundation.org \
--cc=printing-summit@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.