Hi,
Is it possible to display a QWidget on DOM (Div tag) using QtWebkit Bridge?
For this we do not want to override QWebView's paint method. This is
similar to NPAPI'S rendering, but utilizing QtWebkit Bridge.
Also, as per QtWebkit Bridge documentation, we can get DOM objects as
QWebElement in
Hi,
On Fri, Mar 25, 2011 at 12:53 PM, Chandan Apsangi chandan...@gmail.comwrote:
Is it possible to display a QWidget on DOM (Div tag) using QtWebkit
Bridge?
For this we do not want to override QWebView's paint method. This is
similar to NPAPI'S rendering, but utilizing QtWebkit Bridge.
Hi Brent,
I definitely agree that gyp is rather undocumented and kind of hard to
use. It's nowhere near the level of documentation of CMake, let alone
Xcode or GNU makefiles. Hopefully we can fix this in the near future.
That said, I'd be kind of surprised if cmake was already installed on
your
Hello WebKit developers,
I've created a draft blog post at http://www.webkit.org/blog/?p=1580 about
the recent changes I and others have made to the UA string. I'm interested
in any feedback you might have.
I've written a similar blog post, but focused on Chrome and aimed at a wider
audience,
On Fri, Mar 25, 2011 at 10:50 AM, Peter Kasting pkast...@google.com wrote:
I've created a draft blog post at http://www.webkit.org/blog/?p=1580 about
the recent changes I and others have made to the UA string. I'm interested
in any feedback you might have.
Note, since this is a draft, you
In addition to your comments, I also find the gyp syntax somewhat unpleasant.
In particular, in .gypi lists of files to compile, ever entry is double-quoted,
comma-separated, line-separated, and then grouped in multiple levels of braces.
This is noisier than any of our current formats except
On Mar 25, 2011, at 1:53 PM, Peter Kasting wrote:
UA String Changes On WebKit Trunk
Posted by Peter Kasting on Friday, March 25th, 2011 at 10:44 am
Recently some changes to the UA string (tracked by
https://bugs.webkit.org/show_bug.cgi?id=54556) have landed. These changes
are designed to
Hi Peter,
I think you should say User Agent String in the title and maybe in
the first paragraph say User Agent (UA) string, so that it's not
quite as cryptic.
The inline URLs are a bit ugly, perhaps some changes could be turned
into a link to the tracking bug and similar changes in Firefox 4
If you take a look at
http://trac.webkit.org/browser/trunk/Source/WebKit/wince/WebCoreSupport/FrameLoaderClientWinCE.cpp#L57
I’m not sure if point 5 is correct. ;-)
The WinCE port has still my initial UA string for testing.
- Patrick
_
From: webkit-dev-boun...@lists.webkit.org
On Fri, Mar 25, 2011 at 11:05 AM, Patrick R. Gansterer par...@paroga.comwrote:
If you take a look at
http://trac.webkit.org/browser/trunk/Source/WebKit/wince/WebCoreSupport/FrameLoaderClientWinCE.cpp#L57I’m
not sure if point 5 is correct. ;-)
The WinCE port has still my initial UA string
I've incorporated all the existing feedback into the draft. Feel free to
take another look.
PK
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
The blog post begs the question made me wonder.
Why was Macintosh; kept when it is redundant with Intel Mac OS X
10_6_7?
The reasoning seem analogous to what was given for why Windows; was
removed.
dave
On Fri, Mar 25, 2011 at 11:44 AM, Peter Kasting pkast...@google.com wrote:
I've
Ugh my strikethrough on begs the question was lost (and I meant that
phrase as a joke).
On Fri, Mar 25, 2011 at 11:54 AM, David Levin le...@google.com wrote:
The blog post begs the question made me wonder.
Why was Macintosh; kept when it is redundant with Intel Mac OS X
10_6_7?
The
WinCE port is not dead, but I don't have much time to implement/upstream new
features at the moment :-(
I filed bug 57111 and will post a patch.
- Patrick
_
From: Peter Kasting [mailto:pkast...@google.com]
Sent: Friday, March 25, 2011 7:41 PM
To: Patrick R. Gansterer
Cc:
On Fri, Mar 25, 2011 at 11:54 AM, David Levin le...@google.com wrote:
The blog post begs the question made me wonder.
Why was Macintosh; kept when it is redundant with Intel Mac OS X
10_6_7?
The reasoning seem analogous to what was given for why Windows; was
removed.
Unlike Windows, the
On Fri, Mar 25, 2011 at 11:44 AM, Peter Kasting pkast...@google.com wrote:
I've incorporated all the existing feedback into the draft. Feel free to
take another look.
Since some folks seem to be unable to see the draft even while logged in,
here's the new fulltext.
PK
---
User Agent
On 2011-03-25, at 12:07, Peter Kasting wrote:
On Fri, Mar 25, 2011 at 11:44 AM, Peter Kasting pkast...@google.com wrote:
I've incorporated all the existing feedback into the draft. Feel free to
take another look.
Since some folks seem to be unable to see the draft even while logged in,
On Fri, Mar 25, 2011 at 12:54 PM, Mark Rowe mr...@apple.com wrote:
Is there some reason why these examples use manufactured Safari build
numbers? It's implausible that a version of Safari with a build number of
534.24 would ever claim to be version 5.0.3.
Sorry, I wasn't sure what the right
On 2011-03-25, at 12:56, Peter Kasting wrote:
On Fri, Mar 25, 2011 at 12:54 PM, Mark Rowe mr...@apple.com wrote:
Is there some reason why these examples use manufactured Safari build
numbers? It's implausible that a version of Safari with a build number of
534.24 would ever claim to be
On Fri, Mar 25, 2011 at 1:03 PM, Mark Rowe mr...@apple.com wrote:
On 2011-03-25, at 12:56, Peter Kasting wrote:
On Fri, Mar 25, 2011 at 12:54 PM, Mark Rowe mr...@apple.com wrote:
Is there some reason why these examples use manufactured Safari build
numbers? It's implausible that a version
20 matches
Mail list logo
