On Fri, Apr 23, 2010 at 12:54 AM, Darin Fisher da...@chromium.org wrote:
On Tue, Apr 20, 2010 at 10:53 AM, Peter Kasting pkast...@google.comwrote:
On Tue, Apr 20, 2010 at 1:26 AM, Patrick Roland Gansterer
par...@paroga.com wrote:
Bradley Nelson:
1. Ability to incrementally transition
On 26.04.10 22.16, Andras Becsi wrote:
As far as I know QtWebKit uses this keyword to indicate that the
corresponding bug has been checked and prioritized based on its severity
by a triaging group of two QtWebKit developers.
https://trac.webkit.org/wiki/QtWebKitBugs#Triagingbugs
That's
Hello,
I am implementing XML3D http://www.xml3d.org/ format into WebKit. I have a
number of new elements that I have added to a separate namespace. Root
element is xml3d and it's the only one who has a renderer. Every child
that is attached to the subtree of this element should notify parent
27.04.2010, в 00:56, Tor Arne Vestbø написал(а):
As far as I know QtWebKit uses this keyword to indicate that the
corresponding bug has been checked and prioritized based on its severity
by a triaging group of two QtWebKit developers.
https://trac.webkit.org/wiki/QtWebKitBugs#Triagingbugs
If you want to set the flags manually, you should write CXXFLAGS+=...
instead of CXXFLAGS=.
However, the first method what you tried is right, so if it is crashing
then smg wrong with the JIT.
What platform (Architecture, OS, qt-version) do you use?
On 04/27/2010 05:41 PM, Nyx wrote:
I am
Hi,
Yes, I have tried this on several versions of Ubuntu, including Lucid.
I don't have Windows machine so I can't try that. There is not a single
instance of a QtWebKit browser (or my own snippet of QtWebKit code) that works
- and 100% of every GtkWebKit browsers (and my own snippet of
Sorry, I wasn't clear. My probems are all on Ubuntu Linux - both in Jaunty and
Lucid - with all QtEbkit-based browsers. what is http://doobie.sf.net;? A
QtWebkit-based browser? Is it open-source?
Cheers,
---AK
From: Max petersonm...@googlemail.com
To:
If you want to set the flags manually, you should write CXXFLAGS+=...
instead of CXXFLAGS=.
Thanks. I will be trying that.
However, the first method what you tried is right, so if it is crashing
then smg wrong with the JIT. What platform (Architecture, OS, qt-version)
do you use?
Ubuntu
Here's the prototype I made during the hackathon that simply uses a bunch of
Javascript to make it easier to type up comments:
http://ascherkus.appspot.com/bugzilla/index.html
I'm not a WebKit reviewer, but from what I gathered during the session
there's a lot of copying and pasting involved. I
On Thu, Apr 22, 2010 at 1:13 PM, Adam Roben aro...@apple.com wrote:
On Apr 22, 2010, at 4:01 PM, Darin Adler wrote:
- The comments all cite only a single line of the patch and I almost
never have a comment that's for a single line. So I have to do a lot of
editing, pretending to comment on
On 4/27/2010 5:38 PM, ext Alexey Proskuryakov wrote:
27.04.2010, в 00:56, Tor Arne Vestbø написал(а):
As far as I know QtWebKit uses this keyword to indicate that the
corresponding bug has been checked and prioritized based on its severity
by a triaging group of two QtWebKit developers.
On Tue, Apr 27, 2010 at 9:14 AM, Phoenix Revived
phoenixrevi...@yahoo.com wrote:
Yes, I have tried this on several versions of Ubuntu, including Lucid.
I don't have Windows machine so I can't try that. There is not a single
instance of a QtWebKit browser (or my own snippet of QtWebKit code)
I've renamed Triaged to QtTriaged.
Dave
- Original Message
From: Jocelyn Turcotte jocelyn.turco...@nokia.com
To: webkit-dev@lists.webkit.org
Sent: Tue, April 27, 2010 10:02:36 AM
Subject: Re: [webkit-dev] Bugzilla Triaged keyword
On 4/27/2010 5:38 PM, ext Alexey Proskuryakov
On 04/27/2010 07:02 PM, Nyx wrote:
If you want to set the flags manually, you should write CXXFLAGS+=...
instead of CXXFLAGS=.
Another way would be to set export QMAKEARGS=$QMAKEARGS
DEFINES+=ENABLE_JIT=0 before building.
However, the first method what you tried is right, so if it is
Another way would be to set export QMAKEARGS=$QMAKEARGS
DEFINES+=ENABLE_JIT=0 before building.
Will try it too.
That is strange. Did you checkout the source from svn? Did you mess
around in the code?
Yes. I checked it out last night from the trunk.
--
View this message in context:
Another way would be to set export QMAKEARGS=$QMAKEARGS
DEFINES+=ENABLE_JIT=0 before building.
Ok. I tried this approach. I have a build script that looks like this:
QTDIR=/usr/share/qt4/
export QMAKEARGS=$QMAKEARGS DEFINES+=ENABLE_JIT=0
WebKit/WebKitTools/Scripts/build-webkit --qt
It builds,
On Apr 27, 2010, at 2:10 PM, Nyx wrote:
I also tried adding #define ENABLE_JIT 0 at the top of the Interpreter.cpp
file in JavaScriptCore. This builds, but produces a segmentation fault.
This would not work as you would end up with some parts of WebKit compiled with
the jit enabled, and some
In WebCore/platform/image-
decoders/jpeg/JPEGImageDecoder.cpp (
https://trac.webkit.org/browser/trunk/WebCore/platform/image-decoders/jpeg/JPEGImageDecoder.cpp)
and png/PNGImageDecoder.cpp, setjmp and longjmp are called. This causes this
code unportable to Windows environment. At
Hi, I'm working on a project which makes use of JavaScriptCore as a
scripting engine outside of WebKit. It would be very helpful to us if
we could get access to the DOMParser and XMLSerializer classes which are
in WebKit's DerivedSources area. However, it seems that those libraries
are using
DerivedSources are generated from here:
http://trac.webkit.org/browser/trunk/WebCore/DerivedSources.make
I think what your'e thinking of as DerivedSources is actually just the
javascript bindings, which will be useless to you w/o the actual
implementations in WebCore.
If for some reason you
Thanks. I apologize for mincing terminology - I'm not particularly
versed in how WebKit is put together, where WebKit ends and
JavaScriptCore begins, etc., and I've mostly been banging my head
against this based on looking at work that some of my coworkers have
done. :)
I should be more
Various WebKit ports expose different bindings. The JS bindings are
only exposed to scripts on pages run inside WebKit.
If you have your own separate javascript environment, you would need
to set up your own custom bindings for that environment. We don't
really provide clean APIs for that,
Okay, that's what I was afraid of. For now I think I'll just write
bindings against libxml, then. Thanks.
Eric Seidel wrote:
Various WebKit ports expose different bindings. The JS bindings are
only exposed to scripts on pages run inside WebKit.
If you have your own separate javascript
On Tue, Apr 27, 2010 at 2:33 PM, SCU Rock scur...@gmail.com wrote:
In WebCore/platform/image-
decoders/jpeg/JPEGImageDecoder.cpp (
https://trac.webkit.org/browser/trunk/WebCore/platform/image-decoders/jpeg/JPEGImageDecoder.cpp)
and png/PNGImageDecoder.cpp, setjmp and longjmp are called.
24 matches
Mail list logo
