Announcement

Collapse
No announcement yet.

Google Replacing GTK2 With Aura In Chrome 35

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

  • phoronix
    started a topic Google Replacing GTK2 With Aura In Chrome 35

    Google Replacing GTK2 With Aura In Chrome 35

    Phoronix: Google Replacing GTK2 With Aura In Chrome 35

    Google will finally be migrating from GTK2 to their own Aura UI code with a target of Chrome/Chromium 35...

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

  • narciso
    replied
    This version is having issues with system borders and title checked in ubuntu 14.04 ambiance theme. When the window is maximized it offsets the window a bit to the right. Works as it should when system borders and title are unchecked.

    Leave a comment:


  • ChrisXY
    replied
    Well, I definitely noticed how the initial website rendering after loading is a lot smoother for at least some websites, like e.g. google plus or youtube.

    edit: but font rendering is looking very different. Not sure if it's better or worse yet. At least they don't have colored anti aliasing by default! Yay!

    FYI, there are also builds for chromium from google, not just for chrome. Shamelessly copied from an AUR package:
    Code:
    wget http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux_x64/$(curl -s "http://commondatastorage.googleapis.com/chromium-browser-snapshots/Linux_x64/LAST_CHANGE")/chrome-linux.zip
    Despite it being called chrome-linux.zip it is actually chromium. But of course it is still a binary from an american company, so if you're paranoid, rather compile it yourself.

    The difference between chromium and chrome: If there is tracking or phone-home code in chromium enabled, it's a bug that's getting fixed. In chrome it's a feature.

    Leave a comment:


  • pandev92
    replied
    Originally posted by Alejandro Nova View Post
    The requirement set is strict. You need:
    - Mesa compiled with VDPAU support. That means: if you use Ubuntu, you need at least a recompile.
    - VDPAU libraries.

    HIGHLY RECOMMENDED:
    - Mesa 10.1. You need GLSL 1.50 for some HW decoding paths.
    - vdpauinfo. Check if your VDPAU setup is working.
    - The following in your ~/.bashrc file
    Code:
    export LIBVA_DRIVER_NAME=vdpau
    export VDPAU_DRIVER=r600
    Apart from that, you need the very latest Google Chrome Unstable build.

    I use xorg edgers ppa with vdpau activated, the latest google chrome unstable from google ppa, and it doesn't work.

    Leave a comment:


  • chrisb
    replied
    Originally posted by Calinou View Post
    What about Ubuntu One?
    Oh you're right. In that case Canonical supports Windows, OS X, Android and Linux. Aura supports Windows and Chrome OS and Linux. So, by this measure alone , Canonical does support more native platforms ;-)

    Leave a comment:


  • RussianNeuroMancer
    replied
    Originally posted by Alejandro Nova View Post
    if you use Ubuntu, you need at least a recompile.
    In 14.04 there is libvdpau1-drivers-mesa package in repository.

    Leave a comment:


  • Alejandro Nova
    replied
    Originally posted by pandev92 View Post
    doesn't work for me, opensource amd drivers, vdpau activated, but flash only " accelerated video rendering, software video decoding"
    The requirement set is strict. You need:
    - Mesa compiled with VDPAU support. That means: if you use Ubuntu, you need at least a recompile.
    - VDPAU libraries.

    HIGHLY RECOMMENDED:
    - Mesa 10.1. You need GLSL 1.50 for some HW decoding paths.
    - vdpauinfo. Check if your VDPAU setup is working.
    - The following in your ~/.bashrc file
    Code:
    export LIBVA_DRIVER_NAME=vdpau
    export VDPAU_DRIVER=r600
    Apart from that, you need the very latest Google Chrome Unstable build.

    Leave a comment:


  • smitty3268
    replied
    Originally posted by abral View Post
    Well, this isn't true. They've used the webkit browser engine, and in a browser the browser engine is definitely the most difficult part to write (indeed no one writes new browser engines, even Apple didn't do their own thing and used KHTML. Only recently Mozilla has started Servo, but it's still in its early stages). So you can't say they've written it from scrath.
    Although webkit was obviously a big part of their browser to start with, they started out replacing the javascript engine with their own custom engine, and they've essentially rewritten all the rest of the webkit code themselves since then - which is why they split Blink away from upstream Webkit, since they really had nothing left in common with the Apple side of the codebase.

    Regardless, Google is only replacing GTK in the browser part of their browser, not the html engine, which doesn't directly connect with any toolkit. So just looking at the shell/UI alone, that is 100% written by google.

    Leave a comment:


  • renkin
    replied
    http://www.reddit.com/r/linux/commen...chrome/cg0xcwc

    Leave a comment:


  • strcat
    replied
    File a bug asking them to enable it on Linux when the kernel, libva, and other dependencies are up-to-date. If lots of bugs are opened about the deficiencies on Linux, they might reconsider whether crippling it by disabling hardware acceleration is actually reducing the number of bug reports.

    Leave a comment:

Working...
X