[Printing-architecture] Common Dialogs for Printing
glen.petrie at eitc.epson.com
Fri Apr 17 12:06:31 PDT 2009
The email I sent was to start a discussion; not a war. But, I gather
from your replies; "that it is your way or no way".
Thus, I would like to stop this email thread and return to something
I sorry, I am a user. I have been a user, architect and developer on
everything from embedded, handheld, mobile, desktop, office, and
production printing solutions including front-end and back-ends.
And Please..... two people in one usability test does not define a
Peace ............... please ...............
> -----Original Message-----
> From: peter sikking [mailto:peter at mmiworks.net]
> Sent: Friday, April 17, 2009 11:50 AM
> To: Petrie, Glen
> Cc: printing-architecture at lists.linux-foundation.org; printing-
> summit at lists.linux-foundation.org
> Subject: Re: [Printing-architecture] Common Dialogs for Printing
> Glen wrote:
> > I guess the addition of the actual preview to the CPD has triggered
> > more review of CPD from my perspective.
> > I hope and believe the key object of this effort is focused on
> > "Common". Thus, I now believe we may be trying to do too much in
> > the CPD and actually need three common dialogs; specifically, the
> > Common Preview Dialog (CRD), the Common Print Dialog (CPD), and the
> > Common Status/Monitoring Dialog (CSD).
> > Actually, what we call print preview is really "preview of the page
> > setup" or "layout". It is expected that printer will print the page
> > as shown in the "print preview" or "page preview". So is this the
> > "print preview" or the applications "page preview"???
> without a doubt _and_ proven by our first tests: the preview needs to
> a lo-res version of exactly what will come out of the printer.
> the good thing about usability tests is that it shuts down, for ever,
> endless discussions about what users really need.
> > Print Preview Dialog:
> this station is long past. see above.
> may I remind you all that is is 100% part of the design that when
> the transformation (formatting for paper) is for users creative/
> tricky/involved that then we recommend applications to show
> a dialog (the size of the actual application window) to let users
> hands-on control the transformation. this includes for instance
> sizing a spreadsheet (with the mouse, not by some number fields)
> across a grid of pages, or placing that image (for hi-end graphics
> apps like GIMP, inkscape) exactly on the page.
> from this transformation dialog the choice is going to be
> 'just print' or to go through the print dialog.
> > Print Dialog:
> > n When I print, however, 95% of the time I want to see a
> > symbolic representation of the print options. That is, which edge
> > is selected when duplex printing, where are the punch hole
> > locations, is the print BW or color, is the media in portrait or
> > landscape mode. None of these and other print options require the
> > actual print content.
> > o In this case, I am not willing to wait for a thumbnail
> > representation of my actual print content because it adds no value
> > to setting print options.
> > o Having a consistent symbolic representation is critical
> > because it makes it easier to quickly identify what options I have
> > set or have not set.
> > n Therefore, I really support using the previous version of
> > the CPD along with a symbolic representation of the print options.
> like Mike said: you are not the user. please...
I sorry, I am a user. I have been a user and developer on everything
from embedded, handheld, mobile, desktop, office, and production
Please..... two people in one usability test define a
> with your knowledge of how it all works you are separating things out
> that are not separate for any non-printing-industry user.
> remember the video clips I showed: the only thing that counts is
> the hardcopy that comes out of the printer. the preview as an integral
> part of the dialog reflects that fact.
> > Status/Monitoring Dialog:
> as I said: next project.
> founder + principal interaction architect
> man + machine interface works
> http://mmiworks.net/blog : on interaction architecture
More information about the Printing-architecture