Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: KDE 4.11 Beta Released, Works On Wayland

  1. #1
    Join Date
    Jan 2007
    Posts
    14,805

    Default KDE 4.11 Beta Released, Works On Wayland

    Phoronix: KDE 4.11 Beta Released, Works On Wayland

    The first beta of the forthcoming KDE 4.11 Software Compilation is now available. KDE 4.11 features greater use of Qt Quick in Plasma Workspaces, KWin supports creating OpenGL 3.1 Core contexts, and KWin is beginning to work on Wayland...

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

  2. #2
    Join Date
    Jan 2009
    Posts
    1,678

    Default

    We need a god damn browser (proper one, FF preferably) that works with WL.

  3. #3
    Join Date
    Sep 2008
    Location
    Vilnius, Lithuania
    Posts
    2,552

    Default

    Quote Originally Posted by 89c51 View Post
    We need a god damn browser (proper one, FF preferably) that works with WL.
    I'd bet that Rekonq will beat FF at that, given that it's full Qt and all.

  4. #4
    Join Date
    Jun 2009
    Posts
    1,136

    Default

    well tested with r600g + opengl 3.1 +wayland 1.1 and weston 1.1[gentoo] and well is really experimental and glitchy to really work with but man it render freaking freaking fast, i mean kde4 is not wayland native hence why you need Xvfb but even so is way faster than Native X11.

    for example rekonq with the wayland experiment beat chrome 28 on native X11 hands down in render speed and scrolling, im really impressed

    note: refresh gets really glichy and multimonitor dont work but as an experiment is a hell of a nerd candy

    im emerging Qt5.1 with wayland QPA and test snowshoe the first native qtquick2 browser, i can't wait to see how native wayland apps will work.

    don't ask me about ubuntu, wait for a PPA to emerge or switch to a big boys distro if you can't wait[gentoo or arch sounds about right]

  5. #5
    Join Date
    Sep 2011
    Posts
    63

    Default

    Quote Originally Posted by 89c51 View Post
    We need a god damn browser (proper one, FF preferably) that works with WL.
    ff still uses gtk2, it'd have to use gtk3 (or qt)

  6. #6
    Join Date
    Jan 2009
    Posts
    1,678

    Default

    Quote Originally Posted by balouba View Post
    ff still uses gtk2, it'd have to use gtk3 (or qt)
    They are moving it to gtk3 but it seems to be taking quite a lot of time. Have no idea why.

    Also with things like jolla and Ubuntu using Qt it would be nice to have a version built with it but i doubt it worths the investment.
    Last edited by 89c51; 06-15-2013 at 10:21 AM.

  7. #7
    Join Date
    Feb 2008
    Location
    Santiago, Chile
    Posts
    242

    Default

    Quote Originally Posted by 89c51 View Post
    They are moving it to gtk3 but it seems to be taking quite a lot of time. Have no idea why.

    Also with things like jolla and Ubuntu using Qt it would be nice to have a version built with it but i doubt it worths the investment.
    I'm quite surprised. AFAIK Firefox already had a proof-of-concept binary compiled against Qt 4, and switching between Qt 4 and Qt 5 code at source level is a breeze, unlike the switch between Gtk 2 and Gtk 3. So, if they are really porting Firefox to GTK3 they are doing at least 3x more work, and scrapping work already done to be compatible with Wayland. In other words, a total waste.

  8. #8
    Join Date
    Dec 2010
    Posts
    1,150

    Default

    Quote Originally Posted by balouba View Post
    ff still uses gtk2, it'd have to use gtk3 (or qt)
    There will never ever be a fully working FF version built on Qt. It was attempted so often already and has always been abandoned after a few months.

  9. #9
    Join Date
    Oct 2008
    Posts
    3,133

    Default

    Quote Originally Posted by Alejandro Nova View Post
    I'm quite surprised. AFAIK Firefox already had a proof-of-concept binary compiled against Qt 4, and switching between Qt 4 and Qt 5 code at source level is a breeze, unlike the switch between Gtk 2 and Gtk 3. So, if they are really porting Firefox to GTK3 they are doing at least 3x more work, and scrapping work already done to be compatible with Wayland. In other words, a total waste.
    The Firefox Qt 4 code was never fully working, always experimental, and completely abandoned a long time ago. It's primarily a Gtk2 app, with a healthy helping of direct X commands that will also need to be replaced with any Wayland port.

  10. #10
    Join Date
    Jan 2009
    Posts
    1,678

    Default

    Quote Originally Posted by smitty3268 View Post
    The Firefox Qt 4 code was never fully working, always experimental, and completely abandoned a long time ago. It's primarily a Gtk2 app, with a healthy helping of direct X commands that will also need to be replaced with any Wayland port.
    TBH i always thought that FF was "easy" to port to different toolkits. Not the case obviously. Or maybe noone cares. Would love an efl port.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •