Re: [webkit-dev] WebKit2GTK+ breakage due to removal of WKPageResourceLoadClient

2013-01-22 Thread Carlos Garcia Campos
El lun, 21-01-2013 a las 17:57 -0800, Sam Weinig escribió: > Hi Mario, > > The motivation of the change was to reduce the chatter between the > WebProcess and UIProcess and reduce the amount of knowledge the > UIProcess has about the internals of the WebProcess. We will also be > removing the UIP

Re: [webkit-dev] distributed build for WebKit on Mac OS 10.8

2013-01-22 Thread Sergio Villar Senin
En 21/01/13 19:39, Zeno Albisser escribiu: > I was more successful using distcc > from: http://www.opensource.apple.com/source/distcc/ > This one seemed to work fairly well. The only problem I had was that Qt > is not actually using xcodebuild. > Therefore I could not make use of any bonjour servi

Re: [webkit-dev] Out-of-process networking and potential for sharing memory cache (was Re: Feature Announcement: Moving HTML Parser off the Main Thread)

2013-01-22 Thread Sergio Villar Senin
En 21/01/13 23:07, Maciej Stachowiak escribiu: > > On Jan 21, 2013, at 11:23 AM, Adam Barth wrote: > >> Some folks have pointed out to me off thread that I'm coming off as >> angry and harsh. I would like to apologize for my tone. >> >> My goal here is not to obstruct or block your progress on

Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME

2013-01-22 Thread TAMURA, Kent
The two mail threads bounce back and forth between Hixie's opinion and yours. Was there a conclusion reached anywhere on what to do with datetime and datetime-local? We agreed that existing implementations of input[type=datetime] were wrong. But we have no conclusion of the type renaming and

Re: [webkit-dev] Out-of-process networking and potential for sharing memory cache (was Re: Feature Announcement: Moving HTML Parser off the Main Thread)

2013-01-22 Thread Maciej Stachowiak
On Jan 22, 2013, at 12:17 AM, Sergio Villar Senin wrote: > En 21/01/13 23:07, Maciej Stachowiak escribiu: >> >> On Jan 21, 2013, at 11:23 AM, Adam Barth wrote: >> >> Thanks, Adam. It's fine to pick up the conversation later, and we're >> certainly open to iterating beyond what we do first. >

Re: [webkit-dev] Please do not enable ENABLE_INPUT_TYPE_DATETIME

2013-01-22 Thread Maciej Stachowiak
On Jan 22, 2013, at 12:32 AM, "TAMURA, Kent" wrote: > > >> The two mail threads bounce back and forth between Hixie's opinion and >> yours. Was there a conclusion reached anywhere on what to do with datetime >> and datetime-local? > > We agreed that existing implementations of input[type=date

[webkit-dev] Dropping support for Windows versions before XP SP2

2013-01-22 Thread Árvai Zoltán
Hi, Currently WebKit is configured to be compatible with Windows 2000 and newer Windows versions. After r139514 using InterlockedIncrement64 is required for int64_t atomicIncrement function to be able to build WebKit2 for Windows. On 32 bit target this method is supported in XP SP2 and later.

Re: [webkit-dev] WebKit2GTK+ breakage due to removal of WKPageResourceLoadClient

2013-01-22 Thread Mario Sanchez Prada
[Replying both Carlos and Sam's mail at once] Hi, > El lun, 21-01-2013 a las 17:57 -0800, Sam Weinig escribió: > > Hi Mario, > > > > The motivation of the change was to reduce the chatter between the > > WebProcess and UIProcess and reduce the amount of knowledge the > > UIProcess has about the i

Re: [webkit-dev] Out-of-process networking and potential for sharing memory cache (was Re: Feature Announcement: Moving HTML Parser off the Main Thread)

2013-01-22 Thread Sergio Villar Senin
En 22/01/13 09:52, Maciej Stachowiak escribiu: >> That'd be awesome, at least an overview document that could help people >> to understand the whole picture and the main advantages/drawbacks of the >> selected design. > > What topics are you interested in? I could probably write decent explanation

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Allan Sandfeld Jensen
On Monday 21 January 2013, Benjamin Poulain wrote: > On Mon, Jan 21, 2013 at 7:00 AM, Zoltan Herczeg wrote: > > In WebKit both RGBA and BGRA formats are used for different purposes and > > different platforms in WebKit. Do we have a policy which one we prefer? > > It would be nice to reduce conver

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Zoltan Herczeg
>> Where in WebKit do you experience problems with color conversion? As for me WebKit2 transmits BGRA images, which needs to be converted to RGBA before it is uploaded to a texture on GLES 2.0. These conversions seems computation heavy for certain animations, and I was wondered whether do we reall

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread noam . rosenthal
I would say that the right way to go about improving pixel transfer (which is what you're trying to do, I believe...) is with OS-provided graphics surfaces; On embedded systems those are usually provided and there are of course solutions for windows and Mac. When using graphics surfaces, you don

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Allan Sandfeld Jensen
On Tuesday 22 January 2013, Zoltan Herczeg wrote: > >> Where in WebKit do you experience problems with color conversion? > > As for me WebKit2 transmits BGRA images, which needs to be converted to > RGBA before it is uploaded to a texture on GLES 2.0. These conversions > seems computation heavy fo

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread John Bauman
Couldn't you just swizzle the value in whatever shader you use? Or you could use EXT_texture_format_BGRA or APPLE_texture_format_BGRA. Also, an optimized BGRA<->RGBA conversion is about the same cost as a memcpy, so if you have any memcpys you need to do you could possibly replace one with

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Allan Sandfeld Jensen
On Tuesday 22 January 2013, John Bauman wrote: > Couldn't you just swizzle the value in whatever shader you use? Or you > could use EXT_texture_format_BGRA or APPLE_texture_format_BGRA. > > Also, an optimized BGRA<->RGBA conversion is about the same cost as a > memcpy, so if you have any m

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Benjamin Poulain
On Tue, Jan 22, 2013 at 12:39 PM, Allan Sandfeld Jensen wrote: > memcpy is heavily optimized for different architectures and even > subarchitectures. Unless you take the time to write several architecture > specific BGRA<->RGBA conversions it will never be as fast as memcpy. > This is actually v

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Balazs Kelemen
On 01/22/2013 05:14 PM, Zoltan Herczeg wrote: Where in WebKit do you experience problems with color conversion? As for me WebKit2 transmits BGRA images, which needs to be converted to RGBA before it is uploaded to a texture on GLES 2.0. These conversions seems computation heavy for certain anima

Re: [webkit-dev] RGBA8 and BGRA8 formats in WebKit

2013-01-22 Thread Allan Sandfeld Jensen
On Wednesday 23 January 2013, Balazs Kelemen wrote: > On 01/22/2013 05:14 PM, Zoltan Herczeg wrote: > >>> Where in WebKit do you experience problems with color conversion? > > > > As for me WebKit2 transmits BGRA images, which needs to be converted to > > RGBA before it is uploaded to a texture on

[webkit-dev] Followup on removing webkitNotifications.createHTMLNotification

2013-01-22 Thread Adam Barth
As discussed in February 2012 [1], we have been deprecating the webkitNotifications.createHTMLNotification API for almost a year. According to FeatureObserver, the API is used in only 0.0008% of web page views, indicating that we have been successful in depreciating it. I've posted a patch to remo