Announcement

Collapse
No announcement yet.

WebKitGTK+ Being Ported To Wayland

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • WebKitGTK+ Being Ported To Wayland

    Phoronix: WebKitGTK+ Being Ported To Wayland

    Developers at the Igalia open-source consulting firm are currently working on porting WebKitGTK+ / WebKit2 to Wayland...

    http://www.phoronix.com/vr.php?view=MTQwNTM

  • #2
    X11 transition teething pains.

    Comment


    • #3
      ?

      Originally posted by dh04000 View Post
      X11 transition teething pains.
      For teething pains do you mean to join in the dev mailing list and to ask how to do something?
      LOL
      I usually call that a normal behaviour, but if you prefer "teething pains"... :-)

      Comment


      • #4
        Blink

        So what happens with Blink?
        WebKit and Blink are going to be maintained separately, or they're going to merge back into one branch again?

        I guess much of what applies to get WebKit ported to Wayland could also be used to port Blink.

        Comment


        • #5
          Originally posted by uid313 View Post
          So what happens with Blink?
          WebKit and Blink are going to be maintained separately, or they're going to merge back into one branch again?

          I guess much of what applies to get WebKit ported to Wayland could also be used to port Blink.
          Just a note that this isn't Webkit in general - it's specifically WebkitGtk, as used mostly by Gnome and a handful of other projects. Some of the code may be sharable with general Webkit and Blink, but much of it is probably specific to this project.

          Comment


          • #6
            Originally posted by Delgarde View Post
            Just a note that this isn't Webkit in general - it's specifically WebkitGtk, as used mostly by Gnome and a handful of other projects. Some of the code may be sharable with general Webkit and Blink, but much of it is probably specific to this project.
            In particular, they're discussing how the webkit2 api works with multiprocess rendering. That's exactly one of the major differences between it and Chrome/Blink. So while it's possible the same general concept may apply between the projects, the particular code is going to be completely different.

            Comment


            • #7
              How about they actually finish the WebKit 2 port and optimize it while they're at it? It's an absolute pig presently in Debian with GNOME 3.8.2-3.8.3. The product stalls quite often and testing the status on html5test.com is embarrassingly slow.

              Comment


              • #8
                Originally posted by uid313 View Post
                So what happens with Blink?
                WebKit and Blink are going to be maintained separately, or they're going to merge back into one branch again?

                I guess much of what applies to get WebKit ported to Wayland could also be used to port Blink.
                Who gives a rat's ass about Blink on GTK? Google Blink with GTK+ is what they'll maintain. WebKitGTK+ went with WebKit proper and not Blink.

                Comment


                • #9
                  Sharing wayland surfaces between processes? We have a NOKIA extension for that. Though why wouldn't http://www.khronos.org/registry/egl/..._drm_image.txt work? That is what wayland uses internally between clients and compositor.

                  Comment

                  Working...
                  X