Am Mittwoch, 14. Dezember 2005 19:56 schrieb Till Kamppeter: Hi Till,
> The added one can depend on CUPS and new GTK, if these > libraries are not present (for example when building on old Red Hat) the > old dialog is used, on current distros the new one (could be > automatically built appropriately by checks in ./configure script). This is the half baked solution and the full baked solution will be more like Portland/RUDI. Why? Because RUDI will make sure that Firefox will not look like a 2nd class citizen on KDE and avoids the need for Firefox to add dependencies to both a special new GTK version or CUPS. IMHO CUPS is a perfect example of a _service_ which happens to also provide a client library. It is a bad design decision for an application to directly link to the cups client library (ABI concerns,...) but it is much better to use a protocol based interface to use the full potential of CUPS. It is the job os some middleware like RUDI to provide the service to the applications in a transparent and ABI agnostic way. In case RUDI is not available for any reason the application shall fall back to the generic/vintage dialog. It is the job of the RUDI platform libary to help the application to achieve the later with as little pain as possible. Regards, -- martin -- http://www.erfrakon.com/ Erlewein, Frank, Konold & Partner - Beratende Ingenieure und Physiker _______________________________________________ Desktop_architects mailing list Desktop_architects@lists.osdl.org https://lists.osdl.org/mailman/listinfo/desktop_architects