Epiphany + Webkit
July 17, 2007 6:17 pm General
As jdub would say: crack now, analysis later.
Search
Last Posts
- WebKitGTK+ Hackfest 2009
- Together we can rule the Galaxy – Epiphany 2.28 and WebKitGTK+ 1.1.15.x
- A GDB public service announcement
- WebKitGTK+ 1.1.14 new features
- The show so far
- I love this plan. I’m excited to be a part of it. Let’s do it!
- ECMAScript 5
- Two releases for the price of one
- WebKitGTK+ a11y (virtual) hackfest
- WebKitGTK+ 1.1.4
- Good news, everyone
- WebKitGTK+ 1.1.1
- Science fiction online
- See no long time
- History Meme
- Joining LiTL
- Epiphany ♥ WebKit
- Leaving Nokia
- Advancements in GTK+-flavored Web Engines
- The Facts in the Case of Mr. Epifanio Navegared
July 17th, 2007 at 7:21 pm
Nice.
Since people keep asking me why I don’t use WebKit for Jackfield, I suppose I should look at webkit now
July 17th, 2007 at 7:24 pm
oh my
July 17th, 2007 at 8:32 pm
I love it when a plan comes together!
July 17th, 2007 at 9:12 pm
Fantastic! I truly so want Epiphany to be the browser I know it can be! It really should be the Safari of Gnome (webkit references aside).
Let the next few months be the months of Epiphany and desktop integration!
July 17th, 2007 at 11:11 pm
What’s so exciting about this, except for the gtkhtml integration? Gecko-based epiphany already was able to draw web pages….
July 18th, 2007 at 12:36 am
Diego: It’s not gtkhtml, it’s WebKit…
July 18th, 2007 at 6:52 am
gtk-webkit needs far less memory than gecko.
July 18th, 2007 at 12:38 pm
Webkit is meaner and leaner alright. That alone perhaps wouldn’t be worth the fuzz but it also makes it possible separating plugins (flash, totem-plugin, and all the others) that crash or have other sorts of problems from the browser. That kids, means a level of stability never seen by Firefox users!
Also I have understood that it is easier to work with and customize it for the actual browser. I took couple nights ago some time to read through all open epiphany bugs from bugzilla (uhh lol) and a few of the really hard ones to solve will become very easy to solve with webkit if I understood correctly. Gecko is just retarded in couple areas.
July 18th, 2007 at 1:54 pm
[...] Non posso comunque esimermi da riportare che, come segnalato da Pollycoke, Epiphany userà Webkit. [...]
July 18th, 2007 at 3:31 pm
I’ll buy “lighter and faster.” More stable, though? That certainly hasn’t been my experience. I’ve had Safari crash on me far more than Camino and Firefox recently. I also don’t understand the idea that Webkit allows separating plugins from the browser. I thought Firefox already did that.
If the Webkit codebase is in better shape than Gecko, that could be a huge advantage. I also like the idea of getting rid of Firefox as a dependency for Epiphany, whether it be through Webkit or XULRunner.
July 18th, 2007 at 3:39 pm
I’m looking forward to Epiphany based on Webkit. The KDE, GNOME and Mac OS X would share the same light engine. Gecko is too powerful and overloaded in some cases (and in some cases it has no functionalis that Webkit/KHTML has).
July 18th, 2007 at 5:15 pm
… and there was much rejoicing.
July 18th, 2007 at 5:59 pm
[...] permalink Gut, eigentlich keine News, aber ich denke schon, dass es eine Erw
July 18th, 2007 at 8:17 pm
“I’ve had Safari crash on me far more than Camino and Firefox recently.”
Konqueror folks might disagree on that.. It’s not webkit’s fault usually.
July 18th, 2007 at 8:42 pm
BTW, is this using gtk-webcore – http://gtk-webcore.sourceforge.net/ – or upstream webkit or what?
July 18th, 2007 at 11:12 pm
It’s using the upstream WebKit gtk port.
July 19th, 2007 at 2:35 am
what’s the plus / minus of that versus gtk-webcore?
July 19th, 2007 at 6:29 am
The plus is that the upstream WebKit is actually maintained.
July 19th, 2007 at 3:28 pm
so’s gtk-webcore. check SVN. the lead maintainer – Kimmo Kinnunen at Nokia – is very responsive to bug reports, I’ve found: since packaging gtk-webcore and midori in Mandriva I’ve passed on several crasher reports to him and they’ve been fixed very promptly. yesterday I reported a build failure with GTK+ 2.11 and it was fixed this morning.
July 19th, 2007 at 10:42 pm
Part of this blog’s name (”iocane”) it’s not considered a good word here in Florence… LOL
July 24th, 2007 at 7:48 am
This is exactly what I expected to find out after reading the title o.us poetry. Thanks for informative article
July 24th, 2007 at 12:32 pm
Bravo!
July 24th, 2007 at 7:04 pm
[...] der erfolgreichen Portierung des Epiphany-Browsers auf das WebKit steht nun offenbar eine Reunion von KHTML und WebKit bevor. Logischerweise würde das bedeuten, [...]
July 24th, 2007 at 7:44 pm
I hope that epiphany will get the alternative non-gecko browser that I’ve been waiting for. Konqueror is nice, but I don’t like the integrated Filebrowser.
July 24th, 2007 at 11:47 pm
[...] (
July 29th, 2007 at 1:38 am
“Konqueror is nice, but I don’t like the integrated Filebrowser”
Perhaps you mean the integreated File _Manager_.
All browsers will browse files.
July 29th, 2007 at 1:40 am
July 30th, 2007 at 8:41 pm
I hope to see this working sooner rather than later, now that the Firefox folks are showing themselves to be a bunch of AHoles. Want to move away from Firefox soon.
July 30th, 2007 at 10:44 pm
[...] experimental WebKit back-end was added by Xan Lopez during the GNOME conference. Read all about it here. Fer also blogged about it and it was even mentioned in an article on Ars [...]