Re: webkit integration in the xwidget branch

[Julien Danjou <julien@danjou.info>]

[-- Attachment #1: Type: text/plain, Size: 1167 bytes --]

On Tue, Jun 28 2011, joakim@verona.se wrote:

> I did a proof of concept webkit xwidget in the xwidget branch.

I'm glad to read that.

> pros:
> - shows tighter webkit integration is indeed possible and that the
> xwidget branch is a pretty cool playground

:-)

> cons:
> - well, webkit doesnt have an out of the box mvc model. I find it
> perplexing that state of the art web engines in 2011 cant even do a 1990s
> type split pane view. I did some brief research around this mysterious
> ommission and found odd references in wikipedia that this might be
> covered by a patent or something. I hope I'm just having a bad dream.

What does that means when using it, concretely? I don't know what model
WebKit uses if it's not MVC, so what's wrong conretely?
(maybe I should take a look at the WebKit API :-)

> Links like these:
> http://www.chromeplugins.org/plugins/google-chrome-dual-view/
> makes me think time stands still. Which is good news for us Emacsers I
> suppose.

In such a context, I tend to argue that this kind of the work of the
window manager to organize windows.

-- 
Julien Danjou
❱ http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]