[webkit-qt] QtScript dependency optional?

[Konstantin Tokarev]

I've found that QtWebKit does not actually depend on QtScript module (at least 
if configured without 
V8 support). 

The only thing actually used is enum QScriptEngine::ValueOwnership. If its 
definition is included into 
Source/WebCore/bridge/qt/qt_instance.h and WebKit/qt/Api/qwebframe.h, QtWebKit 
compiles fine if
QtScript module is disabled in Qt configuration.

Will it be OK if I add new header with the next code

#ifndef QT_NO_SCRIPT
#include QtScript/qscriptengine.h
#else
QT_BEGIN_NAMESPACE
namespace QScriptEngine {
enum ValueOwnership {
QtOwnership,
ScriptOwnership,
AutoOwnership
};
}
QT_END_NAMESPACE
#endif

This header needs to be public because it's needed for qwebframe.h

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] QtScript dependency optional?

[Konstantin Tokarev]

14.01.2011, 21:38, Benjamin Poulain benjamin.poul...@nokia.com:
 On 01/14/2011 07:30 PM, ext Konstantin Tokarev wrote:

  Long term QtWebKit will depends on QtScript for the bridge. To avoid
  inconsistencies and regressions, I think it would be more reasonable to
  guard the functions of the bridge with #ifndef QT_NO_SCRIPT.
  Do you mean it's OK to disable whole class QtInstance? (AFAIU, its main
  method is getQtInstance, and from your words it should be disabled)

 Yep, #ifdef the public methods, and do not compile the classes of the
 bridge.

I've submitted https://bugs.webkit.org/show_bug.cgi?id=52469
But Simon does not like this idea.
Or have I misunderstood something?

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] qtwebkit build issue

[Konstantin Tokarev]

28.01.2011, 23:57, luying pan luying@gmail.com:
 Thanks for the response. That only works the objects that are generated from 
 the same makefile, but I think my general problem is that my compiler is too 
 old. Do you know any ways to use gcc44 instead of gcc? I tried export 
 CC=gcc44 before running ./build-webkit -qt command, but that didn't help.



You can put any arguments fro qmake into build-webkit command line, e.g.


build-webkit --qt --minimal --makeargs=-j4 QMAKE_CXXFLAGS=\-Os 
-DQT_NO_GRAPHICSVIEW\  QMAKE_CXXFLAGS_RELEASE=-Os CONFIG-=release 
CONFIG-=debug QMAKE_CXX=\ccache g++\


But I think gcc 4.1.2 (you are on CentOS 5, right? :) should work for you, 
because even gcc 3.4 is known to build QtWebKit 
(http://doc.qt.nokia.com/latest/compiler-notes.html)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Removing support for Qt 4.6 on QtWebKit trunk

[Konstantin Tokarev]

22.02.2011, 20:15, Andreas Kling andreas.kl...@nokia.com:
 Heyo everyone,

 In preparing for the Qt 4.8 release, I will be removing support for
 building QtWebKit trunk against Qt 4.6, as we normally only support the
 latest two Qt versions.

 Are there any objections to this?

Could you specify Qt 4.7-only features you'd like to use?

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] git confusion - pull to update is merging entire tree

[Konstantin Tokarev]

24.04.2011, 16:31, Lindsay Mathieson lindsay.mathie...@gmail.com:
 I have a git clone of master (g...@gitorious.org:webkit/webkit.git)
 from a couple of weeks back. I've made some minor changes to several
 files in QtWebKit and QtTestBrowser, commited them and just tried to
 do a git pull to update from master.

It is not a good workflow - you should commit your changes to your topic branch
and then rebase it on master (or other upstream branch) if/when needed.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Feedback needed: new design for WebKit 2

[Konstantin Tokarev]

01.07.2011, 18:53, viatcheslav.ostape...@nokia.com:

  -simplify APIs to something minimal: QMobileWebView (the viewport) +
  QMobileWebPage (the view on the page) for mobile. QDesktopWebView as
  the only view for mobile.

 Mobile/Desktop - sounds odd. Who knows, where will be mobile or desktop soon. 
 Some phones are more powerful than other nettops ;)

But phones usually have smaller screens ;)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Almost all webkit LayoutTests failing on Qt for Embedded Linux

[Konstantin Tokarev]

26.07.2011, 16:28, Alexis Menard alexis.men...@openbossa.org:
 As far as I understood the way Qt For Embedded Linux stands today is
 dead/replace/deprecated with Lighthouse no?

Do you expect all embedded developers to switch to Lighthouse overnight
once Qt 4.8 is released?

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Please provide approx QtWebkit 2.2 and Qt 4.8 release dates.

[Konstantin Tokarev]

18.08.2011, 13:09, sunny shah sunny@gmail.com:
 Hi QtWebkit Team,Can you please provide approximate release dates of Qt 4.8 
 an QtWebkit 2.2 ?
 My usage is mainly for Linux and Embedded Linux, so let me know, If it is 
 stable for that two platforms.

We are using Qt 4.7.3 and QtWebKit 2.1.1 on embedded Linux, works fine.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Build Issues

[Konstantin Tokarev]

16.09.2011, 10:30, Konstantin Tokarev annu...@yandex.ru:
 16.09.2011, 03:44, Matt Cote atm1...@gmail.com:

  After the build fails I also have libQtWebKit.so.4.10 libs even though I'm 
 using 4.7.4.
  Any ideas?  Thanks in advance.

 It's OK because build failed on test building stage. It's also OK that .so 
 version does not match Qt version (.so.4.8 == QtWebKit 2.1, .so.2.9 == 
 QtWebKit 2.2)

I've meant .so.4.9 of course :)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Build Issues

[Konstantin Tokarev]

16.09.2011, 03:44, Matt Cote atm1...@gmail.com:
 After the build fails I also have libQtWebKit.so.4.10 libs even though I'm 
 using 4.7.4.
 Any ideas?  Thanks in advance.

It's OK because build failed on test building stage. It's also OK that .so 
version does not match Qt version (.so.4.8 == tWebKit 2.1, .so.2.9 == QtWebKit 
2.2)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Build Issues

[Konstantin Tokarev]

16.09.2011, 18:40, Matt Cote atm1...@gmail.com:
 Hi.  Any ideas about what would cause failure on test building?Also... I 
 can't seem to run the qt test browser after building because nothing seems to 
 be placed in the bin directory.
 [mcot@localhost WebKit-r95080]$ Tools/Scripts/run-launcher --qt
 Starting webkit launcher, running against the built WebKit in 
 /home/mcot/Downloads/WebKit-r95080/WebKitBuild/Release/lib...
 Can't exec 
 /home/mcot/Downloads/WebKit-r95080/WebKitBuild/Release/bin/QtTestBrowser: 
 No such file or directory at Tools/Scripts/run-launcher line 94.
 Died at Tools/Scripts/run-launcher line 94.
 I'm not sure I understand the relationships between the QT Version, QT Webkit 
 Version, and the version numbers on the shared object files after building qt 
 webkit.  Is there any document that explains the relationships between the 
 versions?

Starting from Qt 4.7, QtWebKit has separate versioning (QtWebkit from Qt 4.7 is 
2.0.0). Since than, every minor release (2.1, 2.2, etc.) increases minor 
version of so, which was equal to Qt so version in QtWebKit 2.0.0. Now so 
version of QtWebKit has no relation with underlying Qt.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] libxslt / xml support

[Konstantin Tokarev]

25.11.2011, 14:09, Simon Hausmann simon.hausm...@nokia.com:
 Hi,

 While we're at the topic of third-party libraries (ICU...), there's one other
 thing that I discussed with Andreas yesterday that might make sense for us
 regarding XSLT support:

 I'd like to propose that we remove the code that uses QtXmlPatterns to
 implement XSLT support in WebKit. Instead I'd like to make libxslt a
 dependency (now that we have configure tests) for anyone who wants to build
 QtWebKit with XSLT support.

 If XSLT support is enabled - and therefore libxslt available - we also get an
 implicit availability of libxml. I suggest that in that case we also use
 libxml for XML parsing.

 If XSLT support is _not_ enabled, we don't have libxslt and therefore also no
 libxml available and should continue to use QXmlStreamReader for XML parsing.

 Does that sound reasonable?

But it will bring two extra dependencies at once - libxslt and libxml2. Does 
anybody
here care about embedded systems?


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Updating Qt 4.8.0 with QtWebKit - time to get that last fix in

[Konstantin Tokarev]

25.11.2011, 17:38, benedikte.h...@nokia.com:
 Hi everyone,

 This is just a heads-up to let you know we're getting close to releasing Qt 
 4.8.0.
 If you have a QtWebKit bug fix you'd really like to see go into Qt 4.8.0, 
 there is a small window left for you to get it in.

 Please give us a heads-up if you have anything. Shortly we'll tag what we 
 have as QtWebKit 2.2.1 and pull that into Qt.

I'd like to see r88547 (git c4b8b668 in master) backported to 2.2 branch.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Confused re release process

[Konstantin Tokarev]

08.02.2012, 06:30, Alexis Menard alexis.men...@openbossa.org:
 On Tue, Feb 7, 2012 at 8:45 PM, Lindsay Mathieson
 lindsay.mathie...@gmail.com wrote:

  On Fri, 3 Feb 2012 12:34:44 PM you wrote:
  Have been away for a few months dealing with issues - floods etc :( so a
  little out of touch, please excuse my massive ignorance as to
  the release process.

  Back in August last year I and others commit a inline spellchecking mod to
  webkit:

  https://gitorious.org/+qtwebkit-developers/webkit/qtwebkit/blobs/qtwebkit-2.
  2/Source/WebKit/qt/Api/qwebkitplatformplugin.h

 It was too late to be able to make it for Qt 4.8 therefore QtWebKit
 2.2. This is why nothing has change in Qt or KDE. I don't think we'll
 have a new minor release of Qt 4 with QtWebKit so I don't think there
 is a way for your patch to make its way to KDE for example. Unless
 someone here step up to release a QtWebKit 2.3 with all the QA work it
 requires then it could find its way as a separate release and add-on
 of Qt 4.8.

Wait... There won't be QtWebKit releases for Qt 4.x anymore? What a pity!

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Qt 4.8/Webkit 2.2 no audio/video tag support

[Konstantin Tokarev]

10.02.2012, 03:20, Carlos Smith csm...@stonewedge.net:
 People have been asking on the Qt forums with no help, so maybe I’ll have 
 better luck here.

 Does anyone know why the audio and video tags are not supported in Qt 
 4.8/QtWebkit 2.2, at least on Windows?

 The QtWebKit pages on webkit.org say this version of Webkit supports those 
 tags.  Yet in practice they do not work.  Does anyone have any information or 
 insight into this?

Are you building with build-webkit script, or within Qt?

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] QtWebKit Linking Error On Ubuntu

[Konstantin Tokarev]

10.02.2012, 15:10, rakesh sadhu peerpan...@gmail.com:
 Hi,
 I'm trying to build debug qtwebkit on linux ubuntu 10.10 32-bit version .
 I am getting error while linking .
 Kindly help , I don;t want to change my OS version from 32 to 64 bit.

You can install 64-bit kernel and gcc while keeping 32-bit userland.
If it was Debian you could easily do it using official repositories.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] QtWebKit Linking Error On Ubuntu

[Konstantin Tokarev]

10.02.2012, 15:49, Osztrogonac Csaba o...@inf.u-szeged.hu:
 Hi,

 Konstantin Tokarev írta:

  10.02.2012, 15:10, rakesh sadhu peerpan...@gmail.com:
  Hi,
  I'm trying to build debug qtwebkit on linux ubuntu 10.10 32-bit version .
  I am getting error while linking .
  Kindly help , I don;t want to change my OS version from 32 to 64 bit.
  You can install 64-bit kernel and gcc while keeping 32-bit userland.
  If it was Debian you could easily do it using official repositories.

 We have 32 bit Debian chroot on 64 bit Debian base system. How can
 I install the 64 bit GCC (and binutils) into the 32 bit chroot?

1. Install linux-image-*-amd64
2. Install gcc-*-multilib

It should be enough to run 64-bit gcc but I cannot verify it - haven't used 
Debian for a while.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] QtWebKit Linking Error On Ubuntu

[Konstantin Tokarev]

10.02.2012, 16:42, Osztrogonac Csaba o...@inf.u-szeged.hu:
 Hi,

 Konstantin Tokarev írta:

  10.02.2012, 15:49, Osztrogonac Csaba o...@inf.u-szeged.hu:
  Hi,

  Konstantin Tokarev írta:
   10.02.2012, 15:10, rakesh sadhu peerpan...@gmail.com:
   Hi,
   I'm trying to build debug qtwebkit on linux ubuntu 10.10 32-bit version 
 .
   I am getting error while linking .
   Kindly help , I don;t want to change my OS version from 32 to 64 bit.
   You can install 64-bit kernel and gcc while keeping 32-bit userland.
   If it was Debian you could easily do it using official repositories.
  We have 32 bit Debian chroot on 64 bit Debian base system. How can
   I install the 64 bit GCC (and binutils) into the 32 bit chroot?
  1. Install linux-image-*-amd64
  2. Install gcc-*-multilib

  It should be enough to run 64-bit gcc but I cannot verify it - haven't used 
 Debian for a while.

 After (2) gcc and ld will be still 32 bit binary, but it will be able to
 build 64 bit binary with -m64 option. But a 32 bit ld never will be able
 to use more than 4Gb of memory.

My bad, sorry for noise.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Is there a way to regenerate the files in webkit/WebCore/generated?

[Konstantin Tokarev]

12.02.2012, 06:37, XiaoDong Wang dongdong.w...@gmail.com:
 There is a features.pri in qt-everywhere-opensource-src-4.8.0’s
 webkit/Source/WebCore.
 I comment out some features. But got error with generated files
 like
 ../../WebCore/generated/JSHTMLEmbedElement.cpp:304:39: error:
 ‘class WebCore::HTMLEmbedElement’ has no member named ‘getSVGDocument’

 in the JSHTMLEmbedElement.cpp, the second line wrote
    This file has been generated by generate-bindings.pl. DO NOT MODIFY!

 How to regenerated the files in webkit/WebCore/generated?
 Will regenerate solve the error?

Don't comment out features in pri. You need to build WebKit stand-alone
with build-webkit script and specify required options in it's command line.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] Qt 5 alpha release

[Konstantin Tokarev]

19.03.2012, 18:08, henry.haveri...@nokia.com henry.haveri...@nokia.com:
 On 3/19/12 3:59 PM, Storm-Olsen Marius (Nokia-MP/Austin)
 marius.storm-ol...@nokia.com wrote:

 On 3/19/12 2:48 PM, Haverinen Henry (Nokia-MP/Tampere)
 henry.haveri...@nokia.com wrote:
 The Qt WebKit module can become a part of Qt Essentials, but Qt WebKit
 Widgets module cannot, because it depends on other add-on modules.
 Oh? Which ones? ICU I consider to be an external system library
 dependence, also on Windows. What other requirements are there?

 I meant that the WebKit stuff that comes from Qt 4 and that would now be
 called Qt WebKit Widgets depends on Qt Widgets and Qt Quick 1 (add correct
 naming :).

Are you planning to remove this code from WebKit repository?

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] webkit on Mips (Caught signal 11 (at (nil), invalid address)

[Konstantin Tokarev]

01.05.2012, 16:28, Harsha Buruganahalli harsha.buruganaha...@pace.com:
 Thanks for the reply Konstantin,

 I had a check and I see that we are not using the -ffunction-sections compile 
 options.

It's set inside one of .pro files.

 Why do you suspect the toolchain? Have you witnessed this failure before?

I had random crashes on sh4, finally fixed by updating compiler

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] webkit2, v8, diplomacy

[Konstantin Tokarev]

05.06.2012, 16:53, Balazs Kelemen kbal...@webkit.org:
     Hi all!

 I think it's time to decide how important is the v8 integration for us. I'm 
 not saying it's hyper-super important, I'm just curious about your opinion. 
 In fact we have a qt5 release blocker bug for that: 
 https://bugs.webkit.org/show_bug.cgi?id=76778 (although at the time when it 
 has been filed we did not expect that much community resistance) and it's 
 also quite clear that this could save a lot of memory (1 js engine instead of 
 2).

V8 does not work on a number of srachitectures, e.g. sh4 (while JSC even has 
JIT for it)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo.cgi/webkit-qt

Re: [webkit-qt] qtwebkit qt-4.8.2 crashes in qws embedded environment

[Konstantin Tokarev]

14.08.2012, 17:52, Coda Highland chighl...@gmail.com:
 My first suggestion would be to check out the qtwebkit-2.3 branch and
 try using that; it's much better all around.

Or try to rebuild with --system-malloc

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QImage vs QPixmap as native image

[Konstantin Tokarev]

13.09.2013, 15:50, Jocelyn Turcotte jocelyn.turco...@digia.com:
 On Fri, Sep 13, 2013 at 03:12:59PM +0400, Konstantin Tokarev wrote:

  Hi all,

  There was a patch [1] that was later reverted because of performance 
 degradation on DirectFB, where QPixmap is hardware accelerated.

  We use QtWebKit 2.3.3 with Qt 4.8 on embedded system. We have internally 
 written gfxdriver for QWS which does not provide hardware acceleration for 
 QPixmap's, but allows to create hardware accelerated QImage's (I know it's 
 rather strange, but it's what we have right now).

  Now I'd like to provide hardware acceleration for images in QtWebKit.  What 
 route is better for me:
  1) apply [1] again on top of QtWebKit 2.3 and use accelerated QImage's;
  2) add hardware acceleration for QPixmap's (it does not seem too difficult 
 from implementation point of view for me)?

  Are there any performance advantages from using QImage with WebKit native 
 decoders as compared to QPixmap?

 If my memory serves me right, QPixmap and QImage are the same up to the point 
 where they are given to a paint engine through QPainter.
 Since decoding in QtWebKit happens before that point, any operation on a 
 QPixmap will just be delegated to its internal QImage.

 In Qt4 the X11 paint engine is converting them to an XPixmap, which would 
 allow hardware assisted blitting. Performances should be the same between 
 QPixmap and QImage when using the raster paint engine.
 In Qt5 linux now uses the raster paint engine as well, the only advantage of 
 QPixmap that I'm aware of is for the image blitting special case of the 
 DirectFB platform plugin that you mentioned.

Thank you for reply,

I was more interested in possible advantages of QImage over QPixmap in QtWebKit 
(not vice versa). For example, QPixmap does not allow direct manipulations with 
its pixel buffer which might be used to speed up some operations. I'm just 
wondering if such trick was an initial motivation for QPixmap - QImage 
conversion.

(I'm not using X11 and I can get hardware blitting for QImage)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] [WEBKIT 2.3] Compile on windows with --media-stream with qt 4.8.2 msvc

[Konstantin Tokarev]

04.10.2013, 12:05, arnaud le roy sdnetw...@gmail.com:
 hello,

 i try to compile the webkit 2.3 but i get some compilation error with
 the media_stream options :

 In file included from WebCore/bindings/js/JSEventTargetCustom.cpp:29:0:
 generated/EventTargetHeaders.h:130:30: fatal error: LocalMediaStream.h:
 No such file or directory

This file is located in Source/WebCore/Modules/mediastream. Make sure it's
present in include paths (you may need to fix .pro/.pri files to get it).

Please submit a patch if you succeed.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] [WEBKIT 2.3] Compile on windows with --media-stream with qt 4.8.2 msvc

[Konstantin Tokarev]

04.10.2013, 17:13, arnaud le roy sdnetw...@gmail.com:
 Le 04/10/2013 10:10, Konstantin Tokarev a écrit :

  04.10.2013, 12:05, arnaud le roy sdnetw...@gmail.com:
  hello,

  i try to compile the webkit 2.3 but i get some compilation error with
  the media_stream options :

  In file included from WebCore/bindings/js/JSEventTargetCustom.cpp:29:0:
  generated/EventTargetHeaders.h:130:30: fatal error: LocalMediaStream.h:
  No such file or directory
  This file is located in Source/WebCore/Modules/mediastream. Make sure it's
  present in include paths (you may need to fix .pro/.pri files to get it).

  Please submit a patch if you succeed.

 thanks four your response,

 effectively a have add some includepath in webcore.pri :

   $$SOURCE_DIR/Modules/websockets \
   $$SOURCE_DIR/Modules/mediastream \

 But now i encountered an other problem :

 this file is not present :

 - JSMediaStreamEvent.h
 - JSMediaStreamTrackEvent.h
 - MediaSource.h
 - and maybe others ...

JSMediaStreamEvent.h and JSMediaStreamTrackEvent.h (and other files starting
with JS* you will be missing) should be generated from respective .idl files
(in this case, MediaStreamEvent.idl and MediaStreamTrackEvent.idl).

You need to add them to WebCore/DerivedSources.pri under condition

contains(DEFINES, ENABLE_XXX=1) {
IDL_BINDINGS += \
$$PWD/Modules/mediastream/MediaStreamEvent.idl
...
}

where ENABLE_XXX is ENABLE_MEDIA_STREAM or something like that (look at your
command line for respective -D flag). 


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] [WEBKIT 2.3] Compile on windows with --media-stream with qt 4.8.2 msvc

[Konstantin Tokarev]

04.10.2013, 21:54, arnaud le roy sdnetw...@gmail.com:
 thanks,

 now it compiles fine but i have some unresolved symbol in the final
 linkage !

 for exemple :

 WebCore.lib(JSRTCPeerConnection.obj) : error LNK2019: unresolved
 external symbol public: void __thiscall WebC
 ore::RTCPeerConnection::getStats(class WTF::PassRefPtrclass
 WebCore::RTCStatsCallback,class WTF::PassRefPtr
 class WebCore::MediaStreamTrack)
 (?getStats@RTCPeerConnection@WebCore@@QAEXV?$PassRefPtr@VRTCStatsCallback@W
 ebCore@@@WTF@@V?$PassRefPtr@VMediaStreamTrack@WebCore@@@4@@Z) referenced
 in function __int64 __fastcall WebCo
 re::jsRTCPeerConnectionPrototypeFunctionGetStats(class JSC::ExecState
 *) (?jsRTCPeerConnectionPrototypeFuncti
 onGetStats@WebCore@@YI_JPAVExecState@JSC@@@Z)

 i have 67 unresolved symbol, maybe it is not enougth to include idl ? it
 seems that all the resolved symbol is on media_stream dependency (i
 attach the major unresolved symbol).

 have you an idea ?

You could have easily found (e.g. with git grep) that your missing symbol
should be coming from Modules/mediastream/RTCPeerConnection.cpp.

But files from WebCore/platform/mediastream are missing in WebCore/Target.pri.
You should add them there.

That should resolve linker error, however that may not be enough to get it
working how you want. If you need working WebRTC implementation, you'll
need non-dummy RTCPeerConnectionHandler implementation, and it's present
only in Chromium port (platform/mediastream/chromium), so I'm afraid you
will need a lot of work to integrate it.


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] [WEBKIT 2.3] Compile on windows with --media-stream with qt 4.8.2 msvc

[Konstantin Tokarev]

05.10.2013, 15:40, arnaud le roy sdnetw...@gmail.com:
 thanks,

 i have found my problems this morning and i post it but the message
 awaits approval.

 this is the message :

 hello,
 after some modifications, i have successfully compile the webkit with
 this options :
 --qt --media-stream --media-source --media-capture --video --no-webkit2
 this is the list of files that need to be modified :
 - Source\WebCore\DerivedSources.pri
 - Source\WebCore\WebCore.pri
 - Source\WebCore\Target.pri
 - Source\WebCore\platform\mediastream\RTCPeerConnectionHandler.cpp
 i have some doubt about the add of

 WebCore\platform\mediastream\gstreamer in the target.pri because in
 windows the flag WTF_USE_GSTREAMER=0 (maybe we can force it ?).and the
 other platform for mediastream are blackberry and chronium.

 any help on this part would be good.

 so you confirm my doubt about this part (dummy RTCPeerConnectionHandler
 )so if i understand for the moment we could not enable webrtc on windows
 plattform

Chromium supports windows, so you may want to try to plug that code into
your WebKit build instead of dummy implementation. But it will probably
have Chromium-specific dependencies, so you'll need to figure them out
and maybe modify source code to make it working with QtWebKit.

If your primary platform is Windows, you may want to switch from QtWebKit
to Chromium port (or Qt WebEngine, Chromium wrapper being developed right
now). AFAIK, media support was never first-class citizen for QtWebKit on
Windows.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] [WEBKIT 2.3] Compile on windows with --media-stream with qt 4.8.2 msvc

[Konstantin Tokarev]

05.10.2013, 16:11, arnaud le roy sdnetw...@gmail.com:
 Le 05/10/2013 14:00, Konstantin Tokarev a écrit :

  05.10.2013, 15:40, arnaud le roy sdnetw...@gmail.com:
  thanks,

  i have found my problems this morning and i post it but the message
  awaits approval.

  this is the message :
  hello,
  after some modifications, i have successfully compile the webkit with
  this options :
  --qt --media-stream --media-source --media-capture --video --no-webkit2
  this is the list of files that need to be modified :
  - Source\WebCore\DerivedSources.pri
  - Source\WebCore\WebCore.pri
  - Source\WebCore\Target.pri
  - Source\WebCore\platform\mediastream\RTCPeerConnectionHandler.cpp
  i have some doubt about the add of
  WebCore\platform\mediastream\gstreamer in the target.pri because in
  windows the flag WTF_USE_GSTREAMER=0 (maybe we can force it ?).and the
  other platform for mediastream are blackberry and chronium.
  any help on this part would be good.
  so you confirm my doubt about this part (dummy RTCPeerConnectionHandler
  )so if i understand for the moment we could not enable webrtc on windows
  plattform
  Chromium supports windows, so you may want to try to plug that code into
  your WebKit build instead of dummy implementation. But it will probably
  have Chromium-specific dependencies, so you'll need to figure them out
  and maybe modify source code to make it working with QtWebKit.

  If your primary platform is Windows, you may want to switch from QtWebKit
  to Chromium port (or Qt WebEngine, Chromium wrapper being developed right
  now). AFAIK, media support was never first-class citizen for QtWebKit on
  Windows.

 Thanks for your help !

 but do you think that Qt WebEngine is compatible with Qt 4.8.* or only
 with greater than Qt 5.0 ?

Qt 5 is required (maybe even Qt 5.2), though it might be possible to backport
it to Qt 4. Or just use raw Chromium if Qt wrapper is not principal for you.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

25.10.2013, 16:58, Richard Gerd Kuesters rich...@humantech.com.br:
 Hello all!

 I am currently tweaking one of my webkit applications to shrink its size 
 (bandwidth costs are sometimes high).

You can shrink QtWebKit by using custom options of build-webkit script. For 
example, disabling SVG support will make it much smaller.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

25.10.2013, 22:21, Richard Gerd Kuesters rich...@humantech.com.br:
 Thanks Andras!

 I'm sorry for my DLL list. We already rips *d.dll from the distrib :)

 I was wondering if print or qml or quick or sensors are really necessary for 
 webkit to work ...

That depends only on what your application uses and what are requirements of 
your application.
Basically it means that you can safely throw away most of plugins, keeping 
platforms/qwindows.dll
and probably imageformats qjpeg.dll, qgif.dll, qpng.dll. If you find you 
missing some functionality,
add it back :)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

27.10.2013, 02:17, Richard Gerd Kuesters rich...@humantech.com.br:
 Thanks again Konstantin!

 I think my best hope is based on what you glimpsed while pondering about SVG 
 support on Webkit: compiling Qt submodules one by one, using the switches I 
 might need and other that don't - doing so in a extreme fast machine (SSD 
 raid and so on) with basic automatic functionality tests, could give me a 
 very good result in a couple of days (using config parsing switches scripts). 
 It would be awesome to provide a barely minimal and downsized package for 
 mobile clients (which I'm now focused), as an example.

 One thing I was thinking: is there any ICU flag that I could disable during 
 compiling that doesn't affect Webkit behaviours? I'm asking this because 
 after (or even) webkit's own lib, ICU's the bigger one (~21Mb in Windows -- 
 I'm still working to get it's release lib on mobile).

The largest thing in ICU is internationalization data. Depending on target 
audience of your application, you may want to remove data for some locales - 
look into ICU documentation how to prepare custom .dat file. There may also be 
kinds of data unused by WebKit - maybe currencies or timezones, though I don't 
know for sure.

BTW, QtWebKit 2.3 does not depend on ICU - you may want to use it, or 
forward-port code replacing ICU to your QtWebKit version.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

27.10.2013, 02:17, Richard Gerd Kuesters rich...@humantech.com.br:
 Thanks again Konstantin!

 I think my best hope is based on what you glimpsed while pondering about SVG 
 support on Webkit: compiling Qt submodules one by one, using the switches I 
 might need and other that don't - doing so in a extreme fast machine (SSD 
 raid and so on) with basic automatic functionality tests, could give me a 
 very good result in a couple of days (using config parsing switches scripts). 
 It would be awesome to provide a barely minimal and downsized package for 
 mobile clients (which I'm now focused), as an example.

Most of shrinking can be done deterministically: if you don't need to open TIFF 
images, remove TIFF plugin; if you don't use QtSql, get rid of it; etc. Also 
make sure you are using size optimization of compiler. Even if you don't 
disable SVG in WebKit, you don't need QtSvg and corresponding imageformat 
plugin - WebKit's implementation of SVG is independent and much more complete.


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

28.10.2013, 15:36, Richard Gerd Kuesters rich...@humantech.com.br:
 Well, it might appear as a very dumb question, but ... where do I find this 
 version of QtWebkit that doesnt depends on lib ICU? I was digging around with 
 version 2.3 (including ones already included in Qt 5.2 b1) and they still 
 needs ICU.

git://gitorious.org/+qtwebkit-developers/webkit/qtwebkit-23.git

I'm using 2.3.3 without any ICU.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

28.10.2013, 15:50, Richard Gerd Kuesters rich...@humantech.com.br:
 Yes, I just did that :)

 My only doubt was that I saw some ICU unicode header files in the .pro files. 
 So, I can just drop this on top of the Qt version I use and bye bye ICU?

You don't need to change .pro file to drop ICU (I don't do it).

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

28.10.2013, 22:49, Richard Gerd Kuesters rich...@humantech.com.br:
 Well ... Is it just with me or gitorious is completely unable to work with?

Works fine here. You can try ssh or https url - it might be you are behind a
firewall that blocks git protocol.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

29.10.2013, 17:42, Richard Gerd Kuesters rich...@humantech.com.br:
 Ok, QtWebkit 2.3.3 downloaded! :)

 But, I feel that it'll not work as a simple dropin on top of Qt 5.x, 
 specially if I try to compile it on Windows.

 I noticed a huge difference in the Makefiles (and .pro?) files from the 
 QtWebkit shipped with Qt 5.x and this one, specially in WTF.

 Any thoughts?

I'm afraid QtWebKit 2.3.3 was not tested on Windows at all (though I may be 
wrong). It should be very close to QtWebkit shipped with Qt 5.0.x-5.1.x in 
terms of included bugfixes and features though.

Huge difference in Makefiles should not bother you. But be prepared to some 
cherry-pick work for Windows-specific fixes - having git is highly recommended.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] how to shrink distribution, if possible?

[Konstantin Tokarev]

29.10.2013, 19:13, Konstantin Tokarev annu...@yandex.ru:
 I'm afraid QtWebKit 2.3.3 was not tested on Windows at all (though I may be 
 wrong). 

Looks like QupZilla uses QtWebKit 2.3 on Windows [1], so my guess was wrong :)

[1] https://github.com/QupZilla/qupzilla

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] running a network video stream in webkit

[Konstantin Tokarev]

31.10.2013, 13:05, Thomas Scheuermann scheuerm...@barco.com:
 Hello,

 I would like to run a network video stream in webkit.
 I first tried it with a file:

 video autoplay 
 source  src=BigBuckBunny.ogv
 /video

 This works and the video starts playing.
 If I use:

 video autoplay 
  source
 src=rtsp://192.168.180.22/axis-media/media.amp?videocodec=h264
 /video

 the video doesn't start.
 I can see that the stream is running, if I do:

 gst-launch-1.0 playbin
 uri=rtsp://192.168.180.22/axis-media/media.amp?videocodec=h264

 the video is playing.
 Webkit also uses the gstreamer-1.0 libraries.

 What can I do to get this playing?

HTML5 does not specify what protocols can be used for media sources, so your 
HTML is correct and could work if MediaPlayer implementation supported RTSP. 
You need to debug what's going on inside 
Source/WebCore/platform/graphics/gstreamer/MediaPlayerPrivateGStreamer.cpp - 
does gstreamer receive proper URL and if its API is used properly for RTSP case.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] what's the webkit version in Qt5.1 and Qt5.2Beta

[Konstantin Tokarev]

06.11.2013, 17:42, Rethmeier, Eike eike.rethme...@wincor-nixdorf.com:
 Hi,

 by moving from Qt5.1 to Qt5.2 we encountered some CSS rendering changes with 
 FlexBoxes. Because we want to track down the source of the changes (most 
 likely these changes are actually bugfixes in WebKit) we need the versions of 
 WebKit (not QtWebKit!) used in Qt5.1 and Qt5.2Beta.

 Where can I find these versions?

There is no such thing as WebKit version. Versions exist for WebKit ports 
only.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] sqlite database as local storage

[Konstantin Tokarev]

26.02.2014, 00:38, Richard Gerd Kuesters rich...@humantech.com.br:
 hello all! :)

 i was reading some of webkit resources, and one of them is to provide local 
 database storage, including sqlite3.

 ok, i'm developing a custom application with webkit, and i would like to 
 expose my apps database to it, so i can access it directly using javascript 
 (instead of writing miles of cpp code).

 is it possible?

Yes. WebKit exposes sqlite through APIs of Web Storage [1] (aka Local Storage 
aka DOM Storage) and Indexed DB [2].

If this is not what you want and you need to execute SQL queries in your 
applications, you can try Web SQL Database [3], however this specification is 
obsolete.

[1] http://www.w3.org/TR/webstorage/
[2] http://www.w3.org/TR/IndexedDB/



Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] sqlite database as local storage

[Konstantin Tokarev]

26.02.2014, 13:26, Allan Sandfeld Jensen k...@carewolf.com:
 On Wednesday 26 February 2014, Konstantin Tokarev wrote:

  26.02.2014, 00:38, Richard Gerd Kuesters rich...@humantech.com.br:
  hello all! :)

  i was reading some of webkit resources, and one of them is to provide
  local database storage, including sqlite3.

  ok, i'm developing a custom application with webkit, and i would like to
  expose my apps database to it, so i can access it directly using
  javascript (instead of writing miles of cpp code).

  is it possible?
  Yes. WebKit exposes sqlite through APIs of Web Storage [1] (aka Local
  Storage aka DOM Storage) and Indexed DB [2].

 Indexed DB is only supported from Qt 5.3 and uses leveldb as a backend. It is
 the old database API WebSQL that uses SQLite as a backend.

AFAIU it's possible to build 2.2.x or 2.3x with --indexed-database. I have not
checked if it works properly though.


 `Allan

Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] sqlite database as local storage

[Konstantin Tokarev]

26.02.2014, 13:29, Konstantin Tokarev annu...@yandex.ru:
 26.02.2014, 13:26, Allan Sandfeld Jensen k...@carewolf.com:

  On Wednesday 26 February 2014, Konstantin Tokarev wrote:
   26.02.2014, 00:38, Richard Gerd Kuesters rich...@humantech.com.br:
   hello all! :)

   i was reading some of webkit resources, and one of them is to provide
   local database storage, including sqlite3.

   ok, i'm developing a custom application with webkit, and i would like to
   expose my apps database to it, so i can access it directly using
   javascript (instead of writing miles of cpp code).

   is it possible?
   Yes. WebKit exposes sqlite through APIs of Web Storage [1] (aka Local
   Storage aka DOM Storage) and Indexed DB [2].
  Indexed DB is only supported from Qt 5.3 and uses leveldb as a backend. It 
 is
  the old database API WebSQL that uses SQLite as a backend.

 AFAIU it's possible to build 2.2.x or 2.3x with --indexed-database. I have not
 checked if it works properly though.

My bad, IDBSQLiteBackingStore was removed before 2.3 branch-off, though it is 
available
in 2.2.


Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Unable to install Qt5.0

[Konstantin Tokarev]

06.03.2014, 20:52, Manish Gurnaney manishgurna...@gmail.com:
 Hi Arijit,
          I have set following paths in the .bashrc file
 export QTDIR=/usr/share/qt4
 export PATH=$QTDIR/bin:$PATH
 export QMAKEPATH=/home/OpenSource/webkit/Tools/qmake

          Apart from that when check the qmake version it says
 1) qmake -version
    QMake version 2.01a
    Using Qt version 4.8.1 in /usr/lib/x86_64-linux-gnu

 2) which qmake
    /usr/share/qt4/bin/qmake

 I am using Ubuntu 12.04 LTS 64 Bit.
 Please let me know if I am missing some thing.
 Regards,
 Manish R Gurnaney

With Qt 4.x you should use QtWebKit 2.2.x or 2.3.x


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] Questions about Qt input method support in WebKit 2

[Konstantin Tokarev]

Hi Kenneth,

I'm aware that you are not working on WebKit for a long time, however I'd like 
to ask you some questions about your code.

1. In patch [1] what was the motivation for not sending surroundingText in case 
of result.isInPasswordField? In this case code from patch [2] sets hints 
Qt::ImhHiddenText and Qt::ImhSensitiveData for text coming from password 
fields. May !result.isInPasswordField check in [1] be safely removed now?

2. I've found that Element::innerText() used to obtain surroundingText in [1] 
always returns empty string at least for HTMLTextFormControlElement descendants 
( and ). I've fixed it in patch [3], however I've left 
fallback to innerText for other kinds of elements. Are there any other kinds of 
editable elements where innerText() was known to work in past?

3. Have you tried to support text removal in WebKit2 via QInputMethodEvent ? 
I've tried to support event constructed as

QInputMethodEvent event;
event.setCommitString("",-1,1);

in QtWebPageEventHandler::handleInputMethodEvent() [4] by calling 
m_webPageProxy->confirmComposition("", -1, 1), but that didn't work. For now 
I've surrendered to sending key events with Qt::Key_Backspace.


[1] https://bugs.webkit.org/show_bug.cgi?id=74080
[2] https://bugs.webkit.org/show_bug.cgi?id=76169
[3] https://codereview.qt-project.org/#/c/125970/
[4] 
http://trac.webkit.org/changeset/103233/trunk/Source/WebKit2/UIProcess/qt/QtWebPageEventHandler.cpp

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Reviving QtWebKit

[Konstantin Tokarev]

30.12.2015, 20:01, "Coda Highland" :
> I'm interested but contractually prohibited from contributing. :( I
> wish you the best of luck.

Thank you! Let's hope there will be something for you to test eventually :)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] QtWebKit + libsoup experiment

[Konstantin Tokarev]

Hi all,

(reposting here from webkitnix group in case anyone from INdT team is still 
reading this list) 

I just re-read announcement of Nix from 2013 [1], and it mentions QtWebKit + 
libsoup experiment.
Were its details (goals, results, source code) published somewhere?

I'm also interested why libsoup was chosen over libcurl, and what particular 
drawbacks of QNAM you were trying to overcome.

Have you done any benchmarks comparing performance of QNAM vs libsoup vs 
libcurl?

Thanks!

[1] https://lists.webkit.org/pipermail/webkit-dev/2013-May/024908.html

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] Reviving QtWebKit

[Konstantin Tokarev]

Hello everyone,

I'd like to upgrade QtWebKit to modern WebKit code base. 

One particular goal is to obtain modern browser engine capable of running in 
low memory conditions on MIPS device, which would have relatively small binary 
size.

I'd like to support the next configurations:

* OS: Linux (X11 and EGLFS)
* CPU architectures: x86_64, MIPS
* Compiler: g++ 4.8
* Qt >= 5.4

Other platforms may be supported on best effort basis if community is 
interested. 
Primary focus will probably be on WebKit2, but WebKit1 will also be supported.

In case anyone does not follow WebKit development, here are several highlights 
of what has changed since last QtWebKit branch-off:

* Partial ES6 support in JavaScriptCore 
(https://webkit.org/blog/4054/es6-in-webkit/)
* JavaScriptCore now uses C stack
* FTL JIT - ultimate JIT tier which compiles JS using LLVM 
(https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/)
* JIT for CSS selectors 
(https://webkit.org/blog/3271/webkit-css-selector-jit-compiler/)
* MediaSource and MediaStream (WebRTC) support in GStreamer MediaPlayer 
implementation


Is anybody interested in this project? I'll appreciate any kinds of help.


Here are a few questions for QtWebKit developers:

1. Was it ever considered to switch build system to cmake? In past most ports 
had their own build systems, but now all ports living in trunk use cmake (even 
Apple/Mac is starting to use it) and in future it probably is going to be _the_ 
build system of WebKit project.

Are there any technical reasons to keep using qmake? For the record, I'm rather 
CMake hater than fanboy, but I also prefer to be realistic.

2. How would you recommend to merge WebKit and QtWebKit code bases: 
a) add WebKit code to QtWebKit branch, or 
b) add QtWebKit code to WebKit branch? 

(a) would make easier to preserve history of recent changes in QtWebKit
(b) would bring in LayoutTests, ManualTests, and PerformanceTests, which are 
not present in qtwebkit repo (though I'm not sure how much use would have these 
tests for port not living in trunk).

3. Is there any documentation on [Qt]WebKit internals outside of webkit.org?


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Reviving QtWebKit

[Konstantin Tokarev]

30.12.2015, 15:00, "Konstantin Tokarev" <annu...@yandex.ru>:
> In case anyone does not follow WebKit development, here are several 
> highlights of what has changed since last QtWebKit branch-off:
>
> * Partial ES6 support in JavaScriptCore 
> (https://webkit.org/blog/4054/es6-in-webkit/)
> * JavaScriptCore now uses C stack
> * FTL JIT - ultimate JIT tier which compiles JS using LLVM 
> (https://webkit.org/blog/3362/introducing-the-webkit-ftl-jit/)
> * JIT for CSS selectors 
> (https://webkit.org/blog/3271/webkit-css-selector-jit-compiler/)
> * MediaSource and MediaStream (WebRTC) support in GStreamer MediaPlayer 
> implementation

Sorry, forgotten to mention Content Blocking API:

https://webkit.org/blog/3476/content-blockers-first-look/

-- 
Merry Christmas and Happy New Year,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] [Announcement] QtWebKit Technology Preview 1

[Konstantin Tokarev]

Hi all,

We are pleased to announce QtWebKit Technology Preview 1 [1]

This release features major update of WebKit engine, bringing in support for 
modern Web standards, performance and memory usage optimizations, lots of bug- 
and security fixes done by WebKit community since 2013, when Qt port was 
removed from the trunk of WebKit.

Here is a list of the most prominent changes:

New Web APIs:
-

* A lot of ES2015 features are now supported (82% according to [2] as compared 
to 10% in QtWebKit 5.6)
* Responsive images support ( element, srcset and sizes attributes)
* ellipse() method in Canvas API
* CSS selectors ::read-write and ::read-only
* HTML  element
* WebAudio API

Other improvements:
---

* B3 JIT compiler [3] is now used on x86_64, providing impressive performnce 
improvements for computationally-intensive code
* JavaScriptCore now uses C stack, reducing memory usage and memory 
fragmentation
* JIT for CSS selectors is now available [4]
* New Web Inspector UI

--

However, not all features of QtWebkit 5.6 are implemented in this release. Here 
are the most prominent missing features:

* WebKit 2 and QML integration. Work on it is starting now.
* Support for Qt (QWebPluginFactory) and NPAPI plugins in WebKit 1 (widgets) 
API.
* Private browsing API.
* Accelerated compositing (OpenGL mode works in private branch but is not 
merged yet, software mode is not implemented yet).
* IndexedDB and WebGL are not supported yet

You can find a list of known bugs at [5].

--

This release should be considered to have beta quality and is not recommended 
for use in production environments. However, it's already quite stable and 
could be used as site-speicifc browser or content renderer, unless your content 
is affected by aforementioned bugs.

--

Your help is very much needed!

If you want to have your favorite features to be implemented faster, don't 
hesitate to join our team. There are a lot of different tasks, and many of them 
don't require knowledge of WebKit internals.

--


This release was brought to you by Konstantin Tokarev (annulen) and Vitaly 
Slobodin (vitallium), with invaluable help of WebKit and Qt communitites' 
members.

Happy hacking, and stay tuned!


--

[1] Source code: https://github.com/annulen/webkit/archive/qtwebkit-tp1.zip
Or use qtwebkit-tp1 tag from https://github.com/annulen/webkit git 
repository
Windows x64 binaries built with MSVC 2015: 
https://dl.dropboxusercontent.com/u/30021413/WebKit_MSVC2015_X64_Release.zip

System requirements, build instructions, FAQ and other useful info can be 
found at https://github.com/annulen/webkit/wiki


[2] https://kangax.github.io/compat-table/es6/
[3] https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/
[4] https://webkit.org/blog/3271/webkit-css-selector-jit-compiler/
[5] https://github.com/annulen/webkit/issues?q=is%3Aissue+is%3Aopen+label%3Abug


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] [Announcement] QtWebKit Technology Preview 2

[Konstantin Tokarev]

Hi all,

We are pleased to announce QtWebKit Technology Preview 2. You can find download 
links below [1].

This release includes bug fixes and improvements as compared to Technology 
Preview 1 [2].


Restored Web APIs to improve feature parity with QtWebKit 5.7:
--

* Indexed Database.

This is completely new implementation, which doesn't depend on LevelDB anymore, 
and is more compliant to modern W3C standards.

* Media Source Extensions (only when GStreamer is used).

This is still experimental, known issue is that some YouTube video with preroll 
advertisment are not playing, though it works fine in other cases. To enable 
it, use new attribute QWebSettings::MediaSourceEnabled.

* Device motion and orientation API.
* Gamepad API (on Linux only).
* Enabled  support like it was done in previous releases.


Other improvements
--

* Support for OS X (>= 10.10) added.

You can find build instructions at [3], or use binary build.

* Integrations for qmake, cmake, and pkg-config are now installed.

You can find instructions how to use them in your projects at [4].

* Enabled print support.
* Documentation in HTML and QCH formats is now generated and installed.

Prominent bug fixes
---
* Fixed missing text rendering on some sites.
* Fixed copying to clipboard from web views.
* Fixed some ABI compatibility issues.


---

We are constantly progressing towards restoring feature parity with QtWebKit 
releases based on old WebKit branch, i.e. QtWebKit 5.6 and 5.7. You can track 
this progress at page [5].

--

Your help is very much needed!

If you want to have your favorite features to be implemented faster, don't 
hesitate to join our team. There are a lot of different tasks, and many of them 
don't require knowledge of WebKit internals.

For example it would be great if you helped us to review and improve our CMake 
code.

Happy hacking, and stay tuned!

---

[1]
  Source code:
https://github.com/annulen/webkit/archive/qtwebkit-tp2.tar.gz
https://github.com/annulen/webkit/archive/qtwebkit-tp2.zip
  Or use qtwebkit-tp2 tag from https://github.com/annulen/webkit git repository

  Binaries:
  Windows x86: 
https://dl.dropboxusercontent.com/u/30021413/qtwebkit-tp2-msvc2015-x86.zip
  Windows x64: 
https://www.dropbox.com/s/wmfbwzf0ygcafr1/qtwebkit-tp2-msvc2015-x64.zip
  OS X: https://dl.dropboxusercontent.com/u/30021413/QtWebKit.zip

[2] https://lists.webkit.org/pipermail/webkit-qt/2016-May/004062.html
[3] https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X
[4] https://github.com/annulen/webkit/wiki/Using-QtWebKit-in-your-project
[5] https://github.com/annulen/webkit/wiki/Comparison-with-QtWebKit-5.6

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit reviving progress

[Konstantin Tokarev]

11.01.2016, 14:15, "Konstantin Tokarev" <annu...@yandex.ru>:
> Hello again,
>
> I've created repository at https://github.com/annulen/webkit. Branch 
> qtwebkit-1 contains Qt port of JavaScriptCore, it can be built with 
> build-webkit script. Resulting jsc executable successfully passes tests.
>
> I've added some other information to the wiki:
>
> https://github.com/annulen/webkit/wiki
>
> In particular, it contains list of areas where you can help in case you are 
> interested.
>
> Stay tuned!

BTW, if anyone reading my little wiki find politically incorrect phrasing, or 
factual errors, or just wants to add more information, please send me your 
GitHub nick and I'll add you to collaborators.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit reviving progress

[Konstantin Tokarev]

11.01.2016, 14:53, "Vitaly Slobodin" :
>>  Thta's sad to see work being duplicated. You should have been notified 
>> others on the list. Nevertheless, I hope we will be able to join our work.
>
> Well, I did it really quickly, so I know that there're some problems. I just 
> wanted to check if it's possible.
>
>>  Like I wrote before, upstream is converging around use of CMake as *the* 
>> build system of WebKit, so it's not reasonable to resist. So I decided to go 
>> straight to CMake, despite some bias that I have against it.
>
> Using CMake makes the whole job much easier. We don't need to convert CMake 
> macros for auto-generated files. In other words, with CMake we don't need to 
> do redundant work.

Also, use of CMake can make feasible building WebKit1 part with Qt 4.8 at some 
point. QMake build system was heavily changed during Qt 5 development and is 
incompatible with qmake coming from Qt 4.8, while (AFAIU) code haven't diverged 
too much.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit reviving progress

[Konstantin Tokarev]

11.01.2016, 14:53, "Vitaly Slobodin" :
>
> I'll definitely help you as much as I can!
>

Please take a look at https://github.com/annulen/webkit/wiki/Open-Projects

Also, there are some missing bits in WTF that need to have Qt implementation:

Source/WTF/wtf/qt/RunLoopQt.cpp
Source/WTF/wtf/qt/WorkQueueQt.cpp

The next big step is porting WebCore, but it won't be easy to parallelize.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit reviving progress

[Konstantin Tokarev]

11.01.2016, 17:57, "Atul Sowani" <sow...@gmail.com>:
>  Hi!
>
> I would like to help you in this effort by making sure the new code
> works fine on IBM ppc64le platform. Please let me know if that is
> okay.

Of course!

Moreover, if you are going to implement ppc64le support in LLINT or JIT, you 
can get some limited amount of help here (though I only have big-endian ppc32 
near)

You can start from building JSC, we need to sort out build issues.

If you are cross-compiling you'll need to prepare toolchain file for CMake.

>
> Thanks,
> Atul.
>
> On Mon, Jan 11, 2016 at 5:41 PM, Konstantin Tokarev <annu...@yandex.ru> wrote:
>>  11.01.2016, 14:15, "Konstantin Tokarev" <annu...@yandex.ru>:
>>>  Hello again,
>>>
>>>  I've created repository at https://github.com/annulen/webkit. Branch 
>>> qtwebkit-1 contains Qt port of JavaScriptCore, it can be built with 
>>> build-webkit script. Resulting jsc executable successfully passes tests.
>>>
>>>  I've added some other information to the wiki:
>>>
>>>  https://github.com/annulen/webkit/wiki
>>>
>>>  In particular, it contains list of areas where you can help in case you 
>>> are interested.
>>>
>>>  Stay tuned!
>>
>>  BTW, if anyone reading my little wiki find politically incorrect phrasing, 
>> or factual errors, or just wants to add more information, please send me 
>> your GitHub nick and I'll add you to collaborators.
>>
>>  --
>>  Regards,
>>  Konstantin
>>  ___
>>  webkit-qt mailing list
>>  webkit-qt@lists.webkit.org
>>  https://lists.webkit.org/mailman/listinfo/webkit-qt
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] New QtWebKit progress

[Konstantin Tokarev]

Hi all,

I'm pleased to announce that qtwebkit-1 branch in repository [1] now contains 
everything needed for successful linking of libQt5WebKit.so on Linux using gcc 
4.8.4 or clang 3.7. Branch is based on today's trunk and uses B3 compiler as a 
default FTL backend.

Note that QtTestBrowser is not yet here so there is nothing to run yet. Stay 
tuned!

Windows support is coming soon. It would be great if someone tried to compile 
the code on OS X (10.10 or 10.11 is required) and report encountered issues.

Also I'd like to inform you that trunk (and therefore qtwebkit-1 branch) now 
contains mostly working support for MIPS architecture in JSC engine (up to DFG 
JIT).

[1] https://github.com/annulen/webkit

-

Now about sad things. There are some features that I had to disable during this 
work. They don't have high priority for me, so if anything of these items is 
important for you, please join our project!

* QWebHistory, QWebHistoryItem, and QWebHistoryInterface. WebKit APis has 
changed in this field, so it would require some investigation to restore these 
QtWebKit APIs.

I can assure you that I'm not going make any "official" releases without some 
kind of working history API, but if you want to speed up this process your help 
would be welcome.

* Private browsing API was significantly changed, so it is disabled for now.

Please help if you want this feature to be implemented sooner.

* Plugins (both Qt-style and NPAPI) in WebKit 1 (widgets API). Upstream removed 
support for plugins in single-process mode for non-Windows platforms. On the 
plus side, plugin integration classes were refactored so it should be possible 
to re-add these things without intervention to WebCore.

If nobody is going to help in this field, QtWebKit will likely be released 
without plugin support. Note that Qt Bridge is not affected at all.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] Anyone here interested in QtWebKit on OS X?

[Konstantin Tokarev]

Hi all,

Is anybody here interested in QtWebKit on OS X?

Aside from ongoing project of QtWebKit reviving (which you are welcome to join 
in), there are several possible improvements in QtWebKit 5.6 which could be 
made if you help with testing.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Anyone here interested in QtWebKit on OS X?

[Konstantin Tokarev]

20.01.2016, 18:33, "Coda Highland" <chighl...@gmail.com>:
> On Wed, Jan 20, 2016 at 7:19 AM, Konstantin Tokarev <annu...@yandex.ru> wrote:
>>  Hi all,
>>
>>  Is anybody here interested in QtWebKit on OS X?
>>
>>  Aside from ongoing project of QtWebKit reviving (which you are welcome to 
>> join in), there are several possible improvements in QtWebKit 5.6 which 
>> could be made if you help with testing.
>>
>>  --
>>  Regards,
>>  Konstantin
>>  ___
>>  webkit-qt mailing list
>>  webkit-qt@lists.webkit.org
>>  https://lists.webkit.org/mailman/listinfo/webkit-qt
>
> Yes, I'm available to help with testing.

1. Could you check if https://bugs.webkit.org/show_bug.cgi?id=36853 reproduces 
with Qt 5?
2. Does modern Safari change font size on buttons when scaling page? What other 
modern browsers do on OS X?
3. Does the next HTML code display button with height 250px or something around 
30px in a) modern Safari b) other modern browsers on OS X
4. Do you think if https://codereview.qt-project.org/#/c/146741 would be better 
to have on OS X?

I guess items 2-4 are related to HIG but I'm too lazy to look it up :)

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Anyone here interested in QtWebKit on OS X?

[Konstantin Tokarev]

20.01.2016, 19:43, "Konstantin Tokarev" <annu...@yandex.ru>:
> 20.01.2016, 18:33, "Coda Highland" <chighl...@gmail.com>:
>>  On Wed, Jan 20, 2016 at 7:19 AM, Konstantin Tokarev <annu...@yandex.ru> 
>> wrote:
>>>   Hi all,
>>>
>>>   Is anybody here interested in QtWebKit on OS X?
>>>
>>>   Aside from ongoing project of QtWebKit reviving (which you are welcome to 
>>> join in), there are several possible improvements in QtWebKit 5.6 which 
>>> could be made if you help with testing.
>>>
>>>   --
>>>   Regards,
>>>   Konstantin
>>>   ___
>>>   webkit-qt mailing list
>>>   webkit-qt@lists.webkit.org
>>>   https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>>  Yes, I'm available to help with testing.
>
> 1. Could you check if https://bugs.webkit.org/show_bug.cgi?id=36853 
> reproduces with Qt 5?
> 2. Does modern Safari change font size on buttons when scaling page? What 
> other modern browsers do on OS X?
> 3. Does the next HTML code display button with height 250px or something 
> around 30px in a) modern Safari b) other modern browsers on OS X

Forgotten to paste HTML in question:

botz


> 4. Do you think if https://codereview.qt-project.org/#/c/146741 would be 
> better to have on OS X?
>
> I guess items 2-4 are related to HIG but I'm too lazy to look it up :)
>
> --
> Regards,
> Konstantin
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] New QtWebKit progress

[Konstantin Tokarev]

15.02.2016, 21:20, "mepard" <mep...@me.com>:
> On Feb 12, 2016, at 9:32 AM, Konstantin Tokarev <annu...@yandex.ru> wrote:
>>   It would be great if someone tried to compile the code on OS X (10.10 or 
>> 10.11 is required) and report encountered issues.
>
> I had to make 2 changes to build on OS X 10.11. With these changes, it builds 
> and the MiniBrowser works.
>
> 1. I re-removed setCachedImage from Source/WebCore/html/HTMLImageElement.h.
>
> 2. I added a placeholder for ContextMenuItemTagOpenLinkInThisWindow in 
> WebHTMLView.mm:
>
> diff --git a/Source/WebKit/mac/WebView/WebHTMLView.mm 
> b/Source/WebKit/mac/WebView/WebHTMLView.mm
> index 028567f..6f24eda 100644
> --- a/Source/WebKit/mac/WebView/WebHTMLView.mm
> +++ b/Source/WebKit/mac/WebView/WebHTMLView.mm
> @@ -529,6 +529,8 @@ static Optional toTag(ContextMenuAction action)
>  return WebMenuItemTagMediaMute;
>  case ContextMenuItemTagDictationAlternative:
>  return WebMenuItemTagDictationAlternative;
> + case ContextMenuItemTagOpenLinkInThisWindow:
> + return Nullopt; // FIXME: This was added to QTWebKit
>  case ContextMenuItemTagToggleVideoFullscreen:
>  return WebMenuItemTagToggleVideoFullscreen;
>  case ContextMenuItemTagShareMenu:
>
> I can do a Pull Request if you prefer.

No, Mac code should compile without modifications, I'll add #if for 
ContextMenuItemTagOpenLinkInThisWindow and setCachedImage.


However, what I really wanted you to do was to build Qt port, and you've just 
built Mac port instead :)

Building Qt port requires --qt argument to be passed to build-webkit script. 
See [1] for more details, it says "Linux" but some parts apply to OS X as well. 
You'll need to install cmake if you don't have it.

build-webkit uses environment variable WEBKIT_OUTPUTDIR to choose build dir, so 
you can e.g. have Mac and Qt ports built from the same tree in parallel 
directories.

Thanks!

[1] https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-Linux

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] New QtWebKit progress

[Konstantin Tokarev]

15.02.2016, 21:35, "Konstantin Tokarev" <annu...@yandex.ru>:
> 15.02.2016, 21:20, "mepard" <mep...@me.com>:
>>  On Feb 12, 2016, at 9:32 AM, Konstantin Tokarev <annu...@yandex.ru> wrote:
>>>    It would be great if someone tried to compile the code on OS X (10.10 or 
>>> 10.11 is required) and report encountered issues.
>>
>>  I had to make 2 changes to build on OS X 10.11. With these changes, it 
>> builds and the MiniBrowser works.
>>
>>  1. I re-removed setCachedImage from Source/WebCore/html/HTMLImageElement.h.
>>
>>  2. I added a placeholder for ContextMenuItemTagOpenLinkInThisWindow in 
>> WebHTMLView.mm:
>>
>>  diff --git a/Source/WebKit/mac/WebView/WebHTMLView.mm 
>> b/Source/WebKit/mac/WebView/WebHTMLView.mm
>>  index 028567f..6f24eda 100644
>>  --- a/Source/WebKit/mac/WebView/WebHTMLView.mm
>>  +++ b/Source/WebKit/mac/WebView/WebHTMLView.mm
>>  @@ -529,6 +529,8 @@ static Optional toTag(ContextMenuAction 
>> action)
>>   return WebMenuItemTagMediaMute;
>>   case ContextMenuItemTagDictationAlternative:
>>   return WebMenuItemTagDictationAlternative;
>>  + case ContextMenuItemTagOpenLinkInThisWindow:
>>  + return Nullopt; // FIXME: This was added to QTWebKit
>>   case ContextMenuItemTagToggleVideoFullscreen:
>>   return WebMenuItemTagToggleVideoFullscreen;
>>   case ContextMenuItemTagShareMenu:
>>
>>  I can do a Pull Request if you prefer.
>
> No, Mac code should compile without modifications, I'll add #if for 
> ContextMenuItemTagOpenLinkInThisWindow and setCachedImage.

Pushed fixes for both issues.

>
> However, what I really wanted you to do was to build Qt port, and you've just 
> built Mac port instead :)
>
> Building Qt port requires --qt argument to be passed to build-webkit script. 
> See [1] for more details, it says "Linux" but some parts apply to OS X as 
> well. You'll need to install cmake if you don't have it.
>
> build-webkit uses environment variable WEBKIT_OUTPUTDIR to choose build dir, 
> so you can e.g. have Mac and Qt ports built from the same tree in parallel 
> directories.
>
> Thanks!
>
> [1] https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-Linux
>
> --
> Regards,
> Konstantin
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] New QtWebKit progress

[Konstantin Tokarev]

17.02.2016, 08:44, "Cheng, Bobber" <bch...@intercalleurope.com>:
> Hi Konstantin,
>
> Thanks for your help. I switched branch qtwebkit-1 and uses following command 
> to compile:
>
> perl Tools/Scripts/build-webkit --qt --release --cmakeargs="-W no-dev 
> -DCMAKE_PREFIX_PATH=D:\Qt\Qt5.6.0\5.6\msvc2015"  --no-ninja
>
> Whenever I set --no-ninja or not, I always got following error:
>
> -- Enabled features:
>
> --  ENABLE_DATABASE_PROCESS . OFF
>
> --  ENABLE_INDEXED_DATABASE   OFF
>
> --  ENABLE_VIDEO  OFF
>
> -- Configuring done
>
> -- Generating done
>
> -- Build files have been written to: D:/working/webkit/WebKitBuild/Release
>
> Microsoft (R) Build Engine version 14.0.24730.2
>
> Copyright (C) Microsoft Corporation. All rights reserved.
>
> MSBUILD : error MSB1001: Unknown switch.
>
> Switch: -j4
>
> For switch syntax, type "MSBuild /help"
>
> I used Qt 5.6 RC, MSVC 2015, CMake 3.4.3.

It is known problem, current solution is to use ninja or this patch:

https://github.com/Vitallium/webkit/commit/c93fee8cd35490165011b9eaafae3ad3d7c5c8a3


>
> I tried to open WebKitBuild\Release\WebKit.sln with MSVC 2015. I got lots of 
> compilation error when I compile WebCore.

Please ignore these .sln and .vcxproj files in repository, they have no 
relation to Qt port.

>
> I got same compilation error as before when I compile WebKit.
>
> 1>-- Build started: Project: WebKit (WebKit\WebKit), Configuration: 
> Release Win32 --
>
> 1>  WebKitPrefix.cpp
>
> 1>D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
> file or directory
>
> Thanks,
>
> Bobber
>
> -Original Message-
> From: Konstantin Tokarev [mailto:annu...@yandex.ru]
> Sent: Tuesday, February 16, 2016 7:00 PM
> To: Cheng, Bobber; webkit-qt@lists.webkit.org
> Subject: Re: [webkit-qt] New QtWebKit progress
>
> 16.02.2016, 12:39, "Cheng, Bobber" <bch...@intercalleurope.com>:
>
>> Hi Konstantin,
>
>>
>
>> Did you successfully compile Qt5WebKit on Windows? I following your guide 
>> https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-Windows, but I 
>> got compile error as following. Do you have any suggest to fix it?
>
> Make sure you are building right branch (qtwebkit-1) and pass --qt to 
> build-webkit.
>
>>
>
>> Thanks,
>
>> Bobber
>
>>
>
>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory (compiling source file 
>> D:\working\webkit\Source\WTF\wtf\Assertions.cpp) 
>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>
>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory (compiling source file 
>> D:\working\webkit\Source\WTF\wtf\DateMath.cpp) 
>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>
>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory (compiling source file 
>> D:\working\webkit\Source\WTF\wtf\DecimalNumber.cpp) 
>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>
>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory (compiling source file 
>> D:\working\webkit\Source\WTF\wtf\DataLog.cpp) 
>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>
>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory (compiling source file 
>> D:\working\webkit\Source\WTF\wtf\GregorianDateTime.cpp) 
>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>
>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory (compiling source file 
>> D:\working\webkit\Source\WTF\wtf\Lock.cpp) 
>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>
>> D:\working\webkit\WebKi

Re: [webkit-qt] New QtWebKit progress

[Konstantin Tokarev]

19.02.2016, 11:50, "Cheng, Bobber" <bch...@intercalleurope.com>:
> Thanks.
>
> Bobber

Please retry now.

>
> -Original Message-
> From: Konstantin Tokarev [mailto:annu...@yandex.ru]
> Sent: Thursday, February 18, 2016 11:47 PM
> To: Cheng, Bobber; webkit-qt@lists.webkit.org
> Subject: Re: [webkit-qt] New QtWebKit progress
>
> 17.02.2016, 08:44, "Cheng, Bobber" <bch...@intercalleurope.com>:
>>  Hi Konstantin,
>>
>>  Thanks for your help. I switched branch qtwebkit-1 and uses following 
>> command to compile:
>>
>>  perl Tools/Scripts/build-webkit --qt --release --cmakeargs="-W no-dev 
>> -DCMAKE_PREFIX_PATH=D:\Qt\Qt5.6.0\5.6\msvc2015" --no-ninja
>>
>>  Whenever I set --no-ninja or not, I always got following error:
>>
>>  -- Enabled features:
>>
>>  -- ENABLE_DATABASE_PROCESS . OFF
>>
>>  -- ENABLE_INDEXED_DATABASE OFF
>>
>>  -- ENABLE_VIDEO  OFF
>>
>>  -- Configuring done
>>
>>  -- Generating done
>>
>>  -- Build files have been written to: D:/working/webkit/WebKitBuild/Release
>>
>>  Microsoft (R) Build Engine version 14.0.24730.2
>>
>>  Copyright (C) Microsoft Corporation. All rights reserved.
>>
>>  MSBUILD : error MSB1001: Unknown switch.
>>
>>  Switch: -j4
>>
>>  For switch syntax, type "MSBuild /help"
>>
>>  I used Qt 5.6 RC, MSVC 2015, CMake 3.4.3.
>
> It is known problem, current solution is to use ninja or this patch:
>
> https://github.com/Vitallium/webkit/commit/c93fee8cd35490165011b9eaafae3ad3d7c5c8a3
>
>>  I tried to open WebKitBuild\Release\WebKit.sln with MSVC 2015. I got lots 
>> of compilation error when I compile WebCore.
>
> Please ignore these .sln and .vcxproj files in repository, they have no 
> relation to Qt port.
>
>>  I got same compilation error as before when I compile WebKit.
>>
>>  1>-- Build started: Project: WebKit (WebKit\WebKit), Configuration: 
>> Release Win32 --
>>
>>  1> WebKitPrefix.cpp
>>
>>  
>> 1>D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No such 
>> file or directory
>>
>>  Thanks,
>>
>>  Bobber
>>
>>  -Original Message-
>>  From: Konstantin Tokarev [mailto:annu...@yandex.ru]
>>  Sent: Tuesday, February 16, 2016 7:00 PM
>>  To: Cheng, Bobber; webkit-qt@lists.webkit.org
>>  Subject: Re: [webkit-qt] New QtWebKit progress
>>
>>  16.02.2016, 12:39, "Cheng, Bobber" <bch...@intercalleurope.com>:
>>
>>>  Hi Konstantin,
>>
>>>
>>
>>>  Did you successfully compile Qt5WebKit on Windows? I following your guide 
>>> https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-Windows, but I 
>>> got compile error as following. Do you have any suggest to fix it?
>>
>>  Make sure you are building right branch (qtwebkit-1) and pass --qt to 
>> build-webkit.
>>
>>>
>>
>>>  Thanks,
>>
>>>  Bobber
>>
>>>
>>
>>>  
>>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No 
>>> such file or directory (compiling source file 
>>> D:\working\webkit\Source\WTF\wtf\Assertions.cpp) 
>>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>>
>>>  
>>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No 
>>> such file or directory (compiling source file 
>>> D:\working\webkit\Source\WTF\wtf\DateMath.cpp) 
>>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>>
>>>  
>>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No 
>>> such file or directory (compiling source file 
>>> D:\working\webkit\Source\WTF\wtf\DecimalNumber.cpp) 
>>> [D:\working\webkit\WebKitBuild\Release\Source\WTF\wtf\WTF.vcxproj]
>>
>>>  
>>> D:\working\webkit\WebKitLibraries\win\include\CoreFoundation/CFMessagePort.h(11):
>>>  fatal error C1083: Cannot open include file: 'dispatch/dispatch.h': No 
>>> such file or directory (compiling source file 
>>&

[webkit-qt] Snapshots repository

[Konstantin Tokarev]

Hello,

In case anyone here were willing to build bleeding edge of QtWebKit from 
sources, but were stopped by immense size of git repository [1], now we have 
lean and mean repository [2] which contains only files which are *required* to 
build QtWebKit instead of complete WebKit tree.

Please try building it on your favorite platform(s). It might be that some 
necessary files were omitted by mistake.

Erratum: if you would like to build with build-webkit (instead of direct use of 
CMake), you need to run this command (or equivalent) in repository root:

mkdir WebKitLibraries


[1] https://github.com/annulen/webkit
[2] https://github.com/annulen/qtwebkit-snapshots

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] [Announcement] QtWebKit Technology Preview 5

[Konstantin Tokarev]

Hi all,

QtWebKit Technology Preview 5 is out.

Highlights of these release are:

* WebGL, accelerated compositing and accelerated 2D canvas are supported now. 
Accelerated compositing is disabled by default for now, it is known to cause 
minor artifacts on some sites.

* MinGW compiler is now fully supported on Windows

This improves feature parity with previous releases of QtWebKit [1]. The only 
major remining thing is QML API (based on WebKit2) which is being worked on 
right now [2]

You can find more detailed release changelog and binary builds compatible with 
official Qt 5.8 SDK at

https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5

Big thanks to all contributors!


[1] https://github.com/annulen/webkit/wiki/Comparison-with-QtWebKit-5.6
[2] https://github.com/annulen/webkit/tree/wk2
 https://github.com/annulen/webkit/wiki/Building-WebKit2-%28WIP%29

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

08.02.2017, 08:31, "Charles-Elie Gentil" :
> Hello,
>
> I want use QtWebKit and so, I build it following these instructions : 
> https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X
> I add a CMAKE_INSTALL_PREFIX to have this command :
>
> ./Tools/Scripts/build-webkit --qt --cmakeargs="-Wno-dev 
> -CMAKE_INSTALL_PREFIX=/path/to/my/dir »
>
> The build correctly run but I can’t find the way to run the « install » 
> command.
>
> I try « ninja install », but I've this message
>
> ninja: error: loading 'build.ninja': No such file or directory
>
> Can you help me ?
>
> Thank you very much.

cd WebKitBuild/Release && ninja install

> Best regards,
>
> Charlie
>
> m...@jiyuusoft.net
> http://blog.jiyuusoft.net
> ,
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

09.02.2017, 10:41, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
> I have just tested with the contents of qtwebkit-tp5-qt58-darwin-x64.tar.xz, 
> pasted in /Users/charlie/qtwebkit.

You need to unpack this archive into prefix of your Qt installation, n this 
case it should be  something like /5.8/clang_64

>
> In my .pro file, I have added
>
> QMAKEPATH += /Users/charlie/qtwebkit
>
> QT += webkit
>
> I have the same problem.
>
> I will test this morning with rebuilding my own QtWebkit from 
> qtwebkit-tp5.tar.xz (The construction is relatively slow with my computer ;-) 
> )
>
> Thank
>
> Best regards,
>
> Charlie
>
> m...@jiyuusoft.net
> http://blog.jiyuusoft.net
>
>> Le 9 févr. 2017 à 08:25, Konstantin Tokarev <annu...@yandex.ru> a écrit :
>>
>> 09.02.2017, 10:13, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
>>> Hello,
>>>
>>> @Konstantin : Thank you for your help.
>>>
>>> I did two tests :
>>>    1°) with QtWebKit form here  : 
>>> https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5 
>>> (qtwebkit-tp5.tar.xz)
>>>    2°) with QtWebKit from qt Community : 
>>> http://download.qt.io/community_releases/5.8/5.8.0-final/
>>>
>>> Note :
>>>    - with 1°) CMAKE_INSTALL_PREFIX doesn’t work, and I use « —prefix » 
>>> option. ninja_install works.
>>
>> Indeed, --prefix is a correct option
>>
>>>    - with 2°) ninja_install doesn’t work.
>>
>> Right, because this is a legacy QtWebKit that uses qmake-based build system, 
>> which does not support ninja
>>
>>> In the 2 cases I have, in WebKitBuild/Release several folders including 
>>> libs and include. These 2 folders are similar to those included in 
>>> qtwebkit-tp5-qt58-darwin-x64.tar.xz 
>>> (https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5).
>>> Currently, I only use the first solution (with tp5 of WebKit)
>>>
>>> I work with Qt5.8 and qmake. I have installed QtWebKit in my Qt 
>>> installation. I add webkit in my project :
>>> QT+= webkit
>>>
>>> Unfortunately, when I want compile my project, lQt5WebKit isn’t found.
>>>
>>> Have you an idea ?
>>
>> If you use custom prefix, read
>> https://github.com/annulen/webkit/wiki/Using-QtWebKit-in-your-project
>>
>> By default, TP5 installs into Qt prefix, in this case QT+=webkit should work 
>> out of the box
>>
>>> Best regards,
>>>
>>> Charlie
>>>
>>> m...@jiyuusoft.net
>>> http://blog.jiyuusoft.net
>>>
>>>> Le 8 févr. 2017 à 08:41, Konstantin Tokarev <annu...@yandex.ru> a écrit :
>>>>
>>>> 08.02.2017, 08:31, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
>>>>> Hello,
>>>>>
>>>>> I want use QtWebKit and so, I build it following these instructions : 
>>>>> https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X
>>>>> I add a CMAKE_INSTALL_PREFIX to have this command :
>>>>>
>>>>> ./Tools/Scripts/build-webkit --qt --cmakeargs="-Wno-dev 
>>>>> -CMAKE_INSTALL_PREFIX=/path/to/my/dir »
>>>>>
>>>>> The build correctly run but I can’t find the way to run the « install » 
>>>>> command.
>>>>>
>>>>> I try « ninja install », but I've this message
>>>>>
>>>>> ninja: error: loading 'build.ninja': No such file or directory
>>>>>
>>>>> Can you help me ?
>>>>>
>>>>> Thank you very much.
>>>>
>>>> cd WebKitBuild/Release && ninja install
>>>>
>>>>> Best regards,
>>>>>
>>>>> Charlie
>>>>>
>>>>> m...@jiyuusoft.net
>>>>> http://blog.jiyuusoft.net
>>>>> ,
>>>>>
>>>>> ___
>>>>> webkit-qt mailing list
>>>>> webkit-qt@lists.webkit.org
>>>>> https://lists.webkit.org/mailman/listinfo/webkit-qt
>>>>
>>>> --
>>>> Regards,
>>>> Konstantin
>>> ,
>>>
>>> ___
>>> webkit-qt mailing list
>>> webkit-qt@lists.webkit.org
>>> https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>> --
>> Regards,
>> Konstantin


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

09.02.2017, 10:13, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
> Hello,
>
> @Konstantin : Thank you for your help.
>
> I did two tests :
>    1°) with QtWebKit form here  : 
> https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5 
> (qtwebkit-tp5.tar.xz)
>    2°) with QtWebKit from qt Community : 
> http://download.qt.io/community_releases/5.8/5.8.0-final/
>
> Note :
>    - with 1°) CMAKE_INSTALL_PREFIX doesn’t work, and I use « —prefix » 
> option. ninja_install works.

Indeed, --prefix is a correct option

>    - with 2°) ninja_install doesn’t work.

Right, because this is a legacy QtWebKit that uses qmake-based build system, 
which does not support ninja

>
> In the 2 cases I have, in WebKitBuild/Release several folders including libs 
> and include. These 2 folders are similar to those included in 
> qtwebkit-tp5-qt58-darwin-x64.tar.xz 
> (https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5).
> Currently, I only use the first solution (with tp5 of WebKit)
>
> I work with Qt5.8 and qmake. I have installed QtWebKit in my Qt installation. 
> I add webkit in my project :
> QT+= webkit
>
> Unfortunately, when I want compile my project, lQt5WebKit isn’t found.
>
> Have you an idea ?

If you use custom prefix, read
https://github.com/annulen/webkit/wiki/Using-QtWebKit-in-your-project

By default, TP5 installs into Qt prefix, in this case QT+=webkit should work 
out of the box

>
> Best regards,
>
> Charlie
>
> m...@jiyuusoft.net
> http://blog.jiyuusoft.net
>
>> Le 8 févr. 2017 à 08:41, Konstantin Tokarev <annu...@yandex.ru> a écrit :
>>
>> 08.02.2017, 08:31, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
>>> Hello,
>>>
>>> I want use QtWebKit and so, I build it following these instructions : 
>>> https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X
>>> I add a CMAKE_INSTALL_PREFIX to have this command :
>>>
>>> ./Tools/Scripts/build-webkit --qt --cmakeargs="-Wno-dev 
>>> -CMAKE_INSTALL_PREFIX=/path/to/my/dir »
>>>
>>> The build correctly run but I can’t find the way to run the « install » 
>>> command.
>>>
>>> I try « ninja install », but I've this message
>>>
>>> ninja: error: loading 'build.ninja': No such file or directory
>>>
>>> Can you help me ?
>>>
>>> Thank you very much.
>>
>> cd WebKitBuild/Release && ninja install
>>
>>> Best regards,
>>>
>>> Charlie
>>>
>>> m...@jiyuusoft.net
>>> http://blog.jiyuusoft.net
>>> ,
>>>
>>> ___
>>> webkit-qt mailing list
>>> webkit-qt@lists.webkit.org
>>> https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>> --
>> Regards,
>> Konstantin
> ,
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

  10.02.2017, 10:33, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hi,  Yes … I do it.I have just rebuild from qtwebkit-tp5.tar.xz with debug and release option. Firstly I notice that the building of QtWebkit don’t produce the same element that a standard installation of Qt. For example (on my mac) : 5.8 |___lib     |QtCore.framework          |_Headers          |_QtCore          |_QtCore_debug          |_QtCore_debug.prl          |_QtCore.prl          |_Resources          |_Versions     |QtCore.framework.dSYM     |QtWebKit.framework          |_Headers          |_QtCore          |_Resources          |_Versions  So, *_debug, *.prl, *_debug.prl and *.dSYM are missing.   Secondly, the error is :     library not found for -lQt5WebKit but the lib should not be lQtWebKit  ? It actually should be -framework QtWebKitPlease try patch https://github.com/annulen/webkit/pull/388  Best regards,Charlie m...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 9 févr. 2017 à 18:23, Konstantin Tokarev <annu...@yandex.ru> a écrit : 09.02.2017, 20:00, "Charles-Élie G" <m...@jiyuusoft.net>:Hi,Unfortunately, I have the same problem if I do it. :-(Oops, looks like my instruction was too sloppy, and you followed it verbatimlyqtwebkit-tp5-qt58-darwin-x64.tar.xz contains wrapping directory "qtwebkit-tp5-qt58-darwin-x64" to avoid tarbombing, so it's structure looks likeqtwebkit-tp5-qt58-darwin-x64├── include├── lib└── mkspecsStructure of Qt looks like5.8└── clang_64   ├── bin   ├── doc   ├── include   ├── lib   ├── mkspecs   ├── phrasebooks   ├── plugins   ├── qml   └── translationsAs you could guess, to work properly contents of "include" need to be unpacked to "include" and so onSo right unpack command iscd 5.8/clang_64 && tar --strip-components=1 -xJf /qtwebkit-tp5-qt58-darwin-x64.tar.xz(where  are paths on your system that I don't know)I guess I should write detailed installation instruction :) Envoyé de mon Galaxy S6 Orange Message d'origine De : Konstantin Tokarev <annu...@yandex.ru>Date : 09/02/2017 08:43 (GMT+01:00)À : Charles-Elie Gentil <m...@jiyuusoft.net>Cc : webkit-qt@lists.webkit.orgObjet : Re: [webkit-qt] Build and Install QtWebKit09.02.2017, 10:41, "Charles-Elie Gentil" <m...@jiyuusoft.net>:I have just tested with the contents of qtwebkit-tp5-qt58-darwin-x64.tar.xz, pasted in /Users/charlie/qtwebkit.You need to unpack this archive into prefix of your Qt installation, n this case it should be  something like /5.8/clang_64 In my .pro file, I have addedQMAKEPATH += /Users/charlie/qtwebkitQT += webkitI have the same problem.I will test this morning with rebuilding my own QtWebkit from qtwebkit-tp5.tar.xz (The construction is relatively slow with my computer ;-) )ThankBest regards,Charliem...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 9 févr. 2017 à 08:25, Konstantin Tokarev <annu...@yandex.ru> a écrit :09.02.2017, 10:13, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hello,@Konstantin : Thank you for your help.I did two tests :   1°) with QtWebKit form here  : https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5 (qtwebkit-tp5.tar.xz)   2°) with QtWebKit from qt Community : http://download.qt.io/community_releases/5.8/5.8.0-final/Note :   - with 1°) CMAKE_INSTALL_PREFIX doesn’t work, and I use « —prefix » option. ninja_install works.Indeed, --prefix is a correct option    - with 2°) ninja_install doesn’t work.Right, because this is a legacy QtWebKit that uses qmake-based build system, which does not support ninja In the 2 cases I have, in WebKitBuild/Release several folders including libs and include. These 2 folders are similar to those included in qtwebkit-tp5-qt58-darwin-x64.tar.xz (https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5).Currently, I only use the first solution (with tp5 of WebKit)I work with Qt5.8 and qmake. I have installed QtWebKit in my Qt installation. I add webkit in my project :QT+= webkitUnfortunately, when I want compile my project, lQt5WebKit isn’t found.Have you an idea ?If you use custom prefix, readhttps://github.com/annulen/webkit/wiki/Using-QtWebKit-in-your-projectBy default, TP5 installs into Qt prefix, in this case QT+=webkit should work out of the box Best regards,Charliem...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 8 févr. 2017 à 08:41, Konstantin Tokarev <annu...@yandex.ru> a écrit :08.02.2017, 08:31, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hello,I want use QtWebKit and so, I build it following these instructions : https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-XI add a CMAKE_INSTALL_PREFIX to have this command :./Tools/Scripts/build-webkit --qt --cmakeargs="-Wno-dev -CMAKE_INSTALL_PREFIX=/path/to/my/dir »The build correctly run but I can’t find the way to run the « install » command.I try « ninja install », but I've this messa

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

  10.02.2017, 23:42, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Ok, it works with a Qt application. Unfortunately, with QML application it doesn’t work. Indeed, QML API is not yet finished. If you are interested you can help us with fixing things on macOS I have this message :plugin cannot be loaded for module "QtWebKit": Impossible de charger la bibliothèque /Applications/Qt/5.8/clang_64/qml/QtWebKit/libqmlwebkitplugin.dylib : (dlopen(/Applications/Qt/5.8/clang_64/qml/QtWebKit/libqmlwebkitplugin.dylib, 133): Library not loaded: @rpath/QtWebKit.framework/Versions/5/QtWebKitReferenced from: /Applications/Qt/5.8/clang_64/qml/QtWebKit/libqmlwebkitplugin.dylibReason: image not found) In my Qt installation, I have :QyWebKit.framework   |_Version|_Current       |_5.602.3       |_Ressources       |_QtWebKit       |_Headers   Maybe change #define QTWEBKIT_VERSION 0x05f00${PROJECT_VERSION_MICRO} to point to Current shortcut ?Best regards,Charlie m...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 10 févr. 2017 à 20:27, Charles-Elie Gentil <m...@jiyuusoft.net> a écrit : Sorry, I don’t see all modifications  :-( I do a new test.Best regards,Charlie m...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 10 févr. 2017 à 20:14, Charles-Elie Gentil <m...@jiyuusoft.net> a écrit : Configuring incomplete, errors occurred! But I think that an error with the patch ofSource/cmake/ECMGeneratePriFile.cmake and Source/cmake/ECMGeneratePkgConfigFile.cmakeBest regards,Charlie m...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 10 févr. 2017 à 18:44, Konstantin Tokarev <annu...@yandex.ru> a écrit :   10.02.2017, 10:33, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hi,  Yes … I do it.I have just rebuild from qtwebkit-tp5.tar.xz with debug and release option. Firstly I notice that the building of QtWebkit don’t produce the same element that a standard installation of Qt. For example (on my mac) : 5.8 |___lib     |QtCore.framework          |_Headers          |_QtCore          |_QtCore_debug          |_QtCore_debug.prl          |_QtCore.prl          |_Resources          |_Versions     |QtCore.framework.dSYM     |QtWebKit.framework          |_Headers          |_QtCore          |_Resources          |_Versions  So, *_debug, *.prl, *_debug.prl and *.dSYM are missing.   Secondly, the error is :     library not found for -lQt5WebKit but the lib should not be lQtWebKit  ? It actually should be -framework QtWebKitPlease try patch https://github.com/annulen/webkit/pull/388  Best regards,Charlie m...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 9 févr. 2017 à 18:23, Konstantin Tokarev <annu...@yandex.ru> a écrit : 09.02.2017, 20:00, "Charles-Élie G" <m...@jiyuusoft.net>:Hi,Unfortunately, I have the same problem if I do it. :-(Oops, looks like my instruction was too sloppy, and you followed it verbatimlyqtwebkit-tp5-qt58-darwin-x64.tar.xz contains wrapping directory "qtwebkit-tp5-qt58-darwin-x64" to avoid tarbombing, so it's structure looks likeqtwebkit-tp5-qt58-darwin-x64├── include├── lib└── mkspecsStructure of Qt looks like5.8└── clang_64   ├── bin   ├── doc   ├── include   ├── lib   ├── mkspecs   ├── phrasebooks   ├── plugins   ├── qml   └── translationsAs you could guess, to work properly contents of "include" need to be unpacked to "include" and so onSo right unpack command iscd 5.8/clang_64 && tar --strip-components=1 -xJf /qtwebkit-tp5-qt58-darwin-x64.tar.xz(where  are paths on your system that I don't know)I guess I should write detailed installation instruction :) Envoyé de mon Galaxy S6 Orange Message d'origine De : Konstantin Tokarev <annu...@yandex.ru>Date : 09/02/2017 08:43 (GMT+01:00)À : Charles-Elie Gentil <m...@jiyuusoft.net>Cc : webkit-qt@lists.webkit.orgObjet : Re: [webkit-qt] Build and Install QtWebKit09.02.2017, 10:41, "Charles-Elie Gentil" <m...@jiyuusoft.net>:I have just tested with the contents of qtwebkit-tp5-qt58-darwin-x64.tar.xz, pasted in /Users/charlie/qtwebkit.You need to unpack this archive into prefix of your Qt installation, n this case it should be  something like /5.8/clang_64 In my .pro file, I have addedQMAKEPATH += /Users/charlie/qtwebkitQT += webkitI have the same problem.I will test this morning with rebuilding my own QtWebkit from qtwebkit-tp5.tar.xz (The construction is relatively slow with my computer ;-) )ThankBest regards,Charliem...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 9 févr. 2017 à 08:25, Konstantin Tokarev <annu...@yandex.ru> a écrit :09.02.2017, 10:13, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hello,@Konstantin : Thank you for your help.I did two tests :   1°) with QtWebKit form here  : https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5 (qtwebkit-tp5.tar.xz)   2°) with QtWebKit from qt Community : http://download.qt.io

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

  10.02.2017, 10:33, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hi,  Yes … I do it.I have just rebuild from qtwebkit-tp5.tar.xz with debug and release option. Firstly I notice that the building of QtWebkit don’t produce the same element that a standard installation of Qt. For example (on my mac) : 5.8 |___lib     |QtCore.framework          |_Headers          |_QtCore          |_QtCore_debug          |_QtCore_debug.prl          |_QtCore.prl          |_Resources          |_Versions     |QtCore.framework.dSYM     |QtWebKit.framework          |_Headers          |_QtCore          |_Resources          |_Versions  So, *_debug, *.prl, *_debug.prl and *.dSYM are missing. Yes, at the moment only release configuration is builtSecondly, the error is :     library not found for -lQt5WebKit but the lib should not be lQtWebKit  ? Could you send me your mkspecs/modules/qt_lib_core.pri? Thanks!  Best regards,Charlie m...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 9 févr. 2017 à 18:23, Konstantin Tokarev <annu...@yandex.ru> a écrit : 09.02.2017, 20:00, "Charles-Élie G" <m...@jiyuusoft.net>:Hi,Unfortunately, I have the same problem if I do it. :-(Oops, looks like my instruction was too sloppy, and you followed it verbatimlyqtwebkit-tp5-qt58-darwin-x64.tar.xz contains wrapping directory "qtwebkit-tp5-qt58-darwin-x64" to avoid tarbombing, so it's structure looks likeqtwebkit-tp5-qt58-darwin-x64├── include├── lib└── mkspecsStructure of Qt looks like5.8└── clang_64   ├── bin   ├── doc   ├── include   ├── lib   ├── mkspecs   ├── phrasebooks   ├── plugins   ├── qml   └── translationsAs you could guess, to work properly contents of "include" need to be unpacked to "include" and so onSo right unpack command iscd 5.8/clang_64 && tar --strip-components=1 -xJf /qtwebkit-tp5-qt58-darwin-x64.tar.xz(where  are paths on your system that I don't know)I guess I should write detailed installation instruction :) Envoyé de mon Galaxy S6 Orange Message d'origine De : Konstantin Tokarev <annu...@yandex.ru>Date : 09/02/2017 08:43 (GMT+01:00)À : Charles-Elie Gentil <m...@jiyuusoft.net>Cc : webkit-qt@lists.webkit.orgObjet : Re: [webkit-qt] Build and Install QtWebKit09.02.2017, 10:41, "Charles-Elie Gentil" <m...@jiyuusoft.net>:I have just tested with the contents of qtwebkit-tp5-qt58-darwin-x64.tar.xz, pasted in /Users/charlie/qtwebkit.You need to unpack this archive into prefix of your Qt installation, n this case it should be  something like /5.8/clang_64 In my .pro file, I have addedQMAKEPATH += /Users/charlie/qtwebkitQT += webkitI have the same problem.I will test this morning with rebuilding my own QtWebkit from qtwebkit-tp5.tar.xz (The construction is relatively slow with my computer ;-) )ThankBest regards,Charliem...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 9 févr. 2017 à 08:25, Konstantin Tokarev <annu...@yandex.ru> a écrit :09.02.2017, 10:13, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hello,@Konstantin : Thank you for your help.I did two tests :   1°) with QtWebKit form here  : https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5 (qtwebkit-tp5.tar.xz)   2°) with QtWebKit from qt Community : http://download.qt.io/community_releases/5.8/5.8.0-final/Note :   - with 1°) CMAKE_INSTALL_PREFIX doesn’t work, and I use « —prefix » option. ninja_install works.Indeed, --prefix is a correct option    - with 2°) ninja_install doesn’t work.Right, because this is a legacy QtWebKit that uses qmake-based build system, which does not support ninja In the 2 cases I have, in WebKitBuild/Release several folders including libs and include. These 2 folders are similar to those included in qtwebkit-tp5-qt58-darwin-x64.tar.xz (https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5).Currently, I only use the first solution (with tp5 of WebKit)I work with Qt5.8 and qmake. I have installed QtWebKit in my Qt installation. I add webkit in my project :QT+= webkitUnfortunately, when I want compile my project, lQt5WebKit isn’t found.Have you an idea ?If you use custom prefix, readhttps://github.com/annulen/webkit/wiki/Using-QtWebKit-in-your-projectBy default, TP5 installs into Qt prefix, in this case QT+=webkit should work out of the box Best regards,Charliem...@jiyuusoft.nethttp://blog.jiyuusoft.net Le 8 févr. 2017 à 08:41, Konstantin Tokarev <annu...@yandex.ru> a écrit :08.02.2017, 08:31, "Charles-Elie Gentil" <m...@jiyuusoft.net>:Hello,I want use QtWebKit and so, I build it following these instructions : https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-XI add a CMAKE_INSTALL_PREFIX to have this command :./Tools/Scripts/build-webkit --qt --cmakeargs="-Wno-dev -CMAKE_INSTALL_PREFIX=/path/to/my/dir »The build correctly run but I can’t find the way to run the « install » command.I try « ninja install »

Re: [webkit-qt] Build and Install QtWebKit

[Konstantin Tokarev]

09.02.2017, 20:00, "Charles-Élie G" <m...@jiyuusoft.net>:
> Hi,
>
> Unfortunately, I have the same problem if I do it. :-(

Oops, looks like my instruction was too sloppy, and you followed it verbatimly

qtwebkit-tp5-qt58-darwin-x64.tar.xz contains wrapping directory 
"qtwebkit-tp5-qt58-darwin-x64" to avoid tarbombing, so it's structure looks like

qtwebkit-tp5-qt58-darwin-x64
├── include
├── lib
└── mkspecs

Structure of Qt looks like

5.8
└── clang_64
├── bin
├── doc
├── include
├── lib
├── mkspecs
├── phrasebooks
├── plugins
├── qml
└── translations

As you could guess, to work properly contents of "include" need to be unpacked 
to "include" and so on

So right unpack command is

cd 5.8/clang_64 && tar --strip-components=1 -xJf 
/qtwebkit-tp5-qt58-darwin-x64.tar.xz

(where  are paths on your system that I don't know)

I guess I should write detailed installation instruction :)

>
> Envoyé de mon Galaxy S6 Orange
>
>  Message d'origine 
> De : Konstantin Tokarev <annu...@yandex.ru>
> Date : 09/02/2017 08:43 (GMT+01:00)
> À : Charles-Elie Gentil <m...@jiyuusoft.net>
> Cc : webkit-qt@lists.webkit.org
> Objet : Re: [webkit-qt] Build and Install QtWebKit
>
> 09.02.2017, 10:41, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
>> I have just tested with the contents of qtwebkit-tp5-qt58-darwin-x64.tar.xz, 
>> pasted in /Users/charlie/qtwebkit.
>
> You need to unpack this archive into prefix of your Qt installation, n this 
> case it should be  something like /5.8/clang_64
>
>>
>> In my .pro file, I have added
>>
>> QMAKEPATH += /Users/charlie/qtwebkit
>>
>> QT += webkit
>>
>> I have the same problem.
>>
>> I will test this morning with rebuilding my own QtWebkit from 
>> qtwebkit-tp5.tar.xz (The construction is relatively slow with my computer 
>> ;-) )
>>
>> Thank
>>
>> Best regards,
>>
>> Charlie
>>
>> m...@jiyuusoft.net
>> http://blog.jiyuusoft.net
>>
>>> Le 9 févr. 2017 à 08:25, Konstantin Tokarev <annu...@yandex.ru> a écrit :
>>>
>>> 09.02.2017, 10:13, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
>>>> Hello,
>>>>
>>>> @Konstantin : Thank you for your help.
>>>>
>>>> I did two tests :
>>>>    1°) with QtWebKit form here  : 
>>>> https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5 
>>>> (qtwebkit-tp5.tar.xz)
>>>>    2°) with QtWebKit from qt Community : 
>>>> http://download.qt.io/community_releases/5.8/5.8.0-final/
>>>>
>>>> Note :
>>>>    - with 1°) CMAKE_INSTALL_PREFIX doesn’t work, and I use « —prefix » 
>>>> option. ninja_install works.
>>>
>>> Indeed, --prefix is a correct option
>>>
>>>>    - with 2°) ninja_install doesn’t work.
>>>
>>> Right, because this is a legacy QtWebKit that uses qmake-based build 
>>> system, which does not support ninja
>>>
>>>> In the 2 cases I have, in WebKitBuild/Release several folders including 
>>>> libs and include. These 2 folders are similar to those included in 
>>>> qtwebkit-tp5-qt58-darwin-x64.tar.xz 
>>>> (https://github.com/annulen/webkit/releases/tag/qtwebkit-tp5).
>>>> Currently, I only use the first solution (with tp5 of WebKit)
>>>>
>>>> I work with Qt5.8 and qmake. I have installed QtWebKit in my Qt 
>>>> installation. I add webkit in my project :
>>>> QT+= webkit
>>>>
>>>> Unfortunately, when I want compile my project, lQt5WebKit isn’t found.
>>>>
>>>> Have you an idea ?
>>>
>>> If you use custom prefix, read
>>> https://github.com/annulen/webkit/wiki/Using-QtWebKit-in-your-project
>>>
>>> By default, TP5 installs into Qt prefix, in this case QT+=webkit should 
>>> work out of the box
>>>
>>>> Best regards,
>>>>
>>>> Charlie
>>>>
>>>> m...@jiyuusoft.net
>>>> http://blog.jiyuusoft.net
>>>>
>>>>> Le 8 févr. 2017 à 08:41, Konstantin Tokarev <annu...@yandex.ru> a écrit :
>>>>>
>>>>> 08.02.2017, 08:31, "Charles-Elie Gentil" <m...@jiyuusoft.net>:
>>>>>> Hello,
>>>>>>
>>>>>> I want use QtWebKit and so, I build it following these instructions : 
>>>>>> https://github.com/annulen/webkit/wi

Re: [webkit-qt] Release assert in JIT on ARM

[Konstantin Tokarev]

19.08.2016, 18:34, "Andrew Webster" :
> This may be a question for webkit-dev, but I thought I'd check here first 
> since I'm using qtwebkit-tp3.
>
> On an arm 32-bit platform in SpeculativeJIT::speculate, I occasionally hit 
> the default handler which contains a release assert when using the 
> WebInspector:
>
> switch (edge.useKind()) {
>
> ...
>
> default:
>     RELEASE_ASSERT_NOT_REACHED();
>     break;
> }
>
> The value of edge.useKind() causing this is MachineIntUse. The case handler 
> for this value has been ifdef'd out on my platform:
>
> #if USE(JSVALUE64)
>     case MachineIntUse:
>     speculateMachineInt(edge);
>     break;
>     case DoubleRepMachineIntUse:
>     speculateDoubleRepMachineInt(edge);
>     break;
> #endif
>
> It appears that MachineIntUse is being set in JSC::DFG::FixupPhase::fixupNode 
> when op is ProfileType:
>
> if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>     if (node->child1()->shouldSpeculateInt32())
>     fixEdge(node->child1());
>     else
>     fixEdge(node->child1());
>     node->remove();
> }
>
> I am not at all familiar with this code, but from other usage of 
> MachineIntUse, I would guess that this should not be used except on a 64-bit 
> platform. Given that, I am not sure if
>
> 1. The typeSet should not conform to TypeMachineInt on 32-bit,
>
> 2. shouldSpeculateInt32 should always be true on 32-bit,
>
> 3. Int32Use should always be used on 32-bit, or
>
> 4. Something else.
>
> I currently am going with 3:
>
> if (typeSet->doesTypeConformTo(TypeMachineInt)) {
> #if USE(JSVALUE64)
>     if (node->child1()->shouldSpeculateInt32())
> #endif
>     fixEdge(node->child1());
> #if USE(JSVALUE64)
>     else
>     fixEdge(node->child1());
> #endif
>
> }
>
> This has solved my immediate problem, but due to my lack of understanding, 
> this solution could be quite flawed.
>
> Any help is much appreciated.


Hello, thanks for the interest!

I'm by no means a JSC expert, however from quick analysis it seems to me that 
the correct code would be


#if USE(JSVALUE64)
if (typeSet->doesTypeConformTo(TypeMachineInt)) {
if (node->child1()->shouldSpeculateInt32())
fixEdge(node->child1());
else
fixEdge(node->child1());
node->remove();
}
#else
if (typeSet->doesTypeConformTo(TypeMachineInt) && 
node->child1()->shouldSpeculateInt32()) {
fixEdge(node->child1());
node->remove();
}
#endif


Anyway, I highly recommend you to:

1. Ask real JSC experts on webkit-dev or jsc-dev
2. Run JSC test suite on target (better debug build as well, as it has much 
more ASSERTs) before and after such changes



>
> Thanks,
>
> Andrew
> ,
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] [Announcement] QtWebKit Technology Preview 3

[Konstantin Tokarev]

Hello everyone,

We are pleased to announce QtWebKit Technology Preview 3!

Highlights of this release are:

* NPAPI and Qt plugins are finally supported on X11 and Windows (not on macOS
yet, sorry)

* Bulk of the patches which have never been in the trunk of webkit.org was
merged from Qt repository. Also, some regressions resulting from migration to
new WebKit branch were fixed, which means that now there's very little chance
for you to hit a bug already fixed a year or two ago :)

* Now we finally have nice compact tarballs, and lightweight git repository for
those of you who just wants to build the bleeding edge and is not going to
develop QtWebKit itself [1]

More detailed release changelog, as well as binary builds you can find at

https://github.com/annulen/webkit/releases/tag/qtwebkit-tp3


If you are wondering what is the deal with QtWebKit raised back from the dead,
please read the following post (it also has a few screenshots):

http://qtwebkit.blogspot.ru/2016/08/qtwebkit-im-back.html



[1] https://github.com/annulen/qtwebkit-snapshots

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Release assert in JIT on ARM

[Konstantin Tokarev]

19.08.2016, 20:43, "Konstantin Tokarev" <annu...@yandex.ru>:
> 19.08.2016, 18:34, "Andrew Webster" <awebs...@arcx.com>:
>>  This may be a question for webkit-dev, but I thought I'd check here first 
>> since I'm using qtwebkit-tp3.
>>
>>  On an arm 32-bit platform in SpeculativeJIT::speculate, I occasionally hit 
>> the default handler which contains a release assert when using the 
>> WebInspector:
>>
>>  switch (edge.useKind()) {
>>
>>  ...
>>
>>  default:
>>  RELEASE_ASSERT_NOT_REACHED();
>>  break;
>>  }
>>
>>  The value of edge.useKind() causing this is MachineIntUse. The case handler 
>> for this value has been ifdef'd out on my platform:
>>
>>  #if USE(JSVALUE64)
>>  case MachineIntUse:
>>  speculateMachineInt(edge);
>>  break;
>>  case DoubleRepMachineIntUse:
>>  speculateDoubleRepMachineInt(edge);
>>  break;
>>  #endif
>>
>>  It appears that MachineIntUse is being set in 
>> JSC::DFG::FixupPhase::fixupNode when op is ProfileType:
>>
>>  if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>>  if (node->child1()->shouldSpeculateInt32())
>>  fixEdge(node->child1());
>>  else
>>  fixEdge(node->child1());
>>  node->remove();
>>  }
>>
>>  I am not at all familiar with this code, but from other usage of 
>> MachineIntUse, I would guess that this should not be used except on a 64-bit 
>> platform. Given that, I am not sure if
>>
>>  1. The typeSet should not conform to TypeMachineInt on 32-bit,
>>
>>  2. shouldSpeculateInt32 should always be true on 32-bit,
>>
>>  3. Int32Use should always be used on 32-bit, or
>>
>>  4. Something else.
>>
>>  I currently am going with 3:
>>
>>  if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>>  #if USE(JSVALUE64)
>>  if (node->child1()->shouldSpeculateInt32())
>>  #endif
>>  fixEdge(node->child1());
>>  #if USE(JSVALUE64)
>>  else
>>  fixEdge(node->child1());
>>  #endif
>>
>>  }
>>
>>  This has solved my immediate problem, but due to my lack of understanding, 
>> this solution could be quite flawed.
>>
>>  Any help is much appreciated.
>
> Hello, thanks for the interest!
>
> I'm by no means a JSC expert, however from quick analysis it seems to me that 
> the correct code would be
>
> #if USE(JSVALUE64)
> if (typeSet->doesTypeConformTo(TypeMachineInt)) {
> if (node->child1()->shouldSpeculateInt32())
> fixEdge(node->child1());
> else
> fixEdge(node->child1());
> node->remove();
> }
> #else
> if (typeSet->doesTypeConformTo(TypeMachineInt) && 
> node->child1()->shouldSpeculateInt32()) {
> fixEdge(node->child1());
> node->remove();
> }
> #endif
>
> Anyway, I highly recommend you to:
>
> 1. Ask real JSC experts on webkit-dev or jsc-dev
> 2. Run JSC test suite on target (better debug build as well, as it has much 
> more ASSERTs) before and after such changes

Sorry, I forgot to add an explanation: AFAIU, MachineInt is Int32 | Int52 and 
on 32-bit platforms we don't speculate about Int52 because it won't fit in the 
register anyway, so MachineInt can be only Int32. If we have a MachineInt which 
is not inferred to be Int32, we cannot do anything fast with it and we follow 
to the next branch TypeNumber | TypeMachineInt.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] [Interest] [Announcement] QtWebKit Technology Preview 3

[Konstantin Tokarev]

19.08.2016, 22:08, "Jason H" :
>>  Hello everyone,
>>
>>  We are pleased to announce QtWebKit Technology Preview 3!
>>
>>  Highlights of this release are:
>>
>>  * NPAPI and Qt plugins are finally supported on X11 and Windows (not on 
>> macOS
>>  yet, sorry)
>>
>>  * Bulk of the patches which have never been in the trunk of webkit.org was
>>  merged from Qt repository. Also, some regressions resulting from migration 
>> to
>>  new WebKit branch were fixed, which means that now there's very little 
>> chance
>>  for you to hit a bug already fixed a year or two ago :)
>>
>>  * Now we finally have nice compact tarballs, and lightweight git repository 
>> for
>>  those of you who just wants to build the bleeding edge and is not going to
>>  develop QtWebKit itself [1]
>>
>>  More detailed release changelog, as well as binary builds you can find at
>>
>>  https://github.com/annulen/webkit/releases/tag/qtwebkit-tp3
>>
>>  If you are wondering what is the deal with QtWebKit raised back from the 
>> dead,
>>  please read the following post (it also has a few screenshots):
>>
>>  http://qtwebkit.blogspot.ru/2016/08/qtwebkit-im-back.html
>
> If I understand correctly, QtWebKIT cannot be used on iOS? We're still only 
> able to use QtWebENGINE?

Unfortunately you cannot use any of them, the only working solution is Qt 
WebView module.

And while it's theoretically possible to make QtWebKit working on iOS platform, 
you will be able to use it only for in-house application, as App Store rules 
forbid use of 3rd party browser engines. If this limited use case is 
interesting for anyone, you are welcome to contribute iOS support!

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Release assert in JIT on ARM

[Konstantin Tokarev]

For the record, I've finally merged this patch into qtwebkit-stable branch 
(with correction).

25.08.2016, 16:30, "Andrew Webster" <awebs...@arcx.com>:
> Konstantin,
>
> The patch uses AnyIntUse, which is not defined. MachineIntUse was renamed to 
> AnyIntUse, see https://bugs.webkit.org/show_bug.cgi?id=156941.
>
> The corresponding git commit is 39e9c984. I guess you would either need to 
> grab that commit as well, or rename AnyIntUse back to MachineIntUse. I 
> renamed back to MachineIntUse for testing and can confirm that it fixes my 
> problem. I have not yet run the JSC test suite.
>
> Thanks a lot Yusuke and Konstantin!
>
> Andrew
> ________
> From: Konstantin Tokarev <annu...@yandex.ru>
> Sent: Tuesday, August 23, 2016 2:00 PM
> To: Yusuke SUZUKI
> Cc: Andrew Webster; webkit-qt@lists.webkit.org; jsc-...@lists.webkit.org
> Subject: Re: [webkit-qt] Release assert in JIT on ARM
>
> 23.08.2016, 20:59, "Yusuke SUZUKI" <utatane@gmail.com>:
>>  Fixed. https://trac.webkit.org/changeset/204699
>>
>>  So, I think Konstantin will update the QtWebKitNG for the next Technology 
>> Preview.
>>  Once it is done & released, this issue is fixed :)
>
> I've prepared a backport of this patch to qtwebkit-stable branch, but haven't 
> checked it yet:
>
> https://github.com/annulen/webkit/commit/26abba03efc2013b3937a32c815c0111572f225c
>
>>  On Fri, Aug 19, 2016 at 10:34 PM, Yusuke SUZUKI <utatane@gmail.com> 
>> wrote:
>>>  Nice catch!
>>>
>>>  I've just filed it in https://bugs.webkit.org/show_bug.cgi?id=161029.
>>>  AnyInt includes int52 representation, that is only allowed in 64bit DFG. 
>>> (See enableInt52())
>>>
>>>  On Sat, Aug 20, 2016 at 2:49 AM, Konstantin Tokarev <annu...@yandex.ru> 
>>> wrote:
>>>>  19.08.2016, 20:43, "Konstantin Tokarev" <annu...@yandex.ru>:
>>>>>  19.08.2016, 18:34, "Andrew Webster" <awebs...@arcx.com>:
>>>>>>   This may be a question for webkit-dev, but I thought I'd check here 
>>>>>> first since I'm using qtwebkit-tp3.
>>>>>>
>>>>>>   On an arm 32-bit platform in SpeculativeJIT::speculate, I occasionally 
>>>>>> hit the default handler which contains a release assert when using the 
>>>>>> WebInspector:
>>>>>>
>>>>>>   switch (edge.useKind()) {
>>>>>>
>>>>>>   ...
>>>>>>
>>>>>>   default:
>>>>>>   RELEASE_ASSERT_NOT_REACHED();
>>>>>>   break;
>>>>>>   }
>>>>>>
>>>>>>   The value of edge.useKind() causing this is MachineIntUse. The case 
>>>>>> handler for this value has been ifdef'd out on my platform:
>>>>>>
>>>>>>   #if USE(JSVALUE64)
>>>>>>   case MachineIntUse:
>>>>>>   speculateMachineInt(edge);
>>>>>>   break;
>>>>>>   case DoubleRepMachineIntUse:
>>>>>>   speculateDoubleRepMachineInt(edge);
>>>>>>   break;
>>>>>>   #endif
>>>>>>
>>>>>>   It appears that MachineIntUse is being set in 
>>>>>> JSC::DFG::FixupPhase::fixupNode when op is ProfileType:
>>>>>>
>>>>>>   if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>>>>>>   if (node->child1()->shouldSpeculateInt32())
>>>>>>   fixEdge(node->child1());
>>>>>>   else
>>>>>>   fixEdge(node->child1());
>>>>>>   node->remove();
>>>>>>   }
>>>>>>
>>>>>>   I am not at all familiar with this code, but from other usage of 
>>>>>> MachineIntUse, I would guess that this should not be used except on a 
>>>>>> 64-bit platform. Given that, I am not sure if
>>>>>>
>>>>>>   1. The typeSet should not conform to TypeMachineInt on 32-bit,
>>>>>>
>>>>>>   2. shouldSpeculateInt32 should always be true on 32-bit,
>>>>>>
>>>>>>   3. Int32Use should always be used on 32-bit, or
>>>>>>
>>>>>>   4. Something else.
>>>>>>
>>>>>>   I currently am going with 3:
>>>>>>
>>

[webkit-qt] QtWebKit + MinGW

[Konstantin Tokarev]

Hi all,

There was some interest in getting MinGW support in QtWebKit. I've added 
preliminary instruction at [1]. It uses MSYS2 package repository to set up 
build environment without much hassle.

If anyone has interest to fix remaining build issues you can checkout 
mingw_build branch from git repo.

[1] 
https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-Windows-%28MSYS%29

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Project ERROR: Unknown module(s) in QT: webkitwidgets

[Konstantin Tokarev]

23.08.2016, 17:16, "Florian Bruhin" :
> Hi,
>
> * Gokul kumar  [2016-08-23 18:54:36 +0530]:
>>  I'm trying to build a project which uses QT5.6.
>>
>>  When I try to build it I'm getting following error.
>>
>>  *Project ERROR: Unknown module(s) in QT: webkitwidgets*
>
> QtWebKit was removed from Qt 5.6.
>
> You have various options:
>
> - Switch to its official successor, QtWebEngine:
>   http://doc.qt.io/qt-5/qtwebengine-index.html
> - Download and build QtWebKit separately from here:
>   http://download.qt.io/community_releases/5.6/5.6.1/
> - Download and build the technical preview of the unofficial QtWebKit
>   successor: https://github.com/annulen/webkit/wiki

Windows binaries are here:

https://github.com/annulen/webkit/releases/tag/qtwebkit-tp3 (only for MSVC 2015 
at the moment)

> - Use an older, unsupported Qt (which I wouldn't recommend)
>
> Florian
>
> --
> http://www.the-compiler.org | m...@the-compiler.org (Mail/XMPP)
>    GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc
>  I love long mails! | http://email.is-not-s.ms/
> ,
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Release assert in JIT on ARM

[Konstantin Tokarev]

23.08.2016, 20:59, "Yusuke SUZUKI" <utatane@gmail.com>:
> Fixed. https://trac.webkit.org/changeset/204699
>
> So, I think Konstantin will update the QtWebKitNG for the next Technology 
> Preview.
> Once it is done & released, this issue is fixed :)

I've prepared a backport of this patch to qtwebkit-stable branch, but haven't 
checked it yet:

https://github.com/annulen/webkit/commit/26abba03efc2013b3937a32c815c0111572f225c

>
> On Fri, Aug 19, 2016 at 10:34 PM, Yusuke SUZUKI <utatane@gmail.com> wrote:
>> Nice catch!
>>
>> I've just filed it in https://bugs.webkit.org/show_bug.cgi?id=161029.
>> AnyInt includes int52 representation, that is only allowed in 64bit DFG. 
>> (See enableInt52())
>>
>> On Sat, Aug 20, 2016 at 2:49 AM, Konstantin Tokarev <annu...@yandex.ru> 
>> wrote:
>>> 19.08.2016, 20:43, "Konstantin Tokarev" <annu...@yandex.ru>:
>>>> 19.08.2016, 18:34, "Andrew Webster" <awebs...@arcx.com>:
>>>>>  This may be a question for webkit-dev, but I thought I'd check here 
>>>>> first since I'm using qtwebkit-tp3.
>>>>>
>>>>>  On an arm 32-bit platform in SpeculativeJIT::speculate, I occasionally 
>>>>> hit the default handler which contains a release assert when using the 
>>>>> WebInspector:
>>>>>
>>>>>  switch (edge.useKind()) {
>>>>>
>>>>>  ...
>>>>>
>>>>>  default:
>>>>>  RELEASE_ASSERT_NOT_REACHED();
>>>>>  break;
>>>>>  }
>>>>>
>>>>>  The value of edge.useKind() causing this is MachineIntUse. The case 
>>>>> handler for this value has been ifdef'd out on my platform:
>>>>>
>>>>>  #if USE(JSVALUE64)
>>>>>  case MachineIntUse:
>>>>>  speculateMachineInt(edge);
>>>>>  break;
>>>>>  case DoubleRepMachineIntUse:
>>>>>  speculateDoubleRepMachineInt(edge);
>>>>>  break;
>>>>>  #endif
>>>>>
>>>>>  It appears that MachineIntUse is being set in 
>>>>> JSC::DFG::FixupPhase::fixupNode when op is ProfileType:
>>>>>
>>>>>  if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>>>>>  if (node->child1()->shouldSpeculateInt32())
>>>>>  fixEdge(node->child1());
>>>>>  else
>>>>>  fixEdge(node->child1());
>>>>>  node->remove();
>>>>>  }
>>>>>
>>>>>  I am not at all familiar with this code, but from other usage of 
>>>>> MachineIntUse, I would guess that this should not be used except on a 
>>>>> 64-bit platform. Given that, I am not sure if
>>>>>
>>>>>  1. The typeSet should not conform to TypeMachineInt on 32-bit,
>>>>>
>>>>>  2. shouldSpeculateInt32 should always be true on 32-bit,
>>>>>
>>>>>  3. Int32Use should always be used on 32-bit, or
>>>>>
>>>>>  4. Something else.
>>>>>
>>>>>  I currently am going with 3:
>>>>>
>>>>>  if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>>>>>  #if USE(JSVALUE64)
>>>>>  if (node->child1()->shouldSpeculateInt32())
>>>>>  #endif
>>>>>  fixEdge(node->child1());
>>>>>  #if USE(JSVALUE64)
>>>>>  else
>>>>>  fixEdge(node->child1());
>>>>>  #endif
>>>>>
>>>>>  }
>>>>>
>>>>>  This has solved my immediate problem, but due to my lack of 
>>>>> understanding, this solution could be quite flawed.
>>>>>
>>>>>  Any help is much appreciated.
>>>>
>>>> Hello, thanks for the interest!
>>>>
>>>> I'm by no means a JSC expert, however from quick analysis it seems to me 
>>>> that the correct code would be
>>>>
>>>> #if USE(JSVALUE64)
>>>> if (typeSet->doesTypeConformTo(TypeMachineInt)) {
>>>> if (node->child1()->shouldSpeculateInt32())
>>>> fixEdge(node->child1());
>>>> else
>>>> fixEdge(node->child1());
>>>> node->remove();
>>>> }
>>>> #else
>>>> if (typeSet->doesTypeConformTo(TypeMachineInt) && 
>>>> node->child1()->shouldSpeculateInt32()) {
>>>> fixEdge(node->child1());
>>>> node->remove();
>>>> }
>>>> #endif
>>>>
>>>> Anyway, I highly recommend you to:
>>>>
>>>> 1. Ask real JSC experts on webkit-dev or jsc-dev
>>>> 2. Run JSC test suite on target (better debug build as well, as it has 
>>>> much more ASSERTs) before and after such changes
>>>
>>> Sorry, I forgot to add an explanation: AFAIU, MachineInt is Int32 | Int52 
>>> and on 32-bit platforms we don't speculate about Int52 because it won't fit 
>>> in the register anyway, so MachineInt can be only Int32. If we have a 
>>> MachineInt which is not inferred to be Int32, we cannot do anything fast 
>>> with it and we follow to the next branch TypeNumber | TypeMachineInt.
>>>
>>> --
>>> Regards,
>>> Konstantin
>>> ___
>>> webkit-qt mailing list
>>> webkit-qt@lists.webkit.org
>>> https://lists.webkit.org/mailman/listinfo/webkit-qt


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Mingw build debug binaries

[Konstantin Tokarev]

23.04.2017, 10:49, "Thomas Rusche" :
> Hello and first of thanks for this great project, bringing back WebKit to Qt! 
> It is so much better than the new blink-stuff.
>
> I downloaded the technical preview 5 that does now support MinGW 
> 'qtwebkit-tp5-qt58-mingw530-x86.zip' from 
> https://github.com/annulen/webkit/releases and used it successfully in a 
> release mode build. However I can't use debug mode because the debug binaries 
> are not found. Is this my mistake or are they really missing right now? Will 
> they be included one day?

Yes, we have already started to produce debug builds in CI.

>
> Greetings
> Thomas
> ,
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] Heads up: WebKit 2 (QML API) is merged to qtwebkit-stable

[Konstantin Tokarev]

Hi all,

I've just merged WebKit 2 changes into qtwebkit-stable. From this moment it's 
enabled by default on all systems except macOS and Windows. This means that you 
can use QML API on these systems, but there are a few known problems:

* WebView is not flickable by default, until this bug is fixed: 
https://github.com/annulen/webkit/issues/472
* Fullscreen doesn't work
* Authentication doesn't work
* Custom URL schemes don't work, and there might be slight API changes. Note 
that qrc:// scheme is fully suported
* NPAPI plugins are loaded, but don't display anything
* WebGL doesn't work and breaks things 
https://github.com/annulen/webkit/issues/525

If you don't need QML API, you can build QtWebKit with -DENABLE_WEBKIT2=OFF 
cmake option.
The opposite feature, i.e. building only WebKit 2, is not yet supported, please 
reply if you what to have this feature

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Crash with pdf.js (Technology preview 5)

[Konstantin Tokarev]

30.04.2017, 16:07, "Thomas Rusche" <thomas.rus...@gmail.com>:
> Hello Konstantin,
>
> thanks for your answer. Although I am working on Windows 8.1 64 bit, my MinGW 
> is only 32 bit (the one included in the Qt installer). 

Ah, sorry I misunderstood your initial message.

>So I am wondering why it crashes because it seems not to be related to 64 bit 
>MinGW.

Indeed, JIT with MinGW 32-bit was known to work fine. I'll try to reproduce 
your crash.

>
> The other module you are talking about (QtPdf) I already heard about and it 
> is really interesting, but isn't it using Pdfium? Then I would need to use 
> MSVC compiler on Windows. And I am not sure if I could then use the same code 
> on Linux and Mac.

I see that pdfium is packages in MSYS:

https://github.com/Alexpux/MINGW-packages/tree/master/mingw-w64-pdfium-git

So I guess it should be possible to make QtPdf building as well, using patch 
from this link.
That said, QtPdf currently disables build with MinGW, maybe authors are unaware 
of that patch.

http://code.qt.io/cgit/qt-labs/qtpdf.git/tree/qpdf.pro

>
> The TP5 is already build and I only needed to copy the files into Qt's 
> install path. If I manage to build qtwebkit-stable, does it produce the same 
> kind of files which I only need to copy then?

Then you may want to wait for binary builds of the next release, it should 
happen next week.

>
> Thanks!
> Greetings
> Thomas
>
> 2017-04-30 14:46 GMT+02:00 Konstantin Tokarev <annu...@yandex.ru>:
>
>> 30.04.2017, 10:56, "Thomas Rusche" <thomas.rus...@gmail.com>:
>>> Hello!
>>>
>>> Recently I downloaded the preview version 5 and tried to view pdf files 
>>> with Mozilla's pdf.js. I am using Qt5.8 on Windows 8.1 64bit with MinGW.
>>>
>>> The application crashes immediately, saying there was an error in this 
>>> Webkit lib. I cannot find more details because the MinGW debug build is not 
>>> supported right now.
>>
>> TP5 did not support 64-bit MinGW, please use qtwebkit-stable branch.
>>
>> There are 2 issues here:
>>
>> * JIT is currently broken with 64-bit MinGW (see issue [1]). Yeah it's a 
>> shame, but current solution is to disable JIT automatically in this 
>> configuration [2]. Someone has to fix it, otherwise if fast JavaScript is 
>> your requirement you should consider 32-bit MinGW or 64-bit MSVC.
>>
>> * Debug build with MinGW is possible in qtwebkit-stable branch now, by 
>> skipping debug info for internal code [3]. Similar hack was employed in 
>> legacy QtWebKit too.
>>
>> Note that there is a possible alternative to using pdf,js that avoid using 
>> JavaScript for rendering PDF, by integrating new QtPdf module. See [4]. Note 
>> that some code was already written, if you are interested to help with 
>> implementation please join our IRC channel and ping austriancoder. Though I 
>> have no info if QtPdf supports MinGW at the moment or there are any issues.
>>
>> [1] https://github.com/annulen/webkit/issues/442
>> [2] 
>> https://github.com/annulen/webkit/blob/qtwebkit-stable/Source/cmake/OptionsQt.cmake#L206
>> [3] 
>> https://github.com/annulen/webkit/blob/qtwebkit-stable/Source/PlatformQt.cmake#L10
>> [4] https://github.com/annulen/webkit/issues/232
>>
>>>
>>> But perhaps you can retry it.
>>> Just download pdf.js from here: https://github.com/mozilla/pdf.js/releases
>>> and integrate it into a Qt-resource-file under the prefix "/pdfjs".
>>>
>>> Here is the source code:
>>>
>>> pdfjs.h:
>>>
>>> #ifndef PDFJS_H
>>>
>>> #define PDFJS_H
>>>
>>> #include 
>>>
>>> #include 
>>>
>>> class PdfJs : public QWidget
>>>
>>> {
>>>
>>> Q_OBJECT
>>>
>>> QWebView *webview_ = nullptr;
>>>
>>> public:
>>>
>>> PdfJs(QWidget *parent = 0);
>>>
>>> ~PdfJs();
>>>
>>> };
>>>
>>> #endif // PDFJS_H
>>>
>>> pdfjs.cpp:
>>>
>>> #include "pdfjs.h"
>>>
>>> #include 
>>>
>>> #include 
>>>
>>> #include 
>>>
>>> PdfJs::PdfJs(QWidget *parent)
>>>
>>> : QWidget(parent)
>>>
>>> {
>>>
>>> this->setLayout( new QVBoxLayout );
>>>
>>> this->layout()->setContentsMargins(0,0,0,0);
>>>
>>> webview_ = new QWebView(this);
>>>
>>> webview_->setUrl( QUrl("qrc:/pdfjs/web/viewer.html") );
>>>
>>> // Try to find crash hints with the WebInspector (did not work, app crashes 
>>> too early)
>>>
>>> webview_->page()->settings()->setAttribute(QWebSettings::DeveloperExtrasEnabled,
>>>  true);
>>>
>>> QWebInspector *inspector = new QWebInspector();
>>>
>>> inspector->setPage(webview_->page());
>>>
>>> inspector->setVisible(true);
>>>
>>> this->layout()->addWidget( webview_ );
>>>
>>> }
>>>
>>> PdfJs::~PdfJs()
>>>
>>> {
>>>
>>> }
>>>
>>> Greetings
>>>
>>> Thomas
>>>
>>> ,
>>>
>>> ___
>>> webkit-qt mailing list
>>> webkit-qt@lists.webkit.org
>>> https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>> --
>> Regards,
>> Konstantin


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Heads up: WebKit 2 (QML API) is merged to qtwebkit-stable

[Konstantin Tokarev]

26.04.2017, 11:45, "Konstantin Tokarev" <annu...@yandex.ru>:
> Hi all,
>
> I've just merged WebKit 2 changes into qtwebkit-stable. From this moment it's 
> enabled by default on all systems except macOS and Windows. This means that 
> you can use QML API on these systems, but there are a few known problems:
>
> * WebView is not flickable by default, until this bug is fixed: 
> https://github.com/annulen/webkit/issues/472
> * Fullscreen doesn't work
> * Authentication doesn't work
> * Custom URL schemes don't work, and there might be slight API changes. Note 
> that qrc:// scheme is fully suported
> * NPAPI plugins are loaded, but don't display anything
> * WebGL doesn't work and breaks things 
> https://github.com/annulen/webkit/issues/525
>
> If you don't need QML API, you can build QtWebKit with -DENABLE_WEBKIT2=OFF 
> cmake option.
> The opposite feature, i.e. building only WebKit 2, is not yet supported, 
> please reply if you what to have this feature

Update: macOS support is available too now. Please contact me if you want to 
get binaries, compatible with Qt 5.8.0.

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] Heads up: WebKit 2 (QML API) is merged to qtwebkit-stable

[Konstantin Tokarev]

29.04.2017, 16:52, "Konstantin Tokarev" <annu...@yandex.ru>:
> 26.04.2017, 11:45, "Konstantin Tokarev" <annu...@yandex.ru>:
>>  Hi all,
>>
>>  I've just merged WebKit 2 changes into qtwebkit-stable. From this moment 
>> it's enabled by default on all systems except macOS and Windows. This means 
>> that you can use QML API on these systems, but there are a few known 
>> problems:
>>
>>  * WebView is not flickable by default, until this bug is fixed: 
>> https://github.com/annulen/webkit/issues/472
>>  * Fullscreen doesn't work
>>  * Authentication doesn't work
>>  * Custom URL schemes don't work, and there might be slight API changes. 
>> Note that qrc:// scheme is fully suported
>>  * NPAPI plugins are loaded, but don't display anything
>>  * WebGL doesn't work and breaks things 
>> https://github.com/annulen/webkit/issues/525
>>
>>  If you don't need QML API, you can build QtWebKit with -DENABLE_WEBKIT2=OFF 
>> cmake option.
>>  The opposite feature, i.e. building only WebKit 2, is not yet supported, 
>> please reply if you what to have this feature
>
> Update: macOS support is available too now. Please contact me if you want to 
> get binaries, compatible with Qt 5.8.0.

Update: WebKit 2 is enabled by default on Windows too.

>
> --
> Regards,
> Konstantin
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] CSSDefaultStyleSheets::defaultStyle

[Konstantin Tokarev]

24.11.2017, 15:41, "Konstantin Tokarev" <annu...@yandex.ru>:
> 24.11.2017, 15:18, "Andrew Webster" <awebs...@arcx.com>:
>>>   24.11.2017, 05:41, "Andrew Webster" <awebs...@arcx.com>:
>>>>>>    I ran into an ASSERT in ElementRuleCollector::collectMatchingRules 
>>>>>> (ASSERT(matchRequest.ruleSet)). When ignored, it seg faults.
>>>>>>
>>>>>>    The root cause is that ElementRuleCollector::matchUARules and 
>>>>>> CSSDefaultStyleSheets::initDefaultStyle disagree about the location of 
>>>>>> CSSDefaultStyleSheets::defaultStyle.
>>>>>>    Although CSSDefaultStyleSheets::initDefaultStyle has properly created 
>>>>>> CSSDefaultStyleSheets::defaultStyle, ElementRuleCollector::matchUARules 
>>>>>> looks in a different location and ends up with a nullptr.
>>>>>>
>>>>>>    Adding WEBCORE_EXPORT to the declaration of 
>>>>>> CSSDefaultStyleSheets::defaultStyle fixes this. Does anyone have any 
>>>>>> thoughts on why this might be?
>>>>>>
>>>>>>    GCC 6.2.1 for arm32v7.
>>>>>
>>>>>   Are you using static build of QtWebKit by chance?
>>>>
>>>>   Qt5WebKit.so and Qt5WebKitWidgets.so
>>>
>>>   Is value of ::defaultStyle different in 
>>> ElementRuleCollector::matchUARules and 
>>> CSSDefaultStyleSheets::initDefaultStyle?
>>
>>  That's right. But once I add the EXPORT, the address is the same.
>
> Sounds like a linker bug.

If your toolchain has ld.gold and it was automatically used (you can check 
USE_LD_GOLD value in CMakeCache.txt),
you may want to try setting it to OFF and relinking

>
>>>>>>    Thanks,
>>>>>>
>>>>>>    Andrew
>>>>>    --
>>>>>    Regards,
>>>>>    Konstantin
>>>
>>>   --
>>>   Regards,
>>>   Konstantin
>
> --
> Regards,
> Konstantin

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] CSSDefaultStyleSheets::defaultStyle

[Konstantin Tokarev]

24.11.2017, 15:18, "Andrew Webster" :
>>  24.11.2017, 05:41, "Andrew Webster" :
>   I ran into an ASSERT in ElementRuleCollector::collectMatchingRules 
> (ASSERT(matchRequest.ruleSet)). When ignored, it seg faults.
>
>   The root cause is that ElementRuleCollector::matchUARules and 
> CSSDefaultStyleSheets::initDefaultStyle disagree about the location of 
> CSSDefaultStyleSheets::defaultStyle.
>   Although CSSDefaultStyleSheets::initDefaultStyle has properly created 
> CSSDefaultStyleSheets::defaultStyle, ElementRuleCollector::matchUARules 
> looks in a different location and ends up with a nullptr.
>
>   Adding WEBCORE_EXPORT to the declaration of 
> CSSDefaultStyleSheets::defaultStyle fixes this. Does anyone have any 
> thoughts on why this might be?
>
>   GCC 6.2.1 for arm32v7.

  Are you using static build of QtWebKit by chance?
>>>
>>>  Qt5WebKit.so and Qt5WebKitWidgets.so
>>
>>  Is value of ::defaultStyle different in 
>> ElementRuleCollector::matchUARules and 
>> CSSDefaultStyleSheets::initDefaultStyle?
>
> That's right. But once I add the EXPORT, the address is the same.

Sounds like a linker bug.

>
>   Thanks,
>
>   Andrew
   --
   Regards,
   Konstantin
>>
>>  --
>>  Regards,
>>  Konstantin

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] CSSDefaultStyleSheets::defaultStyle

[Konstantin Tokarev]

24.11.2017, 05:41, "Andrew Webster" :
>>>  I ran into an ASSERT in ElementRuleCollector::collectMatchingRules 
>>> (ASSERT(matchRequest.ruleSet)). When ignored, it seg faults.
>>>
>>>  The root cause is that ElementRuleCollector::matchUARules and 
>>> CSSDefaultStyleSheets::initDefaultStyle disagree about the location of 
>>> CSSDefaultStyleSheets::defaultStyle.
>>>  Although CSSDefaultStyleSheets::initDefaultStyle has properly created 
>>> CSSDefaultStyleSheets::defaultStyle, ElementRuleCollector::matchUARules 
>>> looks in a different location and ends up with a nullptr.
>>>
>>>  Adding WEBCORE_EXPORT to the declaration of 
>>> CSSDefaultStyleSheets::defaultStyle fixes this. Does anyone have any 
>>> thoughts on why this might be?
>>>
>>>  GCC 6.2.1 for arm32v7.
>>
>> Are you using static build of QtWebKit by chance?
>
> Qt5WebKit.so and Qt5WebKitWidgets.so

Is value of ::defaultStyle different in 
ElementRuleCollector::matchUARules and CSSDefaultStyleSheets::initDefaultStyle?

>
>>>  Thanks,
>>>
>>>  Andrew
>>  --
>>  Regards,
>>  Konstantin

-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] CSSDefaultStyleSheets::defaultStyle

[Konstantin Tokarev]

> I ran into an ASSERT in ElementRuleCollector::collectMatchingRules 
> (ASSERT(matchRequest.ruleSet)). When ignored, it seg faults.
> 
> The root cause is that ElementRuleCollector::matchUARules and 
> CSSDefaultStyleSheets::initDefaultStyle disagree about the location of 
> CSSDefaultStyleSheets::defaultStyle.
> Although CSSDefaultStyleSheets::initDefaultStyle has properly created 
> CSSDefaultStyleSheets::defaultStyle, ElementRuleCollector::matchUARules looks 
> in a different location and ends up with a nullptr.
> 
> Adding WEBCORE_EXPORT to the declaration of 
> CSSDefaultStyleSheets::defaultStyle fixes this. Does anyone have any thoughts 
> on why this might be?
> 
> GCC 6.2.1 for arm32v7.

Are you using static build of QtWebKit by chance?

> 
> Thanks,
> 
> Andrew
-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit Question

[Konstantin Tokarev]

>>> FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option 
>>> present there. No idea if it's sufficient.
>>
>> FYI, it's not sufficient, which is why I'm considering going back to WebKit.
> 
> Ok. If you don't mind to do some compilation, please get 5.212 branch from 
> git://code.qt.io/qt/qtwebkit.git
> and apply patch https://0x0.st/siPl.txt to it, then build as in [1] but with 
> additional cmake argument
> -DUSE_APPSTORE_COMPLIANT_CODE=ON

It should probable be ok to install ICU with brew or macports if you don't want 
to build it. And I think advice to
use U_DISABLE_RENAMING in the article makes no sense, it's better to keep it as 
is.

> 
> If you have no interest in use of QML API you can also add 
> -DENABLE_WEBKIT2=OFF.
> 
> (Depending on kind of your application you may want to cut down some other 
> stuff, look at public
> cmake options with tool like ccmake or cmake-gui)
> 
> [1] https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X
> 
>> On Sat, Nov 11, 2017 at 9:09 AM, Konstantin Tokarev <annu...@yandex.ru> 
>> wrote:
>>
>>>>> Hi,
>>>
>>>> Hi,
>>>
>>>> Please use webkit-qt@ lists.webkit.org mailing list for QtWebKit questions 
>>>> which don't involve confidential information
>>>
>>>>> I have an app that I publish on the Mac App Store that used QtWebKit. I 
>>>>> remember that in order to get it published I had to follow these 
>>>>> instructions: http://wiki.phisys.com/index.php/How-To_Qt5.3_Mac_AppStore
>>>
>>>>> Since Qt seemed to be moving forward with WebEngine, I spent a couple 
>>>>> months refactoring my app to use that instead. However it wasn't until I 
>>>>> was ready to publish my app that I learned some of the Chromium backend 
>>>>> uses private API, which is not allowed on the Mac App Store. Ugh!
>>>
>>>> FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option 
>>>> present there. No idea if it's sufficient.
>>>
>>>>> Now I'm thinking about going BACK to QtWebKit. Do you know if your fork 
>>>>> is Mac App Store compliant? Do you believe the instructions in the link 
>>>>> above are still relevant? Any advice?
>>>
>>>> I'm not aware of any better guide than your link above. See [1].
>>>
>>>> I think ICU is still considered private API by Apple, and you have to 
>>>> build QtWebKit with your own copy of it. I think we can add an option like 
>>>> aforementioned use_appstore_compliant_code, which will suppress use of 
>>>> system ICU and maybe do other customizations.
>>>
>>>> I guess there should not be other issues with code, though structure of 
>>>> bundles may indeed make correction.
>>>
>>>> Article says that there is no workaround for WebKit2 (QML API), in fact I 
>>>> guess bootstrap_look_up2 issue is easy to get rid of by using unix sockets 
>>>> IPC implementation
>>>
>>>> [1] https://bugreports.qt.io/browse/QTBUG-31419
>>>
>>> Note that I'm talking about QtWebKit 5.212. If you use legacy version e.g. 
>>> one shipped with Qt 5.9, instructions from article should apply verbatimely
>>>
>>>>> Thanks,
>>>
>>>>> Adalid Claure
>>>
>>>> --
>>>
>>>> Regards,
>>>
>>>> Konstantin
>>>
>>>> ___
>>>
>>>> webkit-qt mailing list
>>>
>>>> webkit-qt@lists.webkit.org
>>>
>>>> https://lists.webkit.org/mailman/listinfo/webkit-qt
>>>
>>> --
>>>
>>> Regards,
>>>
>>> Konstantin
> 
> --
> Regards,
> Konstantin
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt
-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit Question

[Konstantin Tokarev]

>>FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option 
>>present there. No idea if it's sufficient.
> 
> FYI, it's not sufficient, which is why I'm considering going back to WebKit.

Ok. If you don't mind to do some compilation, please get 5.212 branch from 
git://code.qt.io/qt/qtwebkit.git
and apply patch https://0x0.st/siPl.txt to it, then build as in [1] but with 
additional cmake argument
-DUSE_APPSTORE_COMPLIANT_CODE=ON

If you have no interest in use of QML API you can also add -DENABLE_WEBKIT2=OFF.

(Depending on kind of your application you may want to cut down some other 
stuff, look at public
cmake options with tool like ccmake or cmake-gui)

[1] https://github.com/annulen/webkit/wiki/Building-QtWebKit-on-OS-X

> 
> On Sat, Nov 11, 2017 at 9:09 AM, Konstantin Tokarev <annu...@yandex.ru> wrote:
> 
>>>> Hi,
>>
>>>
>>
>>> Hi,
>>
>>>
>>
>>> Please use webkit-qt@ lists.webkit.org mailing list for QtWebKit questions 
>>> which don't involve confidential information
>>
>>>
>>
>>>> I have an app that I publish on the Mac App Store that used QtWebKit. I 
>>>> remember that in order to get it published I had to follow these 
>>>> instructions: http://wiki.phisys.com/index.php/How-To_Qt5.3_Mac_AppStore
>>
>>>>
>>
>>>> Since Qt seemed to be moving forward with WebEngine, I spent a couple 
>>>> months refactoring my app to use that instead. However it wasn't until I 
>>>> was ready to publish my app that I learned some of the Chromium backend 
>>>> uses private API, which is not allowed on the Mac App Store. Ugh!
>>
>>>
>>
>>> FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option 
>>> present there. No idea if it's sufficient.
>>
>>>
>>
>>>> Now I'm thinking about going BACK to QtWebKit. Do you know if your fork is 
>>>> Mac App Store compliant? Do you believe the instructions in the link above 
>>>> are still relevant? Any advice?
>>
>>>
>>
>>> I'm not aware of any better guide than your link above. See [1].
>>
>>>
>>
>>> I think ICU is still considered private API by Apple, and you have to build 
>>> QtWebKit with your own copy of it. I think we can add an option like 
>>> aforementioned use_appstore_compliant_code, which will suppress use of 
>>> system ICU and maybe do other customizations.
>>
>>>
>>
>>> I guess there should not be other issues with code, though structure of 
>>> bundles may indeed make correction.
>>
>>>
>>
>>> Article says that there is no workaround for WebKit2 (QML API), in fact I 
>>> guess bootstrap_look_up2 issue is easy to get rid of by using unix sockets 
>>> IPC implementation
>>
>>>
>>
>>> [1] https://bugreports.qt.io/browse/QTBUG-31419
>>
>> Note that I'm talking about QtWebKit 5.212. If you use legacy version e.g. 
>> one shipped with Qt 5.9, instructions from article should apply verbatimely
>>
>>>
>>
>>>> Thanks,
>>
>>>> Adalid Claure
>>
>>>
>>
>>> --
>>
>>> Regards,
>>
>>> Konstantin
>>
>>> ___
>>
>>> webkit-qt mailing list
>>
>>> webkit-qt@lists.webkit.org
>>
>>> https://lists.webkit.org/mailman/listinfo/webkit-qt
>>
>> --
>>
>> Regards,
>>
>> Konstantin
-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebKit Question

[Konstantin Tokarev]

>> Hi,
> 
> Hi,
> 
> Please use webkit-qt@ lists.webkit.org mailing list for QtWebKit questions 
> which don't involve confidential information
> 
>> I have an app that I publish on the Mac App Store that used QtWebKit. I 
>> remember that in order to get it published I had to follow these 
>> instructions: http://wiki.phisys.com/index.php/How-To_Qt5.3_Mac_AppStore
>>
>> Since Qt seemed to be moving forward with WebEngine, I spent a couple months 
>> refactoring my app to use that instead. However it wasn't until I was ready 
>> to publish my app that I learned some of the Chromium backend uses private 
>> API, which is not allowed on the Mac App Store. Ugh!
> 
> FWIW I see there is WEBENGINE_CONFIG += use_appstore_compliant_code option 
> present there. No idea if it's sufficient.
> 
>> Now I'm thinking about going BACK to QtWebKit. Do you know if your fork is 
>> Mac App Store compliant? Do you believe the instructions in the link above 
>> are still relevant? Any advice?
> 
> I'm not aware of any better guide than your link above. See [1].
> 
> I think ICU is still considered private API by Apple, and you have to build 
> QtWebKit with your own copy of it. I think we can add an option like 
> aforementioned use_appstore_compliant_code, which will suppress use of system 
> ICU and maybe do other customizations.
> 
> I guess there should not be other issues with code, though structure of 
> bundles may indeed make correction.
> 
> Article says that there is no workaround for WebKit2 (QML API), in fact I 
> guess bootstrap_look_up2 issue is easy to get rid of by using unix sockets 
> IPC implementation
> 
> [1] https://bugreports.qt.io/browse/QTBUG-31419

Note that I'm talking about QtWebKit 5.212. If you use legacy version e.g. one 
shipped with Qt 5.9, instructions from article should apply verbatimely

> 
>> Thanks,
>> Adalid Claure
> 
> --
> Regards,
> Konstantin
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt
-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

[webkit-qt] QtWebKit 5.212.0 Alpha 4

[Konstantin Tokarev]

New release is now available! Source tarballs and binaries are available at 
https://github.com/qtwebkit/qtwebkit/releases/tag/qtwebkit-5.212.0-alpha4

### New APIs

* `QWebSetting::ErrorPageEnabled` - `true` by default, allows to disable 
built-in error pages if they are not desirable

### Improvements

* [CSS Compositing](https://www.w3.org/TR/compositing-1) is now supported
* Push is enabled by default for HTTP/2 requests
* QtWebKit does not require Python 2 anymore for building and can use Python 3 
instead
* QtWebKit won't be eager to pick bitmap fonts as a suitable choice for 
standard font families
* More appropriiate hinting option for web fonts is used

### Bug fixes

* Fix memory leak in 
[CustomEvent](https://developer.mozilla.org/en-US/docs/Web/API/CustomEvent/CustomEvent)
* SVG fragment identifier is not respected if it is a part of an HTTP URL  
(#818)
* Context menu actions for images in Resources tab of inspector use blob: 
instead of original URL (#899)
* Always enable JavaScript for QWebInspector (#566)
* Inspector UI: Only selected item is painted in Styles combobox (#262)
* Inspector should inspect itself in DEVELOPER_MODE only (#444)
* fast/gradients/css3-color-stop-invalid.html - box is green instead of white 
(#230)
* Work around [QTBUG-77308](https://bugreports.qt.io/browse/QTBUG-77308) when 
using Qt < 5.14
* Fix compilation errors with ICU 65.1 and Qt 5.14
* Fix compilation when QPdf is disabled in Qt
* Fix compilation with MinGW for x86_64 target

### Third-party software updates

Windows binaries are shipped with `ICU 65.1`, `libxml2 2.9.10`, `libxslt 
1.1.34`, and `libjpeg-turbo 2.0.3`.

## Sponsors

This release is sponsored by:
* dizmo AG
* Florian Apolloner
* Movable Ink and Michael Nutt
* ScrapingHub

-- 
Regards,
Konstantin

___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

27.04.2020, 21:44, "Konstantin Tokarev" :
> 27.04.2020, 12:24, "Ramakanth Kesireddy" :
>>  Hi,
>>
>>  Am unable to build Qt WebKit 5.212 sources extracted from 
>> http://download.qt.io/snapshots/ci/qtwebkit/5.212/latest/src/submodules/
>>  as part of Qt 5.12.8 sources.
>
> Hi,
> Please use latest release: 
> https://github.com/qtwebkit/qtwebkit/releases/tag/qtwebkit-5.212.0-alpha4
> Link above should never be used as its contains many garbage files, and even 
> if you use most recently changed, its just snapshot and not fully-validated 
> version.
>
>>  Earlier, Qt WebKit 5.6.3 had been built successfully along with Qt 5.6.3 
>> sources.
>>
>>  Could you please let me know compatible QtWebkit 5.212 sources which would 
>> build along with Qt 5.12.8 sources or QtWebkit  needs to be built as a 
>> separate module using cmake?
>
> Build instructions are referenced in README file, see e.g.
> https://github.com/qtwebkit/qtwebkit/wiki/Building-QtWebKit-on-Linux

Also, make sure that you are building against installed Qt binaries

-- 
Regards,
Konstantin

___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

27.04.2020, 12:24, "Ramakanth Kesireddy" :
> Hi,
>
> Am unable to build Qt WebKit 5.212 sources extracted from 
> http://download.qt.io/snapshots/ci/qtwebkit/5.212/latest/src/submodules/
> as part of Qt 5.12.8 sources.

Hi,
Please use latest release: 
https://github.com/qtwebkit/qtwebkit/releases/tag/qtwebkit-5.212.0-alpha4
Link above should never be used as its contains many garbage files, and even if 
you use most recently changed, its just snapshot and not fully-validated 
version.

>
> Earlier, Qt WebKit 5.6.3 had been built successfully along with Qt 5.6.3 
> sources.
>
> Could you please let me know compatible QtWebkit 5.212 sources which would 
> build along with Qt 5.12.8 sources or QtWebkit  needs to be built as a 
> separate module using cmake?

Build instructions are referenced in README file, see e.g.
https://github.com/qtwebkit/qtwebkit/wiki/Building-QtWebKit-on-Linux

>
> Appreciate your help in this regard as it fails to build after installing all 
> dependencies for Qt WebKit.
>
> Best Regards,
> Ramakanth
>
> Best Regards,
> Ramakanth
> ,
>
> ___
> webkit-qt mailing list
> webkit-qt@lists.webkit.org
> https://lists.webkit.org/mailman/listinfo/webkit-qt


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

30.04.2020, 19:29, "Ramakanth Kesireddy" :
> I need to pass below options in the cmake configure options,right?

Yes

>
> So QtWebkit cannot be build along with Qt 5.12.8 sources unlike with Qt 5.6.3 
> earlier as the build is being supported only with cmake and needs to be built 
> with cmake on Qt installed binaries?

Yes


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

01.05.2020, 06:59, "Ramakanth Kesireddy" :
> Hi Konstantin,
>
> Thanks for your mail.
>
> As per  https://github.com/qtwebkit/qtwebkit/wiki/Building-QtWebKit-on-Linux, 
> it has dependency on Qt positioning and sensor modules.
> Since in the configure line, I skipped the modules  using -skip qtlocation 
> -skip qtsensors, Could you please let me know if Qtwebkit has mandatory 
> dependency on these modules or can be disabled with  -DENABLE_LOCATION=OFF and
>    -DENABLE_SENSORS=OFF ?

-DENABLE_GEOLOCATION=OFF -DENABLE_DEVICE_ORIENTATION=OFF


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

29.04.2020, 14:12, "Ramakanth Kesireddy" :
> Thanks a lot..It resolves the issue. But it throws below error further. Do we 
> required to configure qt with opengl inorder to build qtwebkit?
>
>   CMake Error at Source/cmake/OptionsQt.cmake:592 (message):
>   Qt with OpenGL support is required for ENABLE_OPENGL

This message means that you have to disable OpenGL support with 
-DENABLE_OPENGL=OFF if your Qt doesn't have it.
You might get similar messages for other optional features if you are missing 
stuff.


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

30.04.2020, 16:56, "Ramakanth Kesireddy" :
> Hi Konstantin,
>
> Is there any dependency of Qt WebKit on Qtwebeockets or any other modules as 
> few modules like Qtwebeockets are skipped in installation of Qt libraries 
> along with no opengl in the configure line since there is no GPU on embedded 
> device. But do I need to enable opengl on Ubuntu 16.04 desktop..Please let me 
> know in this regard.

See previous answer. Also, if you are not using QML API you can build with 
-DENABLE_WEBKIT2=OFF
which implicitly disables QtWebSockets dependency as well as other stuff you 
don't need.



-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt

Re: [webkit-qt] QtWebkit 5.212 issue

[Konstantin Tokarev]

mples -no-use-gold-linker -no-iconv 
> -no-mtdev -dbus -fontconfig -system-freetype -no-libudev -no-openssl -qt-pcre 
> -v
>
> Could you please let me know if the error is because of Qt is not configured 
> with ssl though all dependencies and qt modules mentioned in 
> https://github.com/qtwebkit/qtwebkit/wiki/Building-QtWebKit-on-Linux
> are installed or missing anything in this regard?
>
> Thanks and Regards,
> Ramakanth
>
> On Fri, May 1, 2020 at 10:27 AM Ramakanth Kesireddy  
> wrote:
>> Looks like QtPositioning need to be installed as it throws below errors 
>> while running cmake with opengl and webkit2 disabled.
>>
>>  -- Could NOT find Dwz (missing:  DWZ_EXECUTABLE) (Required is at least 
>> version "0.13")
>> -- Found WebP: /usr/include
>> CMake Error at /usr/local/Qt-5.12.8/lib/cmake/Qt5/Qt5Config.cmake:28 
>> (find_package):
>>   Could not find a package configuration file provided by "Qt5Positioning"
>>   with any of the following names:
>>
>>     Qt5PositioningConfig.cmake
>>     qt5positioning-config.cmake
>>
>>   Add the installation prefix of "Qt5Positioning" to CMAKE_PREFIX_PATH or set
>>   "Qt5Positioning_DIR" to a directory containing one of the above files.  If
>>   "Qt5Positioning" provides a separate development package or SDK, be sure it
>>   has been installed.
>> Call Stack (most recent call first):
>>   Source/cmake/OptionsQt.cmake:646 (find_package)
>>   Source/cmake/WebKitCommon.cmake:51 (include)
>>   CMakeLists.txt:137 (include)
>>
>> Best Regards,
>> Ramakanth
>>
>> On Fri, May 1, 2020 at 9:29 AM Ramakanth Kesireddy  
>> wrote:
>>> Hi Konstantin,
>>>
>>> Thanks for your mail.
>>>
>>> As per  
>>> https://github.com/qtwebkit/qtwebkit/wiki/Building-QtWebKit-on-Linux, it 
>>> has dependency on Qt positioning and sensor modules.
>>> Since in the configure line, I skipped the modules  using -skip qtlocation 
>>> -skip qtsensors, Could you please let me know if Qtwebkit has mandatory 
>>> dependency on these modules or can be disabled with  -DENABLE_LOCATION=OFF 
>>> and
>>>    -DENABLE_SENSORS=OFF ?
>>>
>>> Best Regards,
>>> Ramakanth
>>>
>>> On Thu, Apr 30, 2020 at 10:43 PM Konstantin Tokarev  
>>> wrote:
>>>> 30.04.2020, 19:29, "Ramakanth Kesireddy" :
>>>>> I need to pass below options in the cmake configure options,right?
>>>>
>>>> Yes
>>>>
>>>>>
>>>>> So QtWebkit cannot be build along with Qt 5.12.8 sources unlike with Qt 
>>>>> 5.6.3 earlier as the build is being supported only with cmake and needs 
>>>>> to be built with cmake on Qt installed binaries?
>>>>
>>>> Yes
>>>>
>>>> --
>>>> Regards,
>>>> Konstantin


-- 
Regards,
Konstantin
___
webkit-qt mailing list
webkit-qt@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-qt