Announcement

Collapse
No announcement yet.

Chrome 35 Released With Aura Replacing GTK+

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

  • hrkristian
    replied
    Originally posted by Temar View Post
    Ahhhhhhhhhhhhh, shit. I updated too, damn it.
    You'll have to state which distro you're using when asking that question.

    I'll assume you're using Ubuntu with Chromium, in which case what you need is
    Code:
    apt-cache showpkg [I]chromium-browser[/I]
    Code:
    sudo apt-get install [I]chromium-browser[/I]=VERSIONYOUWANT
    Further, if you want to lock that version, do
    Code:
    sudo echo ?[I]chromium-browser[/I] hold? | sudo dpkg ?set-selections
    You'll need to swap out package name in italics if you're running Google Chrome.

    I guess there's also a way to do it graphically, Google that shit in yo' shiny new browser.




    Anyone else got some serious issues with Aura and Nvidia proprietary drivers?
    Had to downgrade back to 34 because it was an unusable mess. (Arch w/NVIDIA 337.19-1)

    Leave a comment:


  • smitty3268
    replied
    Originally posted by 89c51 View Post
    Does GTK3 means a working FF on wayland or we will need more stuff for it?

    TBH i don't think we'll see FF running on pure WL anytime soon
    No. FF uses GTK mostly just for theming purposes, there are still lots of direct calls to X that will all need to be replaced before Wayland can work. GTK3 is just step 1 of the process.

    I wouldn't expect to see it working anytime soon either.

    Leave a comment:


  • stikonas
    replied
    Yes, Oxygen-GTK theme was nicer than this Aura theme. However, Aura interface loads a bit faster than GTK+. They should have switched to some modern toolkit like Qt5.

    Leave a comment:


  • Aeder
    replied
    This new Chrome on Fedora 20 KDE is more stable and fast, as well as more ugly and inconvenient. The "translate page" pop-up has a button in KDE style, and the other one in this new flat style. I can't select text in certain sites which was entirely possible in previous version and in Firefox.

    This thing needed a few more weeks of testing and quality control.

    Leave a comment:


  • 0xBADCODE
    replied
    Originally posted by daedaluz
    Epiphany
    Midori
    Rekonq
    Konqueror
    Opera
    Maxthon
    Internet Explorer
    360hao
    inbuilt-browsers of Eclipse and Netbeans
    Emacs browser
    lynx
    elinks
    that QML browser I made one morning
    You have choice. I recommend Epiphany, allows you to create web apps easily.
    I have to say that
    1) I use Linux and do not plan to change that in foreseeable future. Hence its pointless to offer me win-only stuff like IE.
    2) I also told it have to be open. In no way I would enter sensitive data into blob doing hell-knows-what. So various proprietary skins to webkit/blink like Opera and Maxthon are no use for me either.
    3) I do not give a f..k to web apps. I just do not care about it. I only care about more or less modern web features like HTML5 video and webGL to be working, but that's all.
    4) I asked for more or less strong competitor, didn't I? So your QML browser is cool, but...
    5) And it have to be usable, after all. Not sure who out of this list would qualify.

    Leave a comment:


  • Akka
    replied
    Originally posted by 89c51 View Post
    Does GTK3 means a working FF on wayland or we will need more stuff for it?

    TBH i don't think we'll see FF running on pure WL anytime soon
    I suppose they need to port their XUL toolkit to wayland to get FF running?

    Leave a comment:


  • Temar
    replied
    Originally posted by mikefreeman View Post
    A little off-topic, I apologize. But, does anyone know how to revert from this version of Chrome to an older one with NPAPI support? The only XBMC addon for viewing Amazon Prime content that is functional now relies on Chrome to play content through the NPAPI Flash (the built-in PPAPI Flash is missing the necessary DRM code). This is an absolutely necessary piece for my Linux/XBMC-based HTPC, and I blindly updated to this version without remembering that they removed the NPAPI support a couple versions ago.
    Ahhhhhhhhhhhhh, shit. I updated too, damn it.

    Leave a comment:


  • LtWorf
    replied
    GTK

    If it doesn't use GTK, why does it link to GTK? And Cairo? They probably just reimplemented the widgets or something like that.

    Leave a comment:


  • 89c51
    replied
    Originally posted by paintbynumbers View Post

    I would actually rather see Firefox ported but progress on bugzilla seems slow. My understanding is that Firefox basically works on GTK3 now with some rough edges.

    To be fair to the developers it hardly looks like a simple effort and they have resolved tens of related bugs already toward this porting effort:

    Does GTK3 means a working FF on wayland or we will need more stuff for it?

    TBH i don't think we'll see FF running on pure WL anytime soon

    Leave a comment:


  • paintbynumbers
    replied
    Originally posted by sp82 View Post
    What about chrome on Wayland?
    That's already being worked on but not part of upstream:
    Wayland implementation for Chromium Ozone classes. Contribute to intel/ozone-wayland development by creating an account on GitHub.


    I have trouble building this myself to test more recent changes (the chrome/ozone source tree is huge and my machine runs out of memory).

    There's a new milestone release past due but it looks like there's no binary up yet.

    You can get binaries for the milestones here:


    My last experience was with the Valentine release on that page:
    * the browser works but was not running in a sandbox
    * you get a few warnings about things that are not working when you launch
    * the browser window does not allow itself to be resized without using the mouse/keyboard shortcuts provided by weston

    Chromium was still missing some functionality but it was fast and basically usable to visit webpages. I have high hopes.

    I would actually rather see Firefox ported but progress on bugzilla seems slow. My understanding is that Firefox basically works on GTK3 now with some rough edges.

    To be fair to the developers it hardly looks like a simple effort and they have resolved tens of related bugs already toward this porting effort:


    If you want to take a shot at compiling the chromium browser for wayland (via wayland-ozone) you can find instructions here:
    Wayland implementation for Chromium Ozone classes. Contribute to intel/ozone-wayland development by creating an account on GitHub.


    Many of these links have previously appear on this website before. My apologies for reposting them but I figure somebody might find it helpful.

    Leave a comment:

Working...
X