[webkit-dev] GCONF proxy settings and webkit
Hi! I want to know if there's a way to make WEBKIT browser to use gconf proxy settings for navigating? Regards, Ariel Calzada Activity Central http://www.activitycentral.com ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Is UseV8.cmake still used?
Kentaro Hara hara...@chromium.org writes: EFL and other ports used to have an option to build with V8, but it looks like the option is no longer supported. For example, UseV8.cmake is already out of sync with existing V8 binding files. - Would it be OK to remove UseV8.cmake? - Would it be OK to remove #if PLATFORM(CHROMIUM) from all V8 binding files? If anyone has a plan to support the option in the near future, I'll keep them as is. No objections from the EFL side, I guess -- it's never been used by any of our build bots and I'm not even sure if the Samsung folks have finished their work on it. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Adding blending mode to WebKit canvas
On Nov 9, 2012, at 4:39 PM, Rik Cabanier caban...@gmail.com wrote: Hi, I'd like to add support for blending modes to Canvas. The spec for this feature can be found here: https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#canvascompositingandblending The implementation will be tracked by a meta bug: https://bugs.webkit.org/show_bug.cgi?id=100069 I also attached a large patch that shows how this feature can be implemented. Looking at your patches on bug 100069 and bug 101804, I actually have some questions. If I understand your API changes correctly, the 'globalCompositeOperation' property gets more keywords. The new keywords will be the same as for the 'blend-mode' property of the CSS Compositing spec. Does it mean that blend mode always will use the compositing operator 'source-over'? The example implementation of GraphicsContext::setPlatformCompositeOperation on CG indicates that it would be possible to combine blend modes with different compositing operators in CG already. If you set both with the same property 'globalCompositeOperation', it won't be possible to mix them in the future. If more implementations are capable to support mixing alpha compositing and blending, the property can not be changed anymore. Wouldn't it be better to add a new property to canvas for blending? At the beginning, implementations are just require to use different blend modes in combination with 'source-over'. Btw. why is this addition in CSS Compositing and not in the Canvas spec? Greetings, Dirk Please let me know of any concerns. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Is UseV8.cmake still used?
IIRC, Android (non-Chrome) uses V8. I'm not sure whether PLATFORM(CHROMIUM) is on there. On Sun, Nov 11, 2012 at 3:59 PM, Kentaro Hara hara...@chromium.org wrote: EFL and other ports used to have an option to build with V8, but it looks like the option is no longer supported. For example, UseV8.cmake is already out of sync with existing V8 binding files. - Would it be OK to remove UseV8.cmake? - Would it be OK to remove #if PLATFORM(CHROMIUM) from all V8 binding files? If anyone has a plan to support the option in the near future, I'll keep them as is. -- Kentaro Hara, Tokyo, Japan ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Is UseV8.cmake still used?
The last time I checked, Qt folks were interested in being able to use V8 as well as JSC. I'm not sure if their needs have changed since then. - R. Niwa On Nov 10, 2012 11:00 PM, Kentaro Hara hara...@chromium.org wrote: EFL and other ports used to have an option to build with V8, but it looks like the option is no longer supported. For example, UseV8.cmake is already out of sync with existing V8 binding files. - Would it be OK to remove UseV8.cmake? - Would it be OK to remove #if PLATFORM(CHROMIUM) from all V8 binding files? If anyone has a plan to support the option in the near future, I'll keep them as is. -- Kentaro Hara, Tokyo, Japan ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Adding blending mode to WebKit canvas
On Sun, Nov 11, 2012 at 5:25 PM, Dirk Schulze dschu...@adobe.com wrote: On Nov 9, 2012, at 4:39 PM, Rik Cabanier caban...@gmail.com wrote: Hi, I'd like to add support for blending modes to Canvas. The spec for this feature can be found here: https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#canvascompositingandblending The implementation will be tracked by a meta bug: https://bugs.webkit.org/show_bug.cgi?id=100069 I also attached a large patch that shows how this feature can be implemented. Looking at your patches on bug 100069 and bug 101804, I actually have some questions. If I understand your API changes correctly, the 'globalCompositeOperation' property gets more keywords. The new keywords will be the same as for the 'blend-mode' property of the CSS Compositing spec. Does it mean that blend mode always will use the compositing operator 'source-over'? Correct. From the spec [1]: Blending is not separated from compositing in canvas 2d. If a blend operation is selected its results must always be composited with the ‘ source-over’https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#porterduffcompositingoperators_srcover compositing mode. The example implementation of GraphicsContext::setPlatformCompositeOperation on CG indicates that it would be possible to combine blend modes with different compositing operators in CG already. Unfortunately, CG can't do this (yet). The code is written to minimize change and to make this split easy to implement in the future. If you set both with the same property 'globalCompositeOperation', it won't be possible to mix them in the future. If more implementations are capable to support mixing alpha compositing and blending, the property can not be changed anymore. Well, it can still be changed. If in the future, people feel the need to specify blending and compositing separately, we can define a new property (globalBlendOperation?) that specifies the blending operation before globalCompositeOperation. If a user specifies a blending operation in both globalBlendOperation and globalCompositeOperation, we can define that globalCompositeOperation reverts to source-over. Wouldn't it be better to add a new property to canvas for blending? At the beginning, implementations are just require to use different blend modes in combination with 'source-over'. That could work too. There was a mailing list conversation about this a couple of months ago, and people were evenly split on the subject. The vast majority of cases will use 'source-over' in combination with blending so maybe it's best to keep it simple... Btw. why is this addition in CSS Compositing and not in the Canvas spec? I got feedback that it was best to specify this in the compositing spec since it explains in detail how the formulas work and has pretty pictures. The canvas spec can be changed to refer to the blending spec. Rik 1: https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#canvascompositingandblending ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Is UseV8.cmake still used?
On Sun, Nov 11, 2012 at 6:09 PM, Hajime Morrita morr...@chromium.org wrote: IIRC, Android (non-Chrome) uses V8. I'm not sure whether PLATFORM(CHROMIUM) is on there. non-Chromium Android is no longer supported on trunk. On Sun, Nov 11, 2012 at 6:32 PM, Ryosuke Niwa rn...@webkit.org wrote: The last time I checked, Qt folks were interested in being able to use V8 as well as JSC. I'm not sure if their needs have changed since then. I don't believe they are anymore. Adam ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Adding blending mode to WebKit canvas
On Nov 11, 2012, at 6:59 PM, Rik Cabanier caban...@gmail.com wrote: Wouldn't it be better to add a new property to canvas for blending? At the beginning, implementations are just require to use different blend modes in combination with 'source-over'. That could work too. There was a mailing list conversation about this a couple of months ago, and people were evenly split on the subject. The vast majority of cases will use 'source-over' in combination with blending so maybe it's best to keep it simple... It doesn't make sense to me for blend mode and composite operator to be separate in CSS, but combined in Canvas. Either there are valid use cases for specifying them separately or there are not. I cannot imagine how this could differ between Canvas and CSS. Regards, Maciej ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Adding blending mode to WebKit canvas
On Sun, Nov 11, 2012 at 8:43 PM, Maciej Stachowiak m...@apple.com wrote: On Nov 11, 2012, at 6:59 PM, Rik Cabanier caban...@gmail.com wrote: Wouldn't it be better to add a new property to canvas for blending? At the beginning, implementations are just require to use different blend modes in combination with 'source-over'. That could work too. There was a mailing list conversation about this a couple of months ago, and people were evenly split on the subject. The vast majority of cases will use 'source-over' in combination with blending so maybe it's best to keep it simple... It doesn't make sense to me for blend mode and composite operator to be separate in CSS, but combined in Canvas. Either there are valid use cases for specifying them separately or there are not. I cannot imagine how this could differ between Canvas and CSS. There are cases where it makes sense to have them as separate properties. To be honest, the main reason that the Canvas proposal combines them, is because it is not possible to implement this efficiently using Core Graphics. If we break it up in 2 operations, we have to document the correct behavior (= blending does not force source-over for blending) because the spec can't be changed later. This means that Safari and Firefox for Mac can only implement part of the spec... I prefer to have a consistent implementation that can be extended later as opposed to a 'correct' API that is inconsistently implemented. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Adding blending mode to WebKit canvas
On Sunday, November 11, 2012, Rik Cabanier wrote:
On Sun, Nov 11, 2012 at 8:43 PM, Maciej Stachowiak
m...@apple.comjavascript:_e({}, 'cvml', 'm...@apple.com');
wrote:
On Nov 11, 2012, at 6:59 PM, Rik Cabanier
caban...@gmail.comjavascript:_e({}, 'cvml', 'caban...@gmail.com');
wrote:
Wouldn't it be better to add a new property to canvas for blending? At
the beginning, implementations are just require to use different blend
modes in combination with 'source-over'.
That could work too.
There was a mailing list conversation about this a couple of months ago,
and people were evenly split on the subject.
The vast majority of cases will use 'source-over' in combination with
blending so maybe it's best to keep it simple...
It doesn't make sense to me for blend mode and composite operator to be
separate in CSS, but combined in Canvas. Either there are valid use cases
for specifying them separately or there are not. I cannot imagine how this
could differ between Canvas and CSS.
To be fair, the 'globalCompositOperator' property mixed the compositing
modes with some blend modes already. Which is the fault of the WebKit
implementation. IIRC they have been removed from the Canvas part of the
HTML spec for some time, but were added later again. Now we have multiple
independent implementations that support all currently specified operators.
Greetings,
Dirk
There are cases where it makes sense to have them as separate properties.
To be honest, the main reason that the Canvas proposal combines them, is
because it is not possible to implement this efficiently using Core
Graphics.
If we break it up in 2 operations, we have to document the correct
behavior (= blending does not force source-over for blending) because the
spec can't be changed later.
This means that Safari and Firefox for Mac can only implement part of the
spec...
I prefer to have a consistent implementation that can be extended later as
opposed to a 'correct' API that is inconsistently implemented.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Adding blending mode to WebKit canvas
On Sun, Nov 11, 2012 at 9:52 PM, Dirk Schulze k...@webkit.org wrote: On Sunday, November 11, 2012, Rik Cabanier wrote: On Sun, Nov 11, 2012 at 8:43 PM, Maciej Stachowiak m...@apple.com wrote: On Nov 11, 2012, at 6:59 PM, Rik Cabanier caban...@gmail.com wrote: Wouldn't it be better to add a new property to canvas for blending? At the beginning, implementations are just require to use different blend modes in combination with 'source-over'. That could work too. There was a mailing list conversation about this a couple of months ago, and people were evenly split on the subject. The vast majority of cases will use 'source-over' in combination with blending so maybe it's best to keep it simple... It doesn't make sense to me for blend mode and composite operator to be separate in CSS, but combined in Canvas. Either there are valid use cases for specifying them separately or there are not. I cannot imagine how this could differ between Canvas and CSS. To be fair, the 'globalCompositOperator' property mixed the compositing modes with some blend modes already. Which is the fault of the WebKit implementation. IIRC they have been removed from the Canvas part of the HTML spec for some time, but were added later again. Now we have multiple independent implementations that support all currently specified operators. Is this the 'darker' compositing mode or are there others? ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Is UseV8.cmake still used?
Hi, We were interested in it, but not now. All Qt-V8 related codepaths were removed from tree after WebKit2 with V8 was rejected by the community: http://lists.webkit.org/pipermail/webkit-dev/2012-April/thread.html#20407 http://lists.webkit.org/pipermail/webkit-dev/2012-May/thread.html#20869 http://lists.webkit.org/pipermail/webkit-dev/2012-June/thread.html#20903 Otherwise QtWebKit doesn't use cmake, but qmake. ;-) br, Ossy Ryosuke Niwa írta: The last time I checked, Qt folks were interested in being able to use V8 as well as JSC. I'm not sure if their needs have changed since then. ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
