Results 1 to 10 of 10

Thread: Blue Systems Seeks To Speed Up KF5 Development

  1. #1
    Join Date
    Jan 2007
    Posts
    15,678

    Default Blue Systems Seeks To Speed Up KF5 Development

    Phoronix: Blue Systems Seeks To Speed Up KF5 Development

    For speeding up the development of KDE Frameworks 5, developers at Blue Systems are near exclusively focusing upon the development of these frameworks for the next three months...

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

  2. #2
    Join Date
    Jun 2013
    Posts
    74

    Default

    wasnt that the plan right before the KDE guys did rush into wayland because MIR was announced?

  3. #3
    Join Date
    May 2010
    Posts
    684

    Default

    Quote Originally Posted by k1l_ View Post
    wasnt that the plan right before the KDE guys did rush into wayland because MIR was announced?
    No one "rushed into wayland" because mir was announced. The main difference is news coverage on anything relating to wayland and mir has increased because the "wayland vs mir" drama generates drama and pagehits.

    And there's also lots of development work going on in other parts of the stack (like egl support in mesa) that makes wayland and mir possible. Gnome and KDE have been able to start ramping up their wayland desktop development because these parts of the stack have started maturing enough, not because of anything to do with mir.

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

    Default

    what always amaze me of this flame wars with mir is that the stupidiest further from the truth crazy pulled of an troll ass arguments reach everyone at lightspeed but actual facts require a bazillion posts to reach ppl, well if you reached this post for some reason before post watch this

    http://www.youtube.com/watch?v=RIctzAQOe44 (is from daniel stone an Xorg developer and works with wayland)

  5. #5
    Join Date
    Oct 2012
    Posts
    109

    Default

    Quote Originally Posted by k1l_ View Post
    wasnt that the plan right before the KDE guys did rush into wayland because MIR was announced?
    No, KDE (at least Martin for KWin), has been working on Wayland support for awhile before Mir was even announced. It was always planned for KDE 5, too.

  6. #6
    Join Date
    Oct 2011
    Posts
    56

    Default

    Quote Originally Posted by jrch2k8 View Post
    but actual facts require a bazillion posts to reach ppl, well if you reached this post for some reason before post watch this

    http://www.youtube.com/watch?v=RIctzAQOe44 (is from daniel stone an Xorg developer and works with wayland)
    Thank you for sharing this!
    May I wonder why opensource developers kept this X compatibility for so long, despite all of X did badly?

  7. #7
    Join Date
    Jul 2013
    Location
    USA
    Posts
    715

    Default

    Quote Originally Posted by ulenrich View Post
    Thank you for sharing this!
    May I wonder why opensource developers kept this X compatibility for so long, despite all of X did badly?
    Politics thats why Wayland was Developed and is not called X12 (or is it going to be?)

    http://www.x.org/wiki/Development/X12/

  8. #8
    Join Date
    Feb 2011
    Posts
    1,310

    Default

    Quote Originally Posted by LinuxGamer View Post
    Politics thats why Wayland was Developed and is not called X12 (or is it going to be?)

    http://www.x.org/wiki/Development/X12/
    It isn't called X12 because it has essentially nothing in common with X.

  9. #9
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,941

    Default

    Quote Originally Posted by LinuxGamer View Post
    Politics thats why Wayland was Developed and is not called X12 (or is it going to be?)

    http://www.x.org/wiki/Development/X12/
    X12 assumes you still have SOMETHING in common with the X API.... Wayland doesn't. Wayland throws the entire book and the bookshelf out the window and says "Okay, Start from scratch. No legacy crap, no assumed backwards compatibility, clean break. Lets get this right this time. No stopgap-measures."

    Also, X12 was never really coming to pass... That X12 page was basically a whiteboard of ideas of "If we had to do it all over again, knowing what we know now, what would we change from X11?"

    A lot of those ideas got merged into Wayland, and if some other company wants to make X12 they sure can...but i won't be the X.org devs.

  10. #10
    Join Date
    Dec 2010
    Posts
    1,264

    Default

    Quote Originally Posted by bakgwailo View Post
    No, KDE (at least Martin for KWin), has been working on Wayland support for awhile before Mir was even announced.
    Indeed. Initial steps were taken as early as 2010: http://blog.martin-graesslin.com/blo...#comment-20435
    Back then KWin was just Martinís hobby which is one reason why progress was slow (the other was still changing Wayland API).

    In October 2012 he was hired by Blue Systems to work on KWin full time beginning January 2013. His main goal was to get the Wayland port done: http://blog.martin-graesslin.com/blo.../kwin-hacking/
    All that happened way before Mir was announced.

    Btw, I got all that info by simply opening the Wayland Wikipedia article: https://en.wikipedia.org/wiki/Waylan...ol%29#Adoption

Tags for this Thread

Posting Permissions

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