Re: [webkit-dev] Media Server Development

2013-02-01 Thread Philippe Normand
You should write a new MediaPlayerPrivate backend instead of hacking the
MediaPlayerPrivateGStreamer one.

Philippe

On Thu, 2013-01-31 at 23:04 +0530, Kiran K wrote:
 HI All,
 
 I am working on QtWebKit  on Media Server development. Basic Idea is
 to run Gstreamer in seperate process which acts like a Media server.
 The calls  from WebKit in MediaPlayerPrivateGStreamer.cpp are routed
 to Media Server via DBUS. Media Server implements the methods in
 MediaPlayerPrivateGStreamer class. I am basically doing this to have
 control over the resources like maximum playback instances, hw codec
 control etc. I am able to do achieve playback to some extent. I am
 facing some problems  (race conditions) especially when deleting
 playback instance. From the logs i concluded that when duration()
 function is made  and is waiting for response from server,
 ~MediaPlayerPrivateGStreamer destructor is getting called. (some times
 vice versa too). I am suspecting that the MediaPlayer object is being
 shared between two threads (or across timers). Can anybody give me
 some pointers about HTMLMediaElement  and the timers involved? Any
 help is appreciated.
 
 Thanks,
 Arun
 
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev


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


Re: [webkit-dev] Media Server Development

2013-02-01 Thread Kiran K
Yes Phippe, you are right. I will start doing it , once I am done with
hacking of MediaPlayerPrivateGstreamer.

Regards,
Kiran


On Fri, Feb 1, 2013 at 4:26 PM, Philippe Normand ph...@igalia.com wrote:

 You should write a new MediaPlayerPrivate backend instead of hacking the
 MediaPlayerPrivateGStreamer one.

 Philippe

 On Thu, 2013-01-31 at 23:04 +0530, Kiran K wrote:
  HI All,
 
  I am working on QtWebKit  on Media Server development. Basic Idea is
  to run Gstreamer in seperate process which acts like a Media server.
  The calls  from WebKit in MediaPlayerPrivateGStreamer.cpp are routed
  to Media Server via DBUS. Media Server implements the methods in
  MediaPlayerPrivateGStreamer class. I am basically doing this to have
  control over the resources like maximum playback instances, hw codec
  control etc. I am able to do achieve playback to some extent. I am
  facing some problems  (race conditions) especially when deleting
  playback instance. From the logs i concluded that when duration()
  function is made  and is waiting for response from server,
  ~MediaPlayerPrivateGStreamer destructor is getting called. (some times
  vice versa too). I am suspecting that the MediaPlayer object is being
  shared between two threads (or across timers). Can anybody give me
  some pointers about HTMLMediaElement  and the timers involved? Any
  help is appreciated.
 
  Thanks,
  Arun
 
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev



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


Re: [webkit-dev] Enabling unprefixed CSS Transitions by default.

2013-02-01 Thread Alexis Menard
Hi,

It's now landed http://trac.webkit.org/changeset/141578

Please CC me on bugs that could occur and related to it.

I will move on the CSS Animations now.

Thanks.

