[webkit-dev] Point within WebKit API to extract Bitmaps
Hi Folks We have code which extracts RGB+A bitmaps from WebKit pages in real time. Currently we do this via an OSX WebKit View in a window and by requesting the bitmap through the OSX View mechanism (not directly from WebKit). It works well and we get clean RGB+A in real time from the WebKit structure (usually..) However, we are finding that this approach does not always give us the *performance* that we need, particularly where we have things like deep opacity changes (eg fading things on and off). We have to disable some of the 3d acceleration stuff in the WebKit view to ensure we continue to see changes on the CPU side (otherwise the change happens on the GPU and we only see the completed transition at the CPU side) I have seen other systems which are more deeply knitted into the guts of WebKit which have better performance and I wondered if any WebKit experts here could tell me where in the API of webkit I should look to pull out bitmaps repeatedly (eg 25 FPS) I am reasonably familiar with the overall components of WebKit, but the render layer / context arrangement is fairly complicated to unpick, I understand that QT has a call something like: QWebElement::render(QPainter*, QRect const&) (in QtWebKit) and this may be doing approximately what I want, but I dont want to use QT, so I need to understand which WebKit calls this QWebElement::render is digging into. Any ideas ? Thanks ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Mavericks Nightly
Hi Folks. Any news on when we can get a nightly build to run on Mavericks ? ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] 32-bit WebKit Nighly build APPLICATION ?
Hi Folks. Does anyone know if the WebKit Nightly build app is / can be built as a 32-bit capable binary app ? I note that forcing WebKit to start up in 32-bit mode throws an error - relating to a path in the /Applications/Safari directory. Even tho Safari itself is quite happy to launch in 32-bit mode, and I have compiled the WebKit frameworks with build-webkit --32-bit and replaced the frameworks inside the WebKit nightly app. I need to be able to create an app using the WebKit nightly app, but with modified WebKit frameworks inside, all running in 32-bit. I have not had any luck doing this lately, although It did work OK previously in the Snow Leopard era. The fact that I can select 32-bit on WebKit suggests the app binary itself is universal 64/32 so I am not sure what part of the system is actually throwing the error - it looks like a file it's looking for inside /Applications/Safari which it can't find when in 32 bit mode. The error is Unable to launch Safari, Launching Safari at /Applications/Safari.app failed with the error 'No Such file or directory' (2) I get the same thing with the downloaded WebKit and also one where I have replaced the frameworks with 32-bit only versions. Anyone have *any* idea what is going on? -- To reproduce the problem, just download the nightly build of the WebKit app, set it to start in 32-bit and run it. Thanks. ___ webkit-dev mailing list webkit-dev@lists.webkit.org https://lists.webkit.org/mailman/listinfo/webkit-dev
[webkit-dev] Putting your own Webkit variant back into the Nightly build WebKit App
Hi Folks. I wonder if someone could help me figure out how to move my newly compiled WebKit (with tweaks) into the bundle of the Nightly build application. I want to have a self contained browser running with my webkit-variation. I did manage to do this once last year, and I have the self contained app to prove it, but I don't appear to be able to repeat the feat a year later with a newer set of code. Probably I have forgotten a step and I am missing out something All I am doing is copying the 4 frameworks out of my release folder and replacing the ones in the nightly build folder (in the 10.7 subfolder, since I am testing on 10.7). Whilst my build does what I expect when I use run-safari, the re-bundled Nightly Build webkit app seems to be reverting to the built in webkit, (or at least 'another' web kit without my changes). Maybe I need to copy the frameworks into the 10.6 folder as well ?? Could anyone offer any advice? Thanks. Mark. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Configuring for Clang
Hi Folks. I have been trying for weeks to build WebKit in 32-bit. My system is a MacMini Server with 10.7.4 and latest XCode. I update via SVN then use build-webkit. This creates a good working 64bit version. However, when I use build-webkit --32-bit or build-webkit ARCHS=i386 x86_64 ONLY_ACTIVE_ARCH=NO I get various build failures which generally seem related to 32bit truncation of 64bit values. The folks who have responded to my bug report suggest this is because my system uses GCC when running build-webkit instead of clang. I wondered if someone could provide instructions on configuring this machine to use clang instead when running build-webkit. Thanks Mark ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
Re: [webkit-dev] Configuring for Clang - building webkit 32-bit
Thanks to those that replied to this. For the benefit of anyone else in this situation, here is the summary: - build-webkit fails to GCC instead of clang if the version of the developer tools is too old - If you have previously installed XCode in the old /developer folder, then you upgrade via the app store the new version is installed in /Applications - If you build like this it will still use the old XCode tools in /Developer (and hence fail to GCC) - You need to use the xcode-select -switch instruction from the webkit page on building in order to tell the system to adopt the newer XCode from /Applications - Now if you build-webkit it will use the new tools and be happy with clang. For those trying to build with 32-bit you can add the options to build-webkit or you can set the default using set-webkit-configuration tool to 32-bit. now building in 32-bit with clang. fingers crossed. Thanks for the help Hi Folks. I have been trying for weeks to build WebKit in 32-bit. My system is a MacMini Server with 10.7.4 and latest XCode. I update via SVN then use build-webkit. This creates a good working 64bit version. However, when I use build-webkit --32-bit or build-webkit ARCHS=i386 x86_64 ONLY_ACTIVE_ARCH=NO I get various build failures which generally seem related to 32bit truncation of 64bit values. The folks who have responded to my bug report suggest this is because my system uses GCC when running build-webkit instead of clang. I wondered if someone could provide instructions on configuring this machine to use clang instead when running build-webkit. Thanks Mark ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Compiling WebKit in 32 bit for Mac
Hi There, Could anyone enlighten me on how to create a 'build-webkit' tool which compiles the frameworks with 32-bit (and 64-bit perhaps). I need a 32-bit compatible set of frameworks to allow the WebKit app to support 32-bit plug ins like the QuickTime plug in. Using the 'build-webkit' too appears to produce only 64-bit binaries in the frameworks. I want to rebuild webkit as 32/64 bit, with some tiny code changes, then insert these into the WebKit nightly application. This is working fine with the 64-bit only build I am creating with 'build-webkit' but it doesn't then support the 32-bit plug ins (which the nightly build does when it arrives). Clearly the nightly build is not using 'build-webkit' for the frameworks since it comes with universal 64/32 bit Any suggestions ? Thanks Mark. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] build-webkit failure
Hi Folks. Just trying to build the nightly (WebKit-r120550) from 17th June on OSX 10.7.4 Getting ** BUILD FAILED ** The following build commands failed: CompileC /WebKit-r120550/WebKitBuild/JavaScriptCore.build/Release/JSCLLIntOffsetsExtractor.build/Objects-normal/i386/LLIntOffsetsExtractor.o llint/LLIntOffsetsExtractor.cpp normal i386 c++ com.apple.compilers.gcc.4_2 (1 failure) This appears to be warnings treated as errors for: cc1plus: warnings being treated as errors In file included from /WebKit-r120550/Source/JavaScriptCore/llint/LLIntOffsetsExtractor.cpp:71: /WebKit-r120550/WebKitBuild/Release/LLIntOffsets/LLIntDesiredOffsets.h:100537: warning: this decimal constant is unsigned only in ISO C90 ... and lots more the same Could anyone advise how to relax these errors as warnings so I can build ? Thanks Mark ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
[webkit-dev] Plug Ins dont work when rebuilding WebKit
Hi There I know this has been discussed before, but the solution doesn't work for me I am making a tiny behavioural change to WebCore, then rebuilding WebKit to use in a specialist application. When I am done building I move the frameworks into the pre-built WebKit nightly build application. This works great, and the WebCore now does what I want. However the QuickTime Plug-in no longer works, where it did before I switched out the frameworks. I know that in theory I can just copy the WebKitPluginHost and WebKitPluginAgent from the original nightly build into my own WebKit folder, but that does NOT work for me. Its the same if I rework the nightly build app, or use run-safari script. No Plug ins. Could anyone advise how to troubleshoot this ? Whilst I am on the topic, if I am only making a change to WebCore, how could I just replace the WebCore framework into the Nightly build app instead of all the parts. When I try that, the app doesn't really work right, so I am guessing there are some more complex dependancies between builds. Thanks for any tips. Mark. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
