Announcement

Collapse
No announcement yet.

First There Was Compiz, Now There Is Compiz++

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

  • First There Was Compiz, Now There Is Compiz++

    Phoronix: First There Was Compiz, Now There Is Compiz++

    First there was Compiz, a compositing window manager that brought very interesting desktop effects to Linux, and then Beryl came about as a fork of Compiz before it ultimately turned into Compiz Fusion. Today though, on Christmas eve, the world can now meet Compiz++. Compiz++ is a branch of Compiz that brings several new features to the table and there are huge changes...

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

  • #2
    I have a feeling that KWin's work has been instrumental in all of this. The fact that they are switching to cmake makes this pretty obvious.

    I wonder if compiz will be replacing KWin in the future? Perhaps it can replace Metacity too. That would be a really great thing for the linux community. Or at least this modularization should make it much easier to share code between the projects.

    Granted, it would be trickier to share with Metacity since it doesn't use C++.

    Considering how many distos dump metacity for compiz, it would make perfect sense for GNOME to dump it too, and for all of us to rally around one window manager.

    Comment


    • #3
      Just like with KDE 4, if it's not stable enough it won't conquer users. I hope a new architecture will fix all glitches and bugs that plague Compiz Fusion today.

      Comment


      • #4
        No Composite required, possible X Render backend, C++, CMake... is it Compiz or KWin?

        Comment


        • #5
          I think KDE users will stick to the amazingly fast developing KWin4 which works quite well already. Compiz(++) will become the standard for Gnome though, I guess.

          Comment


          • #6
            Originally posted by d2kx View Post
            I think KDE users will stick to the amazingly fast developing KWin4 which works quite well already. Compiz(++) will become the standard for Gnome though, I guess.
            Not to mention KDE4 is pain free to get setup and use. Even works great in KDE3 when using kwin4 for your Window Manager.

            Comment


            • #7
              "Compiz++ also introduces support for tiled textures, which allows larger pixmaps to be supported whereby its broken into smaller textures to avoid such limitations."
              Does this mean I can use compiz++ on my 9500 with two 1440x900 screens and not get everything past 2048th pixel go black when I start it?

              If true, I can't wait for this to hit the sunrise or x11 overlays in gentoo. This is what has been holding back my use of compositing. I used compiz when I had only one monitor, and then quit using it when I got two.

              Comment


              • #8
                I wonder how C people will react to this.

                Comment


                • #9
                  Originally posted by Vadi View Post
                  I wonder how C people will react to this.
                  It's sad to see so many people doing development for the sake of C than the other way around.

                  Comment


                  • #10
                    Originally posted by RealNC View Post
                    It's sad to see so many people doing development for the sake of C than the other way around.
                    yeah,so true. To me, opengl always seems to make more sense in c++ than in c. Likewise for gui toolkits, and no gobject does not count as an oo language

                    Comment


                    • #11
                      The vala and gobject stuff is rather neat actually. It's more about a cross-language thing than centered on C.

                      Comment


                      • #12
                        IMO, a developer shouldn't become a "fanboi" of a language. The language shouldn't matter at all; pick the most appropriate one for a given project.

                        Unfortunately, many people seem to believe that "the best choice" is always C and have become quite obsessed with it. That shouldn't happen. Perhaps it's because C is all they know and try to hide that fact.

                        Comment


                        • #13
                          Well, if C is all they know, then obviously it's the best choice.

                          Comment


                          • #14
                            Yes, but they don't come forth and say it. They just go into arguments of why C is better than C++ instead of saying "I never learned C++".

                            Comment


                            • #15
                              Originally posted by RealNC View Post
                              IMO, a developer shouldn't become a "fanboi" of a language. The language shouldn't matter at all; pick the most appropriate one for a given project.

                              Unfortunately, many people seem to believe that "the best choice" is always C and have become quite obsessed with it. That shouldn't happen. Perhaps it's because C is all they know and try to hide that fact.
                              Given the scope of the standard libraries, learning debugging and other workflow I find that most developers couldn't and shouldn't try to be good at more than a few. I've meddled in many languages from assembler to Java, but the only one I know really well is Qt/C++, not even C++ in general and I'm still constantly learning from that.

                              If you're designing up a large project where you'll be staffing up people with the right skills, then the project should decide the language. If it's already a given that you'll be the one doing the work, then the wrong language is often the right choice.

                              I'm sure I've done things that are easier done in other languages, but what I do works well and with a lot less effort than trying to figure out a new language. Of course, if I constantly found myself doing something my language of choice isn't suited for, things would be different.

                              Comment

                              Working...
                              X