On Tue, Jan 29, 2013 at 11:22 PM, Eric Seidel e...@webkit.org wrote:
 Thank you for sharing!

 It appears that unless you're logged into WordPress (I had to go dig
 up my credentials) you just get a 404.


 On Tue, Jan 29, 2013 at 6:17 PM, Dean Jackson d...@apple.com wrote:
 Related: when the unprefixed transitions are enabled by default, we plan
 to make a long-overdue blog post on Recent Updates to Transitions and 
 Animations
 where recent means about 2 or 3 years :)

 http://www.webkit.org/blog/?p=2233preview=true

 The idea is that it would cover all the interesting things we've added, even 
 if
 we think most people know about them. Feel free to edit the draft (if that's 
 possible
 - otherwise email me), especially if there are features we've forgotten.

 Dean


 On 30/01/2013, at 8:03 AM, Alexis Menard ale...@webkit.org wrote:

 Hi,

 Last month I started working on supporting unprefixed CSS Transitions
 in WebKit. Today this work is guarded behind
 CSS_TRANSFORMS_ANIMATIONS_TRANSITIONS_UNPREFIXED enabled by default in
 trunk (but disabled in Chrome and probably release branches of other
 ports). After various patches we (Dean Jackson and myself) feel
 confident that the work on the transitions is ready for prime time. We
 still have bugs open in our bug tracker but that doesn't block the
 unprefixed version to go live.

 So the proposal is the following one :
 - Rename CSS_TRANSFORMS_ANIMATIONS_TRANSITIONS_UNPREFIXED to
 CSS_TRANSFORMS_ANIMATIONS_UNPREFIXED to cover the future work for
 unprefixing the animations and the transforms (that I plan to focus
 after this).
 - Ship CSS Transitions unprefixed enabled by default with no feature
 flag to disable it.

 My proposal is tracked here : https://bugs.webkit.org/show_bug.cgi?id=108216

 We can also be proud to say our implementation is maybe the most
 complete one (thanks to the various people involved).

 On a side note the usage of prefixed/unprefixed version is monitored
 through the FeatureObserver so we can later in the future have an idea
 of the usage and maybe remove the prefixed support.

 Thoughts?

 Patched landed :
 http://trac.webkit.org/changeset/141119
 http://trac.webkit.org/changeset/140560
 http://trac.webkit.org/changeset/140448
 http://trac.webkit.org/changeset/140010
 http://trac.webkit.org/changeset/139922
 http://trac.webkit.org/changeset/139762
 http://trac.webkit.org/changeset/139200
 http://trac.webkit.org/changeset/139106
 http://trac.webkit.org/changeset/139070
 http://trac.webkit.org/changeset/138728
 http://trac.webkit.org/changeset/138721
 http://trac.webkit.org/changeset/138184

 Thanks.

 --
 Software Engineer @
 Intel Open Source Technology Center
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev

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



-- 
Software Engineer @
Intel Open Source Technology Center
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Enabling unprefixed CSS Transitions by default.

2013-02-01 Thread Kenneth Rohde Christiansen
Nice work Alexis!

Kenneth

On Fri, Feb 1, 2013 at 1:29 PM, Alexis Menard ale...@webkit.org wrote:
 Hi,

 It's now landed http://trac.webkit.org/changeset/141578

 Please CC me on bugs that could occur and related to it.

 I will move on the CSS Animations now.

 Thanks.

 On Tue, Jan 29, 2013 at 11:22 PM, Eric Seidel e...@webkit.org wrote:
 Thank you for sharing!

 It appears that unless you're logged into WordPress (I had to go dig
 up my credentials) you just get a 404.


 On Tue, Jan 29, 2013 at 6:17 PM, Dean Jackson d...@apple.com wrote:
 Related: when the unprefixed transitions are enabled by default, we plan
 to make a long-overdue blog post on Recent Updates to Transitions and 
 Animations
 where recent means about 2 or 3 years :)

 http://www.webkit.org/blog/?p=2233preview=true

 The idea is that it would cover all the interesting things we've added, 
 even if
 we think most people know about them. Feel free to edit the draft (if 
 that's possible
 - otherwise email me), especially if there are features we've forgotten.

 Dean


 On 30/01/2013, at 8:03 AM, Alexis Menard ale...@webkit.org wrote:

 Hi,

 Last month I started working on supporting unprefixed CSS Transitions
 in WebKit. Today this work is guarded behind
 CSS_TRANSFORMS_ANIMATIONS_TRANSITIONS_UNPREFIXED enabled by default in
 trunk (but disabled in Chrome and probably release branches of other
 ports). After various patches we (Dean Jackson and myself) feel
 confident that the work on the transitions is ready for prime time. We
 still have bugs open in our bug tracker but that doesn't block the
 unprefixed version to go live.

 So the proposal is the following one :
 - Rename CSS_TRANSFORMS_ANIMATIONS_TRANSITIONS_UNPREFIXED to
 CSS_TRANSFORMS_ANIMATIONS_UNPREFIXED to cover the future work for
 unprefixing the animations and the transforms (that I plan to focus
 after this).
 - Ship CSS Transitions unprefixed enabled by default with no feature
 flag to disable it.

 My proposal is tracked here : 
 https://bugs.webkit.org/show_bug.cgi?id=108216

 We can also be proud to say our implementation is maybe the most
 complete one (thanks to the various people involved).

 On a side note the usage of prefixed/unprefixed version is monitored
 through the FeatureObserver so we can later in the future have an idea
 of the usage and maybe remove the prefixed support.

 Thoughts?

 Patched landed :
 http://trac.webkit.org/changeset/141119
 http://trac.webkit.org/changeset/140560
 http://trac.webkit.org/changeset/140448
 http://trac.webkit.org/changeset/140010
 http://trac.webkit.org/changeset/139922
 http://trac.webkit.org/changeset/139762
 http://trac.webkit.org/changeset/139200
 http://trac.webkit.org/changeset/139106
 http://trac.webkit.org/changeset/139070
 http://trac.webkit.org/changeset/138728
 http://trac.webkit.org/changeset/138721
 http://trac.webkit.org/changeset/138184

 Thanks.

 --
 Software Engineer @
 Intel Open Source Technology Center
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev

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



 --
 Software Engineer @
 Intel Open Source Technology Center
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev



