[Openicc] GoSoC 2011: CPD and target printing
ku.b at gmx.de
Sat May 7 01:00:55 PDT 2011
Am 07.05.2011 05:02, schrieb Chris Murphy:
> On May 6, 2011, at 8:16 PM, Robert Krawitz wrote:
>> And it means that if I do want to use those options I have to somehow
>> export it to that special application and hope nothing goes wrong
>> along the way, in addition to requiring a clumsy extra step. I just
>> think that that's the wrong design point.
> No the application is what would show the complex UI for all options, and exports the preset in the proper format, in the proper location, and the preset appears in the CPD, rather than the CPD's options/extended panel being ludicrously cluttered. The CPD already has to do the right thing along the way, if it does the wrong thing when the user chooses all of these options, something will go wrong. It's no different with a utility application.
Satisfaction to a large and in parts specialised user group and simple
just working UIs have both their charm. The idea to initially hide many
of the CPD options and then disclose on request seems appealing. Just
where to disclose. Chris points out, as soon this disclosing happens in
the UI people can get on the wrong path. Thats as well my experience.
Robert, Hal and others are afraid to give too much decisions away in
others hands. I share that too.
As I can't really decide what to favor, I would like to see as end user
three ways to integrate both approaches.
* applications which display all those options which fit to their
complexity of printing, that seems already done in the CPD design
* a rather simple interface to display the requested options from the
command line, DBus and environment variables are the Unix approach to
this, (maybe its already possible as well?)
* convenient and persistent configuration of the visibility of those
options, e.g. a desktop config entry in the print configuration panel,
like a minimal (and maximal) option set
Great input from you all.
in the train to LGM
More information about the openicc