Announcement

Collapse
No announcement yet.

Compiz Will Not Be Ported To Wayland

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

  • #46
    Originally posted by JanC View Post
    The problem is, of course, that GNOME upstream (whatever or whomever that might be; some people suggest it's actually just Red Hat ) did not agree with Canonical's vision on how Ubuntu/GNOME should work. So Canonical had 2 choices: following GNOME blindly (and listening to everybody complaining that they didn't contribute enough to GNOME while knowing that GNOME would likely turn down the patches they wanted included...) or implement their own desktop shell.
    Or they could've modified GNOME Shell by writing extensions or they could've chosen another existing DE like Plasma Desktop (for which Canonical wrote applets anyway to implement Ayatana things).

    Comment


    • #47
      Originally posted by Awesomeness View Post
      Or they could've modified GNOME Shell by writing extensions
      I could be wrong but I was under the impression that initially the extension-related stuff was fairly limited. It wasn't until a few releases in that Gnome shell developers decided to allow people to make more significant changes to the function and appearance of the shell.

      Originally posted by Awesomeness View Post
      or they could've chosen another existing DE like Plasma Desktop (for which Canonical wrote applets anyway to implement Ayatana things).
      As ROSA shows it is not very hard for a distro to ship their own alternative plasma interface. But so much of what Ubuntu relies on is Gnome-based it would be hard to just have the desktop environment use KDE. When frameworks 5 rolls around it will be easier, but that is probably still all least a year off.

      Comment


      • #48
        Originally posted by TheBlackCat View Post
        I could be wrong but I was under the impression that initially the extension-related stuff was fairly limited. It wasn't until a few releases in that Gnome shell developers decided to allow people to make more significant changes to the function and appearance of the shell.
        I don't think GNOME Shell extensions were limited on purpose or anything like that. As more people developed extensions, GNOME shell developers accomodates the changes that were required but extensions always could practically do anything needed. The changes that were done was coming up with a more stricter flow so that the API doesn't have to change so often. In that sense, the extension framework has become mature but Canonical could very well have contributed their changes as extensions but my understanding is that they just thought going their own way gives them better control which is absolutely true but the maintenance headaches are quite large and this was something anybody who goes their own way learns after sometime. Unfortunately it appears that every organization including Red Hat, Novell, Google etc have to independently learn the same lesson. So either Canonical has to hire up or share the maintenance and development costs of the core technology pieces. It will be interesting to see which direction they go. So far it looks they prefer to got their own way which is a valid choice certainly.

        Comment

        Working...
        X