On Wednesday 18 May 2011 08:26:34 Johannes Meixner wrote:
Yes, this is why I do not understand why there is not much more interest in the Common Printing Dialog.
The thing is the print dialog is only one part of the print system, there's the whole process of painting the output into the required output format, and cross-platform support too. The CPD only helps with the dialog itself and sending the print file to Cups (i.e. Linux only), so there is still a lot of code there to be filled by something. Gtk, Qt, KDE, and all the stand-alone apps that do their own dialog still need to solve those other problems themselves.
I would expect a strong demand from the desktop projects and from various application projects to have a Common Printing Dialog.
There is strong demand, but unfortunately I think there's been a lot of miscommunication and misunderstanding of what the toolkits/desktops require and what OpenPrinting can/should provide. The impression that OpenPrinting got that we just wanted patches for a finished product was unfortunate as I think it lead them down an implementation dead-end where they thought a single shared implementation with a non-HIG compliant appearance would be accepted by everyone.
If there was a strong demand from various projects to have it, it would be at least much easier for Till Kamppeter to get it funded when there are no volunteers who implement it.
Without strong and noticeable interest by various projects I have little hope that there will be a Common Printing Dialog.
In it's current form I think the dialog is dead, but I'm hopeful that OP will instead finish the underlying tools and api definitions and define common standards that the toolkits/desktops/apps can then implement a native dialog on top of. It's something I need to write to the OP list about more. John. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org