[cups.development] Re: CUPS and LSB

[Fujinaka, Todd]

....

>> So, what I have to ask is whether my assumptions are correct from the
>> docs I've read on cups.org. Is libcups what I'd use for a
>> higher-level interface?
>
>Both libcups and libcupsimage are required - libcups is the
>application-level interface and libcupsimage is used for printer
>drivers.  Both would need to be included to be really useful - think
>drivers from the printer manufacturers...
>
> > Is cups.h where I find the interfaces to include?
>
>You'll want to include all of the headers in the cups subdirectory.
>"cups.h" is just the "include everything + define the convenience
>functions" header file.
>
>As for the interfaces to include, you'll want to include all of
>the functions that do not start with an underscore (those are
>private APIs) and are not marked deprecated (via GCC attribute).

I have been looking at the interfaces in cups and what I'd like to do,
if possible, is to trim the list down to what an "average" application
would use for printing. So, I'm wondering if I can omit backends, HTTP
and IPP, for example. I must admit that I'm not sure which of the APIs
are used by client applications, but limiting the number of interfaces
also reduces the testing we have to do on our side to see whether the
distros are providing the proper APIs.

Also, has any work been done to change filter/image-png.c to use the
png_get_ and png_set_ syntax entirely to avoid direct access of the
png_info_struct? I edited the file directly and can send patches, but I
haven't gotten everything compiled yet, so I'm not sure it's correct.

Thanks,
Todd