Announcement

Collapse
No announcement yet.

KDE Developers Discuss Merging Libraries With Qt

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

  • KDE Developers Discuss Merging Libraries With Qt

    Phoronix: KDE Developers Discuss Merging Libraries With Qt

    Well, here's some interesting weekend news: there's a polarized discussion taking place right now among core KDE developers about merging the KDE libraries into upstream Qt. Cornelius Schumacher, a long-time German KDE developer and currently the KDE e.V. president, has come out yesterday saying, "Let's merge Qt and the KDE development platform. Let's put all KDE libraries, support libraries, platform modules into Qt, remove the redundancies in Qt, and polish it into one nice consistent set of APIs, providing both, the wonderful KDE integration, consistency and convenience, as well as the simplicity and portability of the Qt platform."..

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

  • #2
    Would merging them not create a big mess, where you will be tangled up in libraries?

    Comment


    • #3
      Sounds nice at first, but definitely will result in major major breakage as these libs get reorganized/merged in with the QT libraries. This should be done as an experimental build first to work out the kinks then be implemented in a future KDE release.

      Wouldn't merging KDE libs into QT cause potential licensing issues?

      Comment


      • #4
        It's nice and all that they are so passionately debating it, but isn't it completely pointless until they at least know that upstream would consider it. I mean merging back always requires two parties acceptance, so if Nokia says no, it's a no-go. So I don't understand why the make all this fuss about it, if they don't even know what the other "side" thinks.

        Comment


        • #5
          Originally posted by bash View Post
          It's nice and all that they are so passionately debating it, but isn't it completely pointless until they at least know that upstream would consider it. I mean merging back always requires two parties acceptance, so if Nokia says no, it's a no-go. So I don't understand why the make all this fuss about it, if they don't even know what the other "side" thinks.
          Absolutely! As QT is owned by Nokia, Nokia will definitely need to be involved in such discussions at all levels. If they support this, then it'll then be much much easier

          Comment


          • #6
            IMO Qt is too big already. Tagging in another 100mb of KDE libs is not going to improve things.

            Comment


            • #7
              It is funny. When in another old thread i said that KDE is just a tech demo from Qt developers designed to showcase Qt's abilities, many people said that i do not know what i am talking about... That this is FUD. Well... explain this smart guys... For this discussion to even happen, it proves my point...

              Sure, KDE is a community project. Sure, some people from all over the world contribute to it. But it's core team that drives it, is from Trolltech. Trolltech points, they follow. It is that simple.

              Imagine if the GNOME guys talked about merging gtk3 libs with GNOME libs...

              PS: I use KDE now myself. The bugs that plagued me in the past are fixed, and it is reasonably stable now. I got bored with GNOME 2.32 showing no progress and made the switch. I also joined the Greek localization team of KDE to provide some translations. Just noting it just in case someone calls me troll or fanboy again...

              Comment


              • #8
                @Michael thank you for not choosing a misleading title

                I think the general idea is a good one but not really possible to get to in "one" go.. I think the kdelibs (and kdepimlibs) first need to be seperated in smaller managable Qt modules. Once that's done the steps aren't far to merge to Qt, but even then there will just always be KDE parts that just won't suit Qt thus they will have to remain in separate Qt modules.

                Also recently Qt posted a blog message indicating they what to be more modular : http://labs.qt.nokia.com/2010/10/26/...going-modular/ so for that i think it would be wise to go with modules for now and not merging.

                My guess is that in the end some Qt KDE modules are created with the parts that simply don't fit or belong to Qt and the rest might get merged.

                Don't forget that this idea requires 2 parties to agree! KDE and Qt!

                Comment


                • #9
                  Originally posted by TemplarGR View Post
                  It is funny. When in another old thread i said that KDE is just a tech demo from Qt developers designed to showcase Qt's abilities, many people said that i do not know what i am talking about... That this is FUD. Well... explain this smart guys... For this discussion to even happen, it proves my point...

                  Sure, KDE is a community project. Sure, some people from all over the world contribute to it. But it's core team that drives it, is from Trolltech. Trolltech points, they follow. It is that simple.

                  Imagine if the GNOME guys talked about merging gtk3 libs with GNOME libs...
                  You are so wrong now.
                  Here is how it really works.
                  SOME KDE developers are SPONSORED by Qt and some other KDE developers work for Qt. Or you can turn it the other way around. Some Qt developers also work on KDE. But it's certainly not the case that Qt points and KDE leads.. hell no! Remember phonon? It was developed by KDE devs and adapted by Qt because it was simply good.

                  Originally posted by TemplarGR View Post
                  PS: I use KDE now myself. The bugs that plagued me in the past are fixed, and it is reasonably stable now. I got bored with GNOME 2.32 showing no progress and made the switch. I also joined the Greek localization team of KDE to provide some translations. Just noting it just in case someone calls me troll or fanboy again...
                  Bugs.. hehe digg some deeper there are a lot more then you know ^_^

                  Comment


                  • #10
                    Considering that KDE is completely dependent on QT this proposal only makes sense.

                    Comment


                    • #11
                      Originally posted by markg85 View Post
                      ! Remember phonon? It was developed by KDE devs and adapted by Qt because it was simply good.
                      Phonon is deprecated in QT.

                      Comment


                      • #12
                        Originally posted by deanjo View Post
                        Phonon is deprecated in QT.
                        Is it deprecated? i didn't know that..

                        Anyway, they have indeed added a way cooler multimedia framework so it would make sense. Phonon is still good though.

                        Comment


                        • #13
                          Originally posted by markg85 View Post
                          Is it deprecated? i didn't know that..

                          Anyway, they have indeed added a way cooler multimedia framework so it would make sense. Phonon is still good though.
                          Yup phonon is replaced with Qt Multimedia and Qt Mobility.

                          Comment


                          • #14
                            It would be nice but only after Qt's licencing issues etc. are fixed. Qt has bright future in mobile world, but developement in desktop side is lacking (at least so have I heard). This would probably fix that and make it even more instresting and complete toolkit. In a long run this is probably the best for both sides.

                            However it really should happen in transission of KDE and Qt 5. Breaking backward compatibility twice in year or two doesn't sound good. Tt also should be done in next couple of years, planning something which might happen in next five years sounds stupid in a world where technology developes as fast as it does - or at least I think so.

                            Comment


                            • #15
                              Originally posted by Teho View Post
                              Tt also should be done in next couple of years, planning something which might happen in next five years sounds stupid in a world where technology developes as fast as it does - or at least I think so.
                              It's not stupid at all to plan that far ahead. Most larger projects give similar time lines when a radical change is desired. If they don't plan that far ahead you get a huge mess in development with some areas being relatively mature and stable while other areas are a complete mess.

                              Comment

                              Working...
                              X