All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alastair M. Robinson" <blackfive@fakenhamweb.co.uk>
To: Robert Krawitz <rlk@alum.mit.edu>
Cc: printing-architecture@lists.linux-foundation.org,
	gimp-print-devel@lists.sourceforge.net
Subject: Re: [Printing-architecture] [Gimp-print-devel] Looking ahead to 5.3
Date: Sat, 25 Oct 2008 20:35:58 +0100	[thread overview]
Message-ID: <4903751E.2000507@fakenhamweb.co.uk> (raw)
In-Reply-To: <200810251857.m9PIvIdi030089@dsl092-065-009.bos1.dsl.speakeasy.net>

Hi :)

Robert Krawitz wrote:

> Right, but that's not efficient for printing large documents at high
> resolution over a network.

Agreed.

> I don't think that that's quite good enough.  I'm OK with having the
> CPD itself provide only a limited set of options, as long as it's
> possible for both users and administrators to create preset bundles
> that may reference options not provided in the PPD file.  Requiring
> use of a client side RIP in order to use custom linearization curves
> isn't acceptable to me.

Fair enough - and I tend to agree - I'm just trying to figure out what 
we can do within the bounds of the current infrastructure, and whether, 
or to what extent, we need new facilities!

> So someone might want to create a preset bundle that includes
> linearization curves and other settings for a particular paper type,
> resolution, and ink set (e. g. photo or matte inks).  I think a user
> should be able to do that just as well as an administrator.

In the scenario I outlined, a user is able to do that.  The sticking 
point is that actually *installing* it, so that the changes can be used 
via the CPD, would require admin rights.

> Note that the preset bundle may actually be a large amount of data.

Yes indeed.

All the best,
--
Alastair M. Robinson


  parent reply	other threads:[~2008-10-25 19:35 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200810132357.m9DNvMRf015955@dsl092-065-009.bos1.dsl.speakeasy.net>
     [not found] ` <48FB37A3.8090007@gmail.com>
     [not found]   ` <200810191602.m9JG2D84030719@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-22 14:49     ` [Printing-architecture] [Gimp-print-devel] Looking ahead to 5.3 Till Kamppeter
2008-10-22 15:17       ` peter sikking
     [not found]         ` <200810230019.m9N0JCIp018128@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-24  8:52           ` peter sikking
2008-10-24 10:08             ` Till Kamppeter
2008-10-24 12:35             ` Alastair M. Robinson
2008-10-24 18:34               ` Hal V. Engel
     [not found]                 ` <49021D0B.4040708@apple.com>
2008-10-25  0:46                   ` Alastair M. Robinson
     [not found]                 ` <200810251458.m9PEwS6D029068@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-25 17:43                   ` Alastair M. Robinson
     [not found]                     ` <200810251857.m9PIvIdi030089@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-25 19:35                       ` Alastair M. Robinson [this message]
     [not found]                         ` <200810251950.m9PJoeFa030284@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26  0:41                           ` Alastair M. Robinson
     [not found]                             ` <200810260049.m9Q0nTIw032617@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26  1:18                               ` Alastair M. Robinson
     [not found]                               ` <49049DC3.8000405@apple.com>
     [not found]                                 ` <200810261653.m9QGrk2l014877@dsl092-065-009.bos1.dsl.speakeasy.net>
     [not found]                                   ` <490530BC.9090803@apple.com>
     [not found]                                     ` <200810271054.m9RAsDLs001975@dsl092-065-009.bos1.dsl.speakeasy.net>
     [not found]                                       ` <alpine.LNX.1.10.0810281134060.17582@nelson.suse.de>
2008-10-28 12:59                                         ` Till Kamppeter
2008-10-28 15:19                                           ` Till Kamppeter
     [not found]                                             ` <49074E92.5020809@apple.com>
     [not found]                                               ` <alpine.LNX.1.10.0810290940570.3548@nelson.suse.de>
     [not found]                                                 ` <200810310048.m9V0mDYI005128@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-31  1:53                                                   ` Alastair M. Robinson
2008-10-25 22:38                     ` Till Kamppeter
     [not found]                       ` <200810252249.m9PMnrSo030956@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26  9:59                         ` Till Kamppeter
     [not found] ` <200810201403.26403.hvengel@astound.net>
     [not found]   ` <200810210026.m9L0Qnd5008431@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-22 17:15     ` [Printing-architecture] [Gimp-print-devel] [Openicc] " Hal V. Engel
     [not found] ` <200810260141.m9Q1fdci000540@dsl092-065-009.bos1.dsl.speakeasy.net>
     [not found]   ` <4904A0EA.4030508@apple.com>
2008-10-26 18:40     ` [Printing-architecture] [Gimp-print-devel] " Hal V. Engel
     [not found]       ` <200810261904.m9QJ423w015373@dsl092-065-009.bos1.dsl.speakeasy.net>
2008-10-26 21:23         ` Hal V. Engel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4903751E.2000507@fakenhamweb.co.uk \
    --to=blackfive@fakenhamweb.co.uk \
    --cc=gimp-print-devel@lists.sourceforge.net \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=rlk@alum.mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.