Closed michaelrsweet closed 17 years ago
CUPS.org User: mike
Reassigned to CUPS 1.2.
Are you looking for the same printer list and controls as on the "printers" page?
CUPS.org User: angelb.bugarin
I've been experimenting with two CUPS servers. And I'm starting to migrate some of our native LP/LPD printers to CUPS. What that means is that I'll be looking at thousands of printers in that one view, the Printers page, via the web interface.
My plan is to group the printers by location and function. This means using an explicit class. Currently, the printer Class from the web interface, when selected, shows a list of printers in its members. You can perform class administration while in the page but not printers.
For example, I have a printer Class named SAP. In the SAP class is a printer called SAPPTR1. When I select or click on the SAP class, it returns or shows the name SAPPTR1 in its members(but you can't admin SAPPTR1 while in the class page).
The CUPS enhancement I'd like to see are the following: a. When selecting(click) on a printer class from the web interface, it should return a list of printers(like the printers page) but printers that only belong in that class(not all printers). At this point, NO administration controls is displayed.
b. When selecting(click) on a printer from a class listed, it should display the printer AND printers administration controls; ie, add, delete, modify, etc.
c. A multi-tiered class(not essential now but would be really nice). For example: I have a class named CHICAGO. A subclass called CHICAGO_ACCTG and CHICAGO_ENGR. To take it further, subclass CHICAGO_ACCTG_MGR and CHICAGO_ACCTG_CLRK. Then the printer, CHICAGO_ACCTG_MGR_HP1.
The values I see when the features above added to CUPS are: a. Makes the software more user-friendly. By allowing the user to stay in one page and perform printer administrations.
b. Simplifies printer administration for thousands of printers. By implementing explicit classes, the admin can group printers by location, function, criticality, usage, etc. And by working in the class, the admin can dynamically administer a printer from within the class page without having to go to the Printers page.
c. By allowing the user creates multi-tiered class, it makes finding a printer faster, from thousand of printers, by going directly to the class. The administrator can also then assign a user admin rights to administer specific class or subclass.
Those are some features I'd like to see in CUPS in future releases. And I hope they made sense.... :)
Thanks! Angel
CUPS.org User: mike
OK, got it, thanks.
CUPS.org User: mike
OK, I'm reassigning this to -feature, so this will not be in CUPS 1.2.
That said, we've made a LOT of changes to the web interface, so I'll be interested in hearing if these changes are still needed, and if so what changes are needed.
CUPS.org User: mike
Pushing this out to CUPS 1.5 at the earliest; I'd still like feedback on whether these changes are even necessary with the current code...
CUPS.org User: angelb.bugarin
The CUPS enhancement I'd like to see are the following:
#
#
Features A and B above are already existing in the current code. As for feature C, since the main idea for having a class is to serve a print job by the next avaialble printer in that class, and not for zoning set of printers for specific access rights, I don't think it's no longer necessary.
Thanks, Angel
Version: -feature CUPS.org User: angelb.bugarin
Classes are great for grouping printers with specific type/function; ie, SAP, Accoutning, Engr, etc.
Currently, when you access a printer Class, you get a listing of queue names that belongs to the Class.
Will there be a patch for CUPS so that when you access the printer Class, you are presented with the actual printer objects like the Printers function instead of just names? This will be usefull specially when dealing with hundreds of printers. From the Class, you can then perform the normal printer administration. Currently, I have to search a printer from the list provided by the Printers function.
Simply put, show a list of printers, not just names, and the admin controls when accessing a printer class.
Thanks! Angel