Ok, there’s something to play with now for the very early adopters:
- Checkout Epiphany trunk (http://svn.gnome.org/svn/epiphany/trunk/)
- Apply the patch on bug 459333
- Checkout WebKit trunk (http://svn.webkit.org/repository/webkit/trunk)
- Build and install the GTK port:
- cd WebKit
- WebKitTools/Scripts/build-webkit –qmakearg=WEBKIT_INC_DIR=$PREFIX/include/WebKit –qmakearg=WEBKIT_LIB_DIR=$PREFIX/lib –gdk
- cd WebKitBuild/Release && make install
- For me the path to the pc file was broken and had to fix it in the Makefile, will open a bug tomorrow
- Compile Epiphany with –with-engine=webkit flag
- I didn’t say it would be easy
If everything succeeds you should be able to launch the browser and load URLs from the entry. Beware that the port is very basic, so almost nothing will work. A lot of work is needed both in ephy and webkit, if you want to help come to #epiphany at irc.gnome.org or #webkit at irc.freenode.org.
Some (IMHO) exciting ideas are on the backburner for WebKit-GTK, so stay tuned. The basic summary would be that this could become the really integrated browser GNOME deserves, down to the engine level.
PS: following the tradition of silly hackergotchies someone might want to use this for mine. Photo by the crazy Peruvian (aka Diego).
well, as I mentioned in the comments for the last post, gtk-webcore is in fact alive and well and under maintenance…
I don’t know the exact details of the relationship between the two but it would be a shame for there to be a split between gtk-webcore and this upstream gtk port of webkit, perhaps the status of the two should be clarified / resolved before too much work goes ahead?
The author of gtk-webcore hangs around the webkit channel and he seemed at least interested in cooperating with the upstream project, so I hope we’ll manage to work all together in the end.
Here’s one proposition for your hackergotchi :
You can find here a big version and also the XCF file so you can modify the shadow easily :
It was not easy because the color of the picture is really really bad.
Hope that you enjoy it.
Thanks! At last epiphany can be truly lightweight and start instantly as it should! Could you please measure and report us differences in startup time?
For me, once this is done, it is one step closer to throwing away the firefox bloat… (irrelevant, but improving epiphany tab handling (bug 110540) is another necessary step to take).
Woah, very nice!
Need to try it out and hopefully be able to fiddle some with integrating it in Devhelp at some point.
Keep it up!
Actually this one is quite better: http://www.flickr.com/photos/lucasrocha/831375401/
Actually you might need this line:
QTDIR=/usr/share/qt4 WebKit/WebKitTools/Scripts/build-webkit –qmakearg=WEBKIT_INC_DIR=$PREFIX/include/WebKit –qmakearg=WEBKIT_LIB_DIR=$PREFIX/lib
And to install libqt4-dev.
Some thought food related to the title of this entry.
First of all, thank you! Can’t wait to run epiphany on WebKit.
I tried building with diegoe’s instructions and apparently only the Qt backend is built (no WebKitGdk package found when building epiphany).
Ok, passing the –gdk option when building WebKit builds the GTK+ port instead. I now have Epiphany running against WebKit!
This is great, keep up the good work. 🙂
Ploum: thanks for the hackergotchi!
thebluesgnr: agh, sorry! the –gdk parameter was indeed missing it the instructions. Updated.
This is exactly what I expected to find out after reading the title o.us poetry. Thanks for informative article
These are some notes on my experience of building with Ephy with WebKit, in case they are helpful to others:
Pingback: Compilare e installare Epiphany con backend WebKit, o quasi « pollycoke :)
Pingback: GNOME 2.19.6 « TuxLinux…. La combriccola del pinguino
Pingback: Gnome 2.19.6 « Note su LINUX
Pingback: GNOME 2.19.6