From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <49E76FA1.2020300@gmail.com> Date: Thu, 16 Apr 2009 19:49:21 +0200 From: Till Kamppeter MIME-Version: 1.0 References: <49E768BF.6030404@apple.com> <49E76EA6.10306@gmail.com> In-Reply-To: <49E76EA6.10306@gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Printing-architecture] [Printing-summit] Preview for CPD List-Id: Printing architecture under linux List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Till Kamppeter Cc: printing-architecture@lists.linux-foundation.org, printing-summit@lists.linux-foundation.org, Michael R Sweet 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. > >