[Printing-architecture] REMINDER: Project ideas for the Google Summer of Code 2009

[Printing-architecture] REMINDER: Project ideas for the Google Summer of Code 2009

[Till Kamppeter]

Hi,

I will do the application for the Linux Foundation as mentoring 
organization in the Google Summer of Code again.

Here is our project ideas list:

https://www.linuxfoundation.org/en/Google_Summer_of_Code_2009

Please add also your project ideas. The more we have the better our 
chances to get accepted as mentoring organization again (note that they 
will accept less mentoring organizations and students this year). There 
are only project ideas for OpenPrinting yet. Please add a section for 
your workgroup if there is none yet.

Deadline for our application is March 13. Please have your ideas posted 
some days before.

More info about the Google Summer of Code:

http://code.google.com/soc/
http://code.google.com/opensource/gsoc/2009/faqs.html

The FAQs (second link) describe the whole procedure with complete timeline.

Feel free to ask me in case of any question.

I also need a co-administrator, who will replace me if I am not 
available during the GSoC. Volunteers please mail.

    Till

Re: [Printing-architecture] REMINDER: Project ideas for the GoogleSummer of Code 2009

[Till Kamppeter]

George Liu wrote:
> The attached picture shows my understanding of the phase 1 of Common
> Print Dialog Project. 
> Is my understanding correct? The yellowish color section done by Lars?

Yes, it is exactly that. Lars is currently working on it. He is patching 
the toolkits to get the D-Bus interface in.

Lars, what is your progress on that?

The CPDAPI 2.0 (the preview support) is subject of the Google Summer of 
Code 2009. Students should implement the preview in the GTK and Qt 
implementations of the dialog and they should patch applications to use 
the D-Bus interface directly.

    Till

Re: [Printing-architecture] REMINDER: Project ideas for the GoogleSummer of Code 2009

[Till Kamppeter]

George Liu wrote:
>> Lars is ... patching the toolkits to get the D-Bus interface in.
> 
> 1. Does it mean that the GTK+ Print dialog portion will be moved out of GTK+ library and be build into a utility (stand alone program)?

The print dialog will stay in GTK+. There will only get the D-Bus 
interface inserted so that the GTK+ dialog can easily get replaced by 
another dialog.

> 2. Does GTK+ tool kit currently depends on D-Bus(libdbus)?

I don't know. Perhaps it uses D-Bus already for other things.

> 3. What if there's no D-Bus Daemon on the distribution (Nokia Tablet, which uses Gtk+ tool kit, for example). Any fall-back solutions?

The D-Bus part will be ptional. You will be able to build GTK+ with and 
without D-Bus. Or there will be a fallback. If the dialog is called and 
no dialog gets found via D-Bus one could do a fallback to the native 
GTK+ dialog.

> 4. How to register my CPDAPI server application with D-Bus? (Switch from gtk+ print dialog to QT print dialog, for example)

Here I cannot help. Lars? Can you answer this question?

    Till

Re: [Printing-architecture] REMINDER: Project ideas for the GoogleSummer of Code 2009

[Lars Uebernickel]

On Fri, 2009-02-27 at 16:49 -0300, Till Kamppeter wrote:
> George Liu wrote:
> >> Lars is ... patching the toolkits to get the D-Bus interface in.
> > 
> > 1. Does it mean that the GTK+ Print dialog portion will be moved out of GTK+ library and be build into a utility (stand alone program)?
> 
> The print dialog will stay in GTK+. There will only get the D-Bus 
> interface inserted so that the GTK+ dialog can easily get replaced by 
> another dialog.
> 
> > 2. Does GTK+ tool kit currently depends on D-Bus(libdbus)?
> 
> I don't know. Perhaps it uses D-Bus already for other things.
> 
> > 3. What if there's no D-Bus Daemon on the distribution (Nokia Tablet, which uses Gtk+ tool kit, for example). Any fall-back solutions?
> 
> The D-Bus part will be ptional. You will be able to build GTK+ with and 
> without D-Bus. Or there will be a fallback. If the dialog is called and 
> no dialog gets found via D-Bus one could do a fallback to the native 
> GTK+ dialog.
> 
> > 4. How to register my CPDAPI server application with D-Bus? (Switch from gtk+ print dialog to QT print dialog, for example)
> 
> Here I cannot help. Lars? Can you answer this question?

The CPDAPI server will not run all the time. Instead, it will make use
of D-Bus' service feature, which starts a process when a specific
interface has been requested by a client application. In order to
register such a service, a .service file needs to be put
into /usr/share/dbus-1/services (on ubuntu, this might differ a bit for
other distributions).

In the CPDAPI case, it might look something like this:

  [D-Bus Service]
  Name=com.openprinting.PrintManager
  Exec=/usr/bin/cpd-dialog-gtk

Changing the dialog is simply a matter of changing the 'exec' line.

    Lars