[cups] OS X dialog to add a printer

[Jacob Marble]

...attachment attached.

If anyone knows an Apple eng that is familiar with PrinterUITool, please
ping.


Jacob


On Fri, May 30, 2014 at 2:45 PM, Jacob Marble <jacobmarble at google.com>
wrote:

> Excuse me, that last message was intended for another list.
>
> Here is a screenshot to demonstrate what happens when printer
> "castlevania-color" is selected. The Name and Location fields are properly
> populated, but not the driver field.
>
> I resolved a very similar problem with the Red Hat system-config-printer
> tool <http://cyberelk.net/tim/software/system-config-printer/> by
> removing an at-sign from the driver's ppd-name.
>
> Again, if this is not the right list, please advise.
>
>
> Jacob
>
>
> On Fri, May 30, 2014 at 2:16 PM, Jacob Marble <jacobmarble at google.com>
> wrote:
>
>> Well, it turns out that the driver was returning an at-sign @ in the
>> ppd-name field, and system-config-printer did not like that. Is there a log
>> where I can check for these kinds of errors?
>>
>> Thanks
>>
>>
>> Jacob
>>
>>
>> On Thu, May 29, 2014 at 1:16 PM, Jacob Marble <jacobmarble at google.com>
>> wrote:
>>
>>> CUPS Cloud Print <http://www.niftiestsoftware.com/cups-cloud-print/> (CCP)
>>> is a backend to Google Cloud Print printers. It could work better in OS X,
>>> so that's what I'm doing today.
>>>
>>> When the user tries to add a printer using the standard OS X (10.9)
>>> dialog ("default" tab), CCP properly provides a list of printers to
>>> cups-deviced, as proven in the OS X dialog.
>>>
>>> However, when the user selects a printer, invoking [cups-driverd list
>>> ...], CCP returns something wrong such that the "Name" and "Location"
>>> fields are properly pre-filled, but the "Use" field (backend/driver/PPD)
>>> falls back on "Generic PostScript Printer" with the message "The selected
>>> printer software isn't from the manufacturer blah blah blah."
>>>
>>> The PPD is generated dynamically with [cups-driverd cat
>>> cupscloudprint:blah]. Calling this by hand works.
>>>
>>> 1) Is this the right place to work on OS X GUI-specific issues?
>>> 2) What does the OS X dialog look for that could be missing? More
>>> IEEE-1284 info?
>>> 3) Is this documented publicly somewhere? I tried the CUPS documentation
>>> and Apple's OS X documentation.
>>>
>>> Thank you,
>>>
>>> Jacob Marble
>>> Google Los Angeles
>>>
>>
>>
>