-- 
Kenneth Rohde Christiansen
Senior Engineer, WebKit, Qt, EFL
Phone  +45 4294 9458 / E-mail kenneth at webkit.org

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


[webkit-dev] Adding blending mode to background images

2013-02-01 Thread Rik Cabanier
Hi,

I'd like to add support for blending of background images.
The spec for this feature can be found here: *
https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#background-blend-mode
*

The implementation will be tracked by a meta bug: *
https://bugs.webkit.org/show_bug.cgi?id=108546*

Please let me know of any concerns.
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
https://lists.webkit.org/mailman/listinfo/webkit-dev


Re: [webkit-dev] Adding blending mode to background images

2013-02-01 Thread Dirk Schulze
Hi Rik,

Can you just add an example for the better understanding please?

Greetings,
Dirk

On Feb 2, 2013, at 6:43 AM, Rik Cabanier caban...@gmail.com wrote:

 Hi,
 
 I'd like to add support for blending of background images.
 The spec for this feature can be found here: 
 https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#background-blend-mode
 
 The implementation will be tracked by a meta bug: 
 https://bugs.webkit.org/show_bug.cgi?id=108546
 
 Please let me know of any concerns.
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev

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


Re: [webkit-dev] Adding blending mode to background images

2013-02-01 Thread Rik Cabanier
Sure!

For instance:

!DOCTYPE HTML
html
head
style
.example {
width: 500px;
height: 500px;
background-image: url(a.png), url(b.png);
-webkit-background-blend-mode: screen, screen;
}
/style
/head
body style=background-color: green;
  div class=example/div
/body
/html


The div in this document contains 2 background images. The
'-webkit-background-blend-mode' property assigns a blending mode to each of
them.
It works very similar to '-webkit-background-composite' [1]

The images blend with each other and their existing backdrop as stated by
the CSS drawing model [2].
This feature will give designers the ability to blend layers of images
together much like they do in graphics applications [3]

Rik

1: https://www.webkit.org/blog/181/css-masks/
2: http://www.w3.org/TR/CSS21/zindex.html
3: see *http://www.youtube.com/watch?v=diJzT-sHizg* for links to tutorials.

On Fri, Feb 1, 2013 at 12:09 PM, Dirk Schulze k...@webkit.org wrote:

 Hi Rik,

 Can you just add an example for the better understanding please?

 Greetings,
 Dirk

 On Feb 2, 2013, at 6:43 AM, Rik Cabanier caban...@gmail.com wrote:

  Hi,
 
  I'd like to add support for blending of background images.
  The spec for this feature can be found here:
 https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#background-blend-mode
 
  The implementation will be tracked by a meta bug:
 https://bugs.webkit.org/show_bug.cgi?id=108546
 
  Please let me know of any concerns.
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev


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


Re: [webkit-dev] Adding blending mode to background images

2013-02-01 Thread Benjamin Poulain
On Fri, Feb 1, 2013 at 12:44 PM, Rik Cabanier caban...@gmail.com wrote:

 background-image: url(a.png), url(b.png);
 -webkit-background-blend-mode: screen, screen;


