Re: Merging conduit-gio branch

["John Stowers" <john stowers gmail com>]

On Thu, Aug 28, 2008 at 12:03 PM, John Stowers <john stowers gmail com> wrote:

Hi Guys,

Its taken a few weeks longer than expected, but I think the conduit-gio branch [1] is ready for merge, probbably tonight or tomorrow. I wanted to get it done before the GNOME beta, but things got in the way, mostly the fact I have been unable to push to bzr-playground for about two weeks.

This has now landed. Can those running on a bleeding edge system, with recent releases of pygobject (with GIO support) please test.

To test uninstalled you should call conduit like the following

CONDUIT_FILE_IMPL=GIO ./conduit/conduit

And preferably, if you also have pywebkitgtk installed

CONDUIT_BROWSER_IMPL=webkit CONDUIT_FILE_IMPL=GIO ./conduit/conduit.real

 John

Basically this splits out all file/vfs/file monitor/volume monitor tasks into platform specific implementations. There are currently two implementations of the appropriate interfaces; a gnomevfs one, and a gio one. After the merge, I will do some more testing on trunk, and then flip the switch to make Conduit use GIO once the next releases of pygobject and gio have been made.

There are no public facing API changes, and all tests pass with the gnomevfs implementation. I still have to finish the VolumeMonitor GIO implementation.

Those that wish to test the new code should change the appropriate line in conduit/__init__.py

I will send out another email later this week with a note to distributors on how to package Conduit. Basically, if your distro ships new pygobject (with GIO support), and pyswebkitgtk, you should make the appropriate mods in conduit/__init__.py.

John

[1] http://bzr-playground.gnome.org/~jstowers/conduit/conduit-gio/ (ignore the fact there has been no commits in months, stupid bzr has locked me out)