<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Cambria;
panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Cambria;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 85.55pt 1.0in 85.55pt;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>Till,<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>Thanks for the feed back. I believe we
have a similar understanding of the problem and what should be in the
guideline. I have noted your comments below and will make sure to
capture them as part of the development of the guideline. <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>I hope to hear from other on guideline.
Once I get some more comments I will try to capture all of the ideas and
comments.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>Have some other ideas related to this
guideline that I will try to send out today or next week.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>Glen<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
For item 4 and 5, I can go through the various combinations to determine<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
the determinable constraints and relationships.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>Constraints
and relationships often depend on the particular printer, <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>some
can do duplex on envelopes, others no. For that the client (the <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>mobile
device) needs to be able to poll this info from the <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>printer/server
before displaying a printing dialog.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'>[</span></font><font color=blue><span
style='color:blue'>gwp] My idea for mobile print is that we would limit the
options like “duplex on envelopes”. The guideline we only
recommend support for the 90% (95% or 99%) print intents. Thus, I am
hoping that the constraints and relationships are definable up front and, thus,
can be predetermined. For mobile, this predetermined constraints
and relationships would greatly reduced complexities. </span></font><font
color=black><span style='color:black'><o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
I can go through the various combinations and create a set of predefined<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
print mode (photo, web page, etc) that mobile devices (clients) can<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
specify and will be understood by the print services or printer.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>Presets
are a good idea on mobile as the limited space cannot hold lots <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>of
fine-tune options and most users want to select a simple document <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>type
instead of lots of settings. By the way, Apple AirPrint also uses <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>presets.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] same comment as above. <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
What would the simplest print-architecture look like and various levels<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
of complexity. That is can a mobile device include CUPS or another, and<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
simpler, print manager (management) solution. How thin can a print<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
manger (management) module be? We would specific (as part of the<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
guideline) what was the minimum support and the ordering for adding more<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
complex capabilities.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>One
important thing is that on mobile we do not need a <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>RIP/filters/backends
and also not the CUPS web interface. A pure <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>CUPS/IPP
client with a simple printing dialog would be enough. Then we <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>can
print onm AirPrint (PDF files via IPP) and on IPP Everywhere.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] I would like to initially determine
(review) the requirements of the “Print Manager” versus specify an
implementation at this time. Then, the guideline would recommend
components. <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] The “simple printing dialog”
is what the guideline is about along with what components it takes to support
it. I am hoping the printing dialog (no matter was interface type
or what level of complexity) can be coherent as perceived the user.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
For the various combinations of interface types shown below, I can<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
create proposed “values” (names or iconics or keystroke or
whatever) to<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
support each interface type.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•a dialog box? (how big?, how many pixels)<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>Mobile
screen sizes vary, especially as there are conventional phones, <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>smartphones,
and tablets/netbooks. So we need flexibility. Tablets and <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>netbooks
can even show the desktop dialog.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] Yes; this is challenge. While
we also way think of the printer supplying capabilities; now the display will
have to provide capabilities (physical size, pixel size, aspect ratio, color
(how many levels), interface type (touch, stylus, etc). Printing
will not be the only application that will need this capability information.
Virtually, any post-hosted application would need this information.</span></font><font
color=black><span style='color:black'> <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•pull down menus?<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•hierarchical menus? (same as display on a printer)<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•one or more iconic?<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>Depends
on how well it works on a touch screen.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] Agreed. But the guideline would
provide a recommendation based on the display capabilities.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•keystroke commands?<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>Not
suitable for touch but useful for netbooks.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] Agreed. But the guideline would
provide a recommendation based on the device capabilities.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•gesturing (double tap to print)?<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>Nice
for touch, but should not interfere with existing gestures and <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>should
not print without confirmation.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] Sorry, I meant double tapping on a
printer iconic to initiate printing. Whether this will actually prints or
just bring up the print dialog is something we need to examine and explore. <o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] I am not sure that a
print-confirmation is always needed. I believe we need to examine the
interface solutions and make a recommendation (as part of the guideline) on
whether print-confirmation is necessary.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•a physical button action?<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
•combinations of the above?<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
The guideline would need a conformance section (include what not to do).<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
The guideline conformance should define the level of print “dialog”<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
(interface) support is required for a mobile device with specific<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
display size and computing power. (think of phone to iPad to netbook to<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
laptop)<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>This
is a good idea, priinting dialog guideline by screen size class.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=black face=Cambria><span
style='font-size:12.0pt;color:black'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;color:blue'>[gwp] This is the key concept for the
mobile print guideline. We need to take care in developing this part of
the guideline.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
The guideline needs to define how applications can
“””extent””” mobile<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
printing and mobile dialogs. The same would be true for print vendor<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
extension.<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
The guideline would need a complete glossary. (I suspect that this would<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
be used by people with various levels of print interface development<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
experience.)<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
The guideline would need a sample implementation (?) of each interface<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>>
type (?)<o:p></o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoPlainText><font size=3 face=Cambria><span style='font-size:12.0pt'>
Till<o:p></o:p></span></font></p>
</div>
</body>
</html>