Out of curiosity:

I am probably way too late for the party, but why not blend
surface-to-surface? E.g.
background-image: blend(url(foo.png), url(bar.png), difference).

This is in order to easily stack them:
background-image: blend(blend(url(foo.png), url(bar.png), difference),
url(giraffe.gif), screen).

Although, maybe we don't want that as it could get more difficult to
optimize...

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


Re: [webkit-dev] Adding blending mode to background images

2013-02-01 Thread Dirk Schulze

On Feb 2, 2013, at 8:01 AM, Benjamin Poulain benja...@webkit.org wrote:

 On Fri, Feb 1, 2013 at 12:44 PM, Rik Cabanier caban...@gmail.com wrote:
 background-image: url(a.png), url(b.png);
 -webkit-background-blend-mode: screen, screen;
 
 Out of curiosity:
 
 I am probably way too late for the party, but why not blend 
 surface-to-surface? E.g.
 background-image: blend(url(foo.png), url(bar.png), difference).
 
 This is in order to easily stack them:
 background-image: blend(blend(url(foo.png), url(bar.png), difference), 
 url(giraffe.gif), screen).

I like the idea, but it has the big disadvantage that you can not repeat an 
image, change origin and size before blending with the next layer.

Greetings,
Dirk

 
 Although, maybe we don't want that as it could get more difficult to 
 optimize...
 
 Benjamin
 ___
 webkit-dev mailing list
 webkit-dev@lists.webkit.org
 https://lists.webkit.org/mailman/listinfo/webkit-dev

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


Re: [webkit-dev] Adding blending mode to background images

2013-02-01 Thread Rik Cabanier
you will be able to do this by using the fully featured 'mix-blend-mode'
property [1].

for instance, if you want 2 images to blend with each other, but not with
their background:

div style=isolation: isolate - anything that creates a stacking context

img src='foo.png'/
img src='bar.png' style='mix-blend-mode: difference'/

/div



1:
https://dvcs.w3.org/hg/FXTF/rawfile/tip/compositing/index.html#mix-blend-mode

On Fri, Feb 1, 2013 at 1:01 PM, Benjamin Poulain benja...@webkit.orgwrote:

 On Fri, Feb 1, 2013 at 12:44 PM, Rik Cabanier caban...@gmail.com wrote:

 background-image: url(a.png), url(b.png);
 -webkit-background-blend-mode: screen, screen;


 Out of curiosity:

 I am probably way too late for the party, but why not blend
 surface-to-surface? E.g.
 background-image: blend(url(foo.png), url(bar.png), difference).

 This is in order to easily stack them:
 background-image: blend(blend(url(foo.png), url(bar.png), difference),
 url(giraffe.gif), screen).

 Although, maybe we don't want that as it could get more difficult to
 optimize...

 Benjamin

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


Re: [webkit-dev] Adding blending mode to background images

2013-02-01 Thread Rik Cabanier
On Fri, Feb 1, 2013 at 1:08 PM, Dirk Schulze dschu...@adobe.com wrote:


 On Feb 2, 2013, at 8:01 AM, Benjamin Poulain benja...@webkit.org wrote:

  On Fri, Feb 1, 2013 at 12:44 PM, Rik Cabanier caban...@gmail.com
 wrote:
  background-image: url(a.png), url(b.png);
  -webkit-background-blend-mode: screen, screen;
 
  Out of curiosity:
 
  I am probably way too late for the party, but why not blend
 surface-to-surface? E.g.
  background-image: blend(url(foo.png), url(bar.png), difference).
 
  This is in order to easily stack them:
  background-image: blend(blend(url(foo.png), url(bar.png),
 difference), url(giraffe.gif), screen).

 I like the idea, but it has the big disadvantage that you can not repeat
 an image, change origin and size before blending with the next layer.


True. This feels more like a filter where you pull different sources in.



 
  Although, maybe we don't want that as it could get more difficult to
 optimize...
 
  Benjamin
  ___
  webkit-dev mailing list
  webkit-dev@lists.webkit.org
  https://lists.webkit.org/mailman/listinfo/webkit-dev


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