[cups.general] STR #1923 fix incomplete?

[Tim Waugh]

On Thu, 2007-02-15 at 12:41 -0500, Michael Sweet wrote:
> I don't see us providing a way to distinguish between compiled-in
> defaults and admin-set defaults.

Why not?  Do you think the user interface we're using should be
different in some way?

> However, the following -default
> attributes are always set and cannot be removed:

I think you're now misunderstanding my use of 'removed'.  So let me be
as clear as I can:

I just want to build a graphical interface for adding and removing
'Option' lines in printers.conf, and I want to implement it using IPP
calls alone.

Currently the interface cannot be implemented without fetching and
parsing printers.conf to find out what 'Option' lines there are.

>      copies-default

So, obviously the attribute cannot be deleted in the IPP sense, but
there can be an 'Option copies' line, set by the admin, that can be
removed -- and this can be done using IPP calls.  It just isn't possible
to ascertain using IPP calls whether there *is* an 'Option copies' line
in the first place, since 'copies-default' is always present.

> > In other words, the admin tool I sent a screenshot of needs to be able
> > to know which options to list in the box, each with a 'Remove' button.
> > Obviously system defaults cannot be removed -- they are hardwired in the
> > software.
> 
> All system defaults can be overridden, too.

Yes, obviously -- that's the point of the admin tool I showed you a
screenshot of.  I just want the interface to be able to show a list of
admin-set options, and *only* admin-set options, so that they can be
modified or unset.

I think somehow we are talking past each other!

Tim.
*/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://lists.cups.org/pipermail/cups/attachments/20070215/d0dfb5a6/attachment.bin>