[webkit-dev] Progressing on the Android port

Hi WebKit-dev folks, in the spirit of the mails describing new features I would like to talk about my intention regarding the Android port. == Aim == I want to build WebKit trunk for Android and use it on a phone. This means I want to have build-webkit integration, will host a buildbot, will work

Re: [webkit-dev] New feature - MHTML support

On May 2, 2011, at 6:03 PM, Eric Seidel wrote: > MHTML support was definitely discussed at length back in the early > days of Safari Windows development in webkit.org. Maybe that desire > has gone away since then. I feel very out-of-touch with current > Safari-on-Windows needs. We've had reques

Re: [webkit-dev] Progressing on the Android port

Hi Holger Freyther, On Thu, May 12, 2011 at 7:08 AM, Holger Freyther wrote: > == How == > I want to use CMake as the buildsystem. The main reason is that it is already > used by other ports and the CMake community provides an easy way to use the > Android NDK. > > My aim is to use the existing SK

[webkit-dev] Why is gtest in the Source directory?

Is gtest required to build any of the WebKit ports? If not, can it be moved out of Source and into Tools? Thanks, —Dan ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev

Re: [webkit-dev] Unifying the build systems

On Wed, May 11, 2011 at 9:31 PM, Lucas De Marchi wrote: > This implementation still lacks some parts (these are the biggest ones > I remember from top of my head, there might be others): > - There's no option to enable WebKit2, webgl and webaudio; > - It always uses GTK2 > - GIR files are not gene

Re: [webkit-dev] Why is gtest in the Source directory?

It sounds like you have a helpful mental mapping for what belongs in each directory that we haven't written anywhere. Perhaps you could write it down and send it to webkit-dev so that we can make it a common model. It feels like a related topic is why are the unit tests under Tools as opposed to

Re: [webkit-dev] Why is gtest in the Source directory?

I think more important issue to consider is should WebKit unit-tests (TestWebKitAPI) live under Tools. Unit-tests evolve with the product and an organic part of it - it doesn't feel that they constitute a "tool". Three possible locations come to mind: - ./Tests - separate top-level directory, sibl

Re: [webkit-dev] Why is gtest in the Source directory?

Here's a straw-man proposal: Tests/ Layout/ # Would be nice to have a better name since these test much more than Layout Performance/ Unit/ Manual/ Source/ JavaScriptCore/ WebCore/ WebKit/ ThirdParty/ ANGLE/ Tools/ WebKitTestRunner/ MiniBrowser/ Scripts/ In this organiz

[webkit-dev] Where should unittests live? WAS: Why is gtest in the Source directory?

Changing the subject to let the original thread remain on topic of where gtest itself should live. Having the unittest file live next to the file it's testing has been great on projects I've worked on (e.g. webkitpy). It makes it straightforward to identify if a give file has unittests and to add

[webkit-dev] crash during plugin unload

Hello, I am seeing a crash in the android browser when unloading an NPAPI plugin I am developing. I do not see the problem in chrome, so am wondering if anyone can help me sort out what's different between the two. The test web page is passing a JS object to the plugin, which calls NPN_SetProper

Re: [webkit-dev] Why is gtest in the Source directory?

On Thu, May 12, 2011 at 10:36 AM, Adam Barth wrote: > Here's a straw-man proposal: > > Tests/ -- All testing code. Do test harnesses go here too? Layout/ # Would be nice to have a better name since these test much > more than Layout > DumpRenderTreeTests? Integration? AutomatedHtmlTests?

Re: [webkit-dev] Why is gtest in the Source directory?

On May 12, 2011, at 11:33 AM, David Levin wrote: > Layout/ # Would be nice to have a better name since these test much > more than Layout > > DumpRenderTreeTests? > Integration? > AutomatedHtmlTests? Here are some characteristics of these tests that may help us name the directory: 1) Thi

Re: [webkit-dev] Why is gtest in the Source directory?

Functional? Regards, Tim. On Thu, May 12, 2011 at 10:48 PM, Darin Adler wrote: > On May 12, 2011, at 11:33 AM, David Levin wrote: > > Layout/ # Would be nice to have a better name since these test much >> more than Layout >> > > DumpRenderTreeTests? > Integration? > AutomatedHtmlTests? > > >

Re: [webkit-dev] Why is gtest in the Source directory?

On May 12, 2011, at 11:48 AM, Darin Adler wrote: > On May 12, 2011, at 11:33 AM, David Levin wrote: > >> Layout/ # Would be nice to have a better name since these test much >> more than Layout >> >> DumpRenderTreeTests? >> Integration? >> AutomatedHtmlTests? > > Here are some characteristics

Re: [webkit-dev] Why is gtest in the Source directory?

On Thu, May 12, 2011 at 11:33 AM, David Levin wrote: > > > On Thu, May 12, 2011 at 10:36 AM, Adam Barth wrote: > >> Here's a straw-man proposal: >> >> Tests/ > > -- All testing code. Do test harnesses go here too? > > Layout/ # Would be nice to have a better name since these test much >> mor

[webkit-dev] Question on Inline element

Hi All, I was trying to develop my expertise by looking at some of the open issues & I was looking intohttps://bugs.webkit.org/show_bug.cgi?id=22764.(Issue with Windows build). We have done a preliminarily analysis & I want to get little help so that