Tom, as usual, you are not only the first to submit a uses case, but have
done a admiral job describing the user scenario. Each use case should have
a possible technical solution or solutions (using IPP and/or other
standards?, or TBD) that the open source client implementers can use to
implement the feature/requirement. Tom's submission includes such an
implementation suggestion. Thanks Tom.
As for the rest of you, please submit each use case with a "Title",
"Description", and "Possible Implementation" section. The title should
sufficiently describe the use case; it will be the "one-liner" that is used
in our brainstorming session sometime during our next set of PWG meetings. A
suggestion was made that we post these to the PWG Web site (in a table?) so
you can look at them collectively and begin to think about priorities. Any
thoughts?
Please note that your submission can be very simple. For example:
Title: IPP/MS Windows Driver Download
Description: Windows user logs onto network and driver magically gets
installed as the default windows printer. (There are many variations of this
use case.)
Possible Implementation: IPP driver download (including any new extensions)
I look forward to your submissions.
**CW
> -----Original Message-----
> From: Hastings, Tom N [SMTP:hastings@cp10.es.xerox.com]
> Sent: Wednesday, May 17, 2000 7:20 PM
> To: pwg-ipp
> Subject: User Scenario for Open Source client feature: On Windows
> batch ma ny prints into a single job (single output document)
>
> At our Open Source Client meeting tonight, we agreed that we should all
> submit User Scenarios illustrating features that users would find useful.
> A
> suggestion of the technology to implement the feature was also encouraged.
> Then Craig Whittle volunteered to help organize a prioritization of them.
>
> So, here is a suggested contribution to the User Scenarios for features
> that
> an Open Source client for Windows could support:
>
> On Windows batch many prints into a single job (single output document)
>
> I'd like to be able to print from any number of applications, any number
> of
> times, but have the output from each collected into a single print job,
> perhaps so I can have it all stapled as a single output document. I want
> to
> go pick it up as a single job from my network printer. Perhaps my network
> printer supports fan-out, so that sending a lot of little jobs over the
> period of an hour results in them being sent randomly to the fanned-out
> printers. This batching of separate print jobs into a single print job
> would be particularly useful from applications such as Outlook or Eudora
> where I want to print certain mail messages as I'm reading them, but only
> want them all printed together as a single job (and all stapled together).
> However, I might like to include output from any other application that I
> happen to be running during the same period. On the other hand, I might,
> during the same period, also want to print something big separately and
> immediately.
>
> Possible technology implementation:
> Install a special "printer" that collects jobs and doesn't actually submit
> them until told to do so by me explicitly. So any Windows printing that I
> do to that Printer gets accumulated into one big job. Perhaps this
> printer
> actually submits the big job as an IPP job that consists of separate
> documents. I'd like to be able to specify "finishings" as one of the
> staple
> values, such as 'staple-dual-left', and with the option of either
> "multiple-document-handling" = 'single-document-new-sheet', so that each
> little job starts on a new sheet, OR "multiple-document-handling" =
> 'single-document' so that each little job just starts on a new side.
>
> Comments?
>
> Is this what was meant at the meeting for a User Scenario that is a user
> feature that we could prioritize?
>
> Tom
This archive was generated by hypermail 2b29 : Thu May 18 2000 - 12:05:12 EDT