Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-03 Thread Martin Robinson
On Thu, May 2, 2013 at 12:19 PM, Niranjan Rao wrote: > I chatted with mrobinson yesterday (thank you mrobinson) and he did explain > some more things which clarified my current problem a bit more. However > issue still remains that moving from 1.* to 2.* is going to be lot more > complicated. C

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-02 Thread Niranjan Rao
On 05/02/2013 12:57 AM, Sergio Villar Senin wrote: En 02/05/13 02:59, Eric Gregory escribiu: On Wed, May 1, 2013 at 5:41 PM, Martin Robinson mailto:martin.james.robin...@gmail.com>> wrote: A WebPage corresponds to a WebView, but on the WebProcess side. The C API exposes frames, but w

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-02 Thread Eric Gregory
On Thu, May 2, 2013 at 12:57 AM, Sergio Villar Senin wrote: > This was already explained during the 2.x development process. In the > new multiprocess architecture, the DOM tree lives in the WebProcess > while your application is the UIProcess. Synchronous communication > between both (as DOM bind

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-02 Thread Martin Robinson
On Thu, May 2, 2013 at 8:28 AM, Christian Betz wrote: > If i'm understanding things correctly from looking at the epiphany > plugin: It looks like I will be creating a plugin that runs in the > WebProcess and sends dbus messages to my main gtk process (or some > other process). what exactly is mi

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-02 Thread Christian Betz
On Wed, May 1, 2013 at 8:41 PM, Martin Robinson wrote: > On Wed, May 1, 2013 at 5:32 PM, Eric Gregory wrote: >> Taking a quick look at the new API, WebFrame has been replaced by WebPage, >> which has a method to get the DOMDocument object: >> http://webkitgtk.org/reference/webkit2gtk/stable/WebKi

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-02 Thread Martin Robinson
On Wed, May 1, 2013 at 5:59 PM, Eric Gregory wrote: >> A WebPage corresponds to a WebView, but on the WebProcess side. The C >> API exposes frames, but we have not exposed them in the GObject API >> because we aren't sure if they will continue to be part of the >> internal UIProcess API. That dec

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-02 Thread Sergio Villar Senin
En 02/05/13 02:59, Eric Gregory escribiu: > On Wed, May 1, 2013 at 5:41 PM, Martin Robinson > > wrote: > > > A WebPage corresponds to a WebView, but on the WebProcess side. The C > API exposes frames, but we have not exposed them in the GObject API

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Eric Gregory
On Wed, May 1, 2013 at 5:41 PM, Martin Robinson < martin.james.robin...@gmail.com> wrote: > > A WebPage corresponds to a WebView, but on the WebProcess side. The C > API exposes frames, but we have not exposed them in the GObject API > because we aren't sure if they will continue to be part of the

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Martin Robinson
On Wed, May 1, 2013 at 5:32 PM, Eric Gregory wrote: > Taking a quick look at the new API, WebFrame has been replaced by WebPage, > which has a method to get the DOMDocument object: > http://webkitgtk.org/reference/webkit2gtk/stable/WebKitWebPage.html#webkit-web-page-get-dom-document A WebPage cor

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Martin Robinson
On Wed, May 1, 2013 at 3:50 PM, Eric Gregory wrote: > Does this method work even when Javascript is disabled? Seems like the docs > should mention that. Thanks for pointing that out. Should be fixed @ http://trac.webkit.org/changeset/149467. --Martin ___

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Eric Gregory
On Wed, May 1, 2013 at 5:13 PM, Niranjan Rao wrote: > Not really. If you use release 2, as far as I can see, you can not get > frames. Its available in release 1. This is to say if you include > webkit2.h, my understanding is these functions are not available. > Taking a quick look at the new A

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Niranjan Rao
Not really. If you use release 2, as far as I can see, you can not get frames. Its available in release 1. This is to say if you include webkit2.h, my understanding is these functions are not available. http://webkitgtk.org/reference/webkit2gtk/stable/WebKitWebView.html Javascript is good e

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Eric Gregory
On Wed, May 1, 2013 at 3:23 PM, Brendan Long wrote: > Using WebKit2, you can run arbitrary JavaScript: > > > http://webkitgtk.org/reference/webkit2gtk/stable/WebKitWebView.html#webkit-web-view-run-javascript > Does this method work even when Javascript is disabled? Seems like the docs should

Re: [webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Brendan Long
Isn't the WebKit1 API still available? It looks like webkit_web_frame_get_dom_document() is still there: http://webkitgtk.org/reference/webkitgtk/stable/WebKitWebFrame.html#webkit-web-frame-get-dom-document Using WebKit2, you can run arbitrary JavaScript: http://webkitgtk.org/reference/webkit2g

[webkit-gtk] Webkit GTK Release 2 - basically unusable for us

2013-05-01 Thread Niranjan Rao
Greetings, I certainly hope that I am wrong with my dramatic subject line, but this is the feeling I am getting right now. Its not my intention to start a flame war as I have great respect for amount work webkit gtk team puts in. However these are (possibly incorrect) observations I have for t