Announcement

Collapse
No announcement yet.

KDE Frameworks 5.7 Brings Many Fixes, Supports NetworkManager 1.0, Etc

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

  • KDE Frameworks 5.7 Brings Many Fixes, Supports NetworkManager 1.0, Etc

    Phoronix: KDE Frameworks 5.7 Brings Many Fixes, Supports NetworkManager 1.0, Etc

    The KDE community has done a Valentine's weekend release of KDE Frameworks 5.7.0, the newest version of the add-on libraries used by KDE applications, KDE Plasma 5, and a growing number of other projects like LXQt...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Updated on Opensuse.

    Network manager is still pretty slow for wifi.
    Right dock autohide still borked when using 1/2 height or so wide pager.
    Still no setting for autohide close delay.

    Oh well mabye next release.

    Comment


    • #3
      Originally posted by grndzro View Post
      Updated on Opensuse.

      Network manager is still pretty slow for wifi.
      .
      By slow, you mean slow to detect and authenticate with SSIDs?

      Comment


      • #4
        Originally posted by Sonadow View Post
        By slow, you mean slow to detect and authenticate with SSIDs?
        Yea. takes like 10 seconds from Kwallet log in. Might be my adapter though. I'll have to test that out with my old one.

        Yep it was the Belkin wifi adapter.
        Last edited by grndzro; 15 February 2015, 03:02 PM.

        Comment


        • #5
          Are most apps ported to KF5/Qt5 yet?

          Comment


          • #6
            Originally posted by ihatemichael View Post
            Are most apps ported to KF5/Qt5 yet?
            To answer your question, i have requested a porting status page from list [1]
            and as a result this [2] came out . It needs to be a little polished but still
            good enough to follow

            [1] : http://lists.kde.org/?l=kde-devel&m=142403181405105&w=2

            [2] : http://imagezero.maxiom.de/files/portingstatus.html


            By the way thanks for your question , sometimes little questions makes huge differences.

            Comment


            • #7
              Originally posted by ihatemichael View Post
              Are most apps ported to KF5/Qt5 yet?
              this is just a KDE Frameworks release, KDE Applications 15.04 is what you're looking for.

              Comment


              • #8
                I'm still overly confused over the new KDE plasma/frameworks/applications/mumbojumbo/5/4/3/2/1/BOOM naming convention, so I guess when everyone is running around screaming "ohh KDE 5 is ready" I'll give it another try. Until then I can spare myself the horror of having to deal with that qt/gtk mess.

                Comment


                • #9
                  Originally posted by halo9en View Post
                  I'm still overly confused over the new KDE plasma/frameworks/applications/mumbojumbo/5/4/3/2/1/BOOM naming convention, so I guess when everyone is running around screaming "ohh KDE 5 is ready" I'll give it another try. Until then I can spare myself the horror of having to deal with that qt/gtk mess.
                  Actually it is very simple:

                  Kde Frameworks : It is not an application or any visible part. It is a layer above Qt. So other window managers or other projects can use these
                  libraries as in their applications without including whole KDE. For example if Gnome needs a file indexer it doesn't need to take whole kde they can
                  just take KDE Frameworks and its baloo. ( KDE Frameworks depends on Qt not other part of Kde )

                  Kde Plasma : All funcy visual part. To make a summary it is the window manager part. The Gui part as you can guess. It needs Qt + Kde Frameworks

                  Kde Applications : KDE's build in applications. Dolphin , Kate , Kde-baseapps , Konsole , ... These are based on Qt + Kde Frameworks.

                  So there won't be a kde 5 , kde 5.1 or kde 6 anymore. We will talk about Kde framework's new version or kde applications's new version. For example
                  Every month there will be a new version for Kde Frameworks but not kde application. Every 3 months there will be new kde applications version.

                  So new kde applications' version will depend new version of kde frameworks. This system also fixes the waiting for lots of time for complete new package of everything.
                  If something is not working in base it will be fixed that also fixes current version of installed applications.

                  I'm not sure if i can explained well or not but i hope i helped a bit.

                  Comment


                  • #10
                    Originally posted by usta View Post
                    Actually it is very simple:

                    Kde Frameworks : It is not an application or any visible part. It is a layer above Qt. So other window managers or other projects can use these
                    libraries as in their applications without including whole KDE. For example if Gnome needs a file indexer it doesn't need to take whole kde they can
                    just take KDE Frameworks and its baloo. ( KDE Frameworks depends on Qt not other part of Kde )

                    Kde Plasma : All funcy visual part. To make a summary it is the window manager part. The Gui part as you can guess. It needs Qt + Kde Frameworks

                    Kde Applications : KDE's build in applications. Dolphin , Kate , Kde-baseapps , Konsole , ... These are based on Qt + Kde Frameworks.

                    So there won't be a kde 5 , kde 5.1 or kde 6 anymore. We will talk about Kde framework's new version or kde applications's new version. For example
                    Every month there will be a new version for Kde Frameworks but not kde application. Every 3 months there will be new kde applications version.

                    So new kde applications' version will depend new version of kde frameworks. This system also fixes the waiting for lots of time for complete new package of everything.
                    If something is not working in base it will be fixed that also fixes current version of installed applications.

                    I'm not sure if i can explained well or not but i hope i helped a bit.
                    You made a very simple thing pretty long, there...

                    It's easy:

                    The only thing a user should care about is Plasma. Plasma = the desktop experience. Currently "KDE" is at version 5.2, as far as users are concerned.

                    Frameworks version numbers are like Qt. If you care about whether you are running Qt 5.3 or 5.4 in the background, you should also be able to figure out the frameworks version, for similar reasons. For anyone confused, just forget about it. You don't need to know.

                    And having the apps use their own version # just makes them more similar to regular applications, which don't depend on anything else for their version number. New release = new version number.

                    Comment

                    Working...
                    X