Announcement

Collapse
No announcement yet.

Unity 2D To Go Away In Ubuntu 12.10

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

  • #31
    Originally posted by jakubo View Post
    How about multimonitor setups?
    I have encountered a 2048x2048 pixel limit on my i945 powered laptop for 3d acceleration, which forced me to use unity 2d when having a second monitor attached. So this probably needs to get "fixed" - or worked around. And as someone mentioned before: the top panel does not always behave nicely when using wine in fullscreen mode... (same thing for special keys and shortcuts in games)
    It's a hardware limitation that's very hard to work around in software, and made even harder by X's design. Even if you did work around it you'd end up having to do all your rendering twice if you had a window that extended across outputs, so performance would be even worse than usual with 945 -- which is very bad as IIRC it doesn't have any hardware vertex shaders.

    I have absolutely no idea where the suggestion that Canonical deliberately crippled it came from.

    Comment


    • #32
      Originally posted by psycho_driver View Post
      This makes me sad. I'm actually quite liking 12.04 on my wife's desktop after some minor tweaks. One of which was switching to unity-2d. 3D has some pretty annoying bugs with some opengl applications (wine in some instances, for one).
      I second that, running it on fairly old laptop, and it's a very clean DE, gets the job done. The onboard Radeon X1100 is sluggish with the 3D version (tried most of the Compiz Config tweaks I could find, disabling vsync, upping the refresh rate, disabling Dash blur...)
      Good thing it's a five years support... Worst case scenario I'm back to Xubuntu.

      Comment


      • #33
        Originally posted by russofris View Post
        This is not a problem with the tech itself, it is a problem with the Unity/Gnome/KDE implementation of the tech. OSX is a good example of a good (yet subdued) implementation of 3D compositing.


        I disagree that they are worthless. A quality reference software stack is a good thing, even if only used as a baseline in which hardware stacks are compared. To say that a product is not performant, while still in it's infancy, is probably short sighted. CPUs will get faster, the software will get faster, and may become useful given time to grow.


        I completely agree. With the exception of some of the corner cases that you outlined, this is dead-on. I think of LLVMPIPE as a potential VESA alternative, and not a replacement for 3D drivers. It may have additional uses once linux has a multi-GPU framework in place, and performance is improved.

        F
        We're sort-of agreeing here. The problem is that they're using the software specifically for that reason that you say is not appropriate. In context, what I said is that these are useless **for this purpose**. I agree that a software reference driver is definitely a valuable thing.

        And yeah, mac10 does compositing, but doesn't accomplish anything useful with it. Its still just eye candy over a very frustrating UI. I wish people would focus on making the UI **GOOD** instead of just "pretty". Sometimes GOOD is also UGLY.

        Comment


        • #34
          Originally posted by asdx
          We need to add support for Wayland to everything NOW and FORCE nvidia to support Wayland, otherwise they will just be lazy about it and won't give a shit about Wayland or anything you come up with.

          Deprecate X NOW and force nvidia to support Wayland or get them out of business. Plain and simple.

          And for the people or developers being afraid to do this: Grow the fuck up already and quit being a fucking sissy.
          Dude! What did I tell you about your demands and being a spoiled kid? You've just now proven to be exactly that, a spoiled kid, and nothing more.

          Deprecating X has nothing to do with anyone needing to grow the fuck up. If you think it's so easy, then go do just that, you "grow the fuck up" and deprecate X from your machine, see how far you'll get.

          Comment


          • #35
            Originally posted by asdx
            I'd rather be spoiled than a conformist.
            Umm, there aren't just those two options, you know. And about spoiled, as a kid you can scream "I want it, I want it!" and your mommy will get it for you. But the real world doesn't work like that.

            Originally posted by asdx
            And I've used the wrong word, I should have said "man the fuck up" because that's what developers should do but they don't because they are too afraid of doing anything that will piss off nvidia.
            Well, have you "manned the fuck up" yet and deprecated X from your machine? No? Why not?

            In your little world, this might be about "too afraid to piss off nvidia". But in the real world, people want to, you know, *use* their machines. X makes that possible. Wayland does not. The developers are making it happen. Which makes them already way more "manned up" that you are. They're actually writing code, instead of being obnoxious on forums.

            But if you think they're so incompetent, why don't you show them how it's done, write some code to make Wayland happen faster. I'm sure they'll be happy to get new contributors. Go ahead, let us see *your* competence. Prove that you can do more that just dish out colorful words, show us how much of a man you are.
            Last edited by Gusar; 05-09-2012, 03:29 PM.

            Comment


            • #36
              I love it when the guy with the unused Soloflex argues with the guy with the unused gym membership about which has the better workout routine.

              Re: Switching to Wayland forces Nvidia to react.

              I have no reason to believe that hardware vendors will react any differently to Wayland than they have previously reacted to X11. Their quickest path to market is probably to create a shim between Wayland and their in-house blob. The only difference this time around is that OSS drivers are first to market. While this settles the philosophical chicken/egg question, we still end up with chickens and eggs. To summarize, I expect we'll be in exactly the same position with Wayland in 2 years as we are with X11 today.

              Comment


              • #37
                X is awesome.

                Comment


                • #38
                  Originally posted by russofris View Post
                  I love it when the guy with the unused Soloflex argues with the guy with the unused gym membership about which has the better workout routine.

                  Re: Switching to Wayland forces Nvidia to react.

                  I have no reason to believe that hardware vendors will react any differently to Wayland than they have previously reacted to X11. Their quickest path to market is probably to create a shim between Wayland and their in-house blob. The only difference this time around is that OSS drivers are first to market. While this settles the philosophical chicken/egg question, we still end up with chickens and eggs. To summarize, I expect we'll be in exactly the same position with Wayland in 2 years as we are with X11 today.

                  I think you are mostly right. What I hope is that Wayland will make work easier for all the developers. Certainly a big win is that it brings a large part of the linux graphic stack up to modern standards (and should make Peter Hutterer happier), and make things easier to work with in the future. So, it is possible that proprietary drivers get ever so slightly more streamlined.

                  Comment


                  • #39
                    Originally posted by asdx
                    Can't nvidia just help improve nouveau and mesa? I mean, my understanding is that nvidia is too tied to the X11 architecture and doesn't really use DRM. So wouldn't it be easier for them to just work on nouveau instead of having to port the whole blob to another windowing system? Is that even possible with Wayland?

                    nouveau already seems to be set with the foundation and using the whole kernel/Linux stack, it seems like it just needs more improvements with performance and also mesa needs to catch up with the latest OpenGL specs to be viable for gaming, etc.
                    Nvidia officially supporting Nouveau would be tantamount to them officially endorsing a reverse engineering effort of their products (namely, their binary drivers and their hardware).

                    I'm not sure they are particularly motivated to try and take legal action against the Nouveau folks as-is (in fact I rather doubt they would), but neither are they going to come out and say, "Yep, go ahead, RE our drivers; that's a good way to develop open drivers for our hardware! Release some open documentation while you're at it!"

                    That kind of attitude is just NOT the way Nvidia works as a company. They don't "get" open source at all, save for maybe half a dozen people in the entire company. And those people aren't the senior execs calling the shots; they're people "like bridgman but at Nvidia" (middle managers or worker bees). They can't turn the gears of the company; they are the gears.

                    It's too bad, because both of Nvidia's major x86 graphics competitors (Intel and AMD) are a LOT more open about publicly supporting official open source graphics drivers. But Nvidia would never do that, whether the implementation of the drivers were "clean room" or "reverse engineered" or even "officially supported by Nvidia". They just don't like open source at all, because there's a risk of their precious "IP" leaking to AMD and giving AMD an edge. Ohnoes!

                    (Aside: The final jab in the stomach for Nvidia is that, despite remaining as selfishly proprietary as possible, the community's RE efforts have done a great job of providing AMD easily-obtaining information about how their competitor's hardware works, and they could probably use this to help them improve their own products if they wanted to. Might be a contributing factor to why AMD's harwdare is so outstanding and extremely competitive / better than Nvidia's since about the HD4000 generation!)

                    Comment


                    • #40
                      Pray he doesn't modify the deal anymore

                      This reminds me of the scene from Empire Strikes Back where Lando is talking to Darth in reference to changes to the supposed deal they made. I used to think only Fedora was a joke-in-progress as now it seems Ubuntu has become.
                      So I don't believe users can keep up with Canonical's ambitious ideas.

                      It's generally the amateurs that come to the table with the bright idea of throwing out everything and starting over only because they are too lazy to comprehend the code-base. You've seen these individuals at your workplace. So eager are they to suggest a new tool to redirect your attention from their lack of progress.

                      I forecast RedHat staying with Gnome 2 for sometime. That means CENTOS and Scientific can still reliably provide for my own needs. Look how it is becoming.

                      "Canonical is just a false prophet offering the Olive Branch dipped in poison.", me

                      If this company seriously cared about humanity we'd still be using gnome 2.28 with simple bug-fixes and back-ports.
                      Too bad I don't have a fortune to support my vision of a great product.

                      Respectfully,.

                      Comment


                      • #41
                        Originally posted by squirrl View Post
                        This reminds me of the scene from Empire Strikes Back where Lando is talking to Darth in reference to changes to the supposed deal they made. I used to think only Fedora was a joke-in-progress as now it seems Ubuntu has become.
                        So I don't believe users can keep up with Canonical's ambitious ideas.

                        It's generally the amateurs that come to the table with the bright idea of throwing out everything and starting over only because they are too lazy to comprehend the code-base. You've seen these individuals at your workplace. So eager are they to suggest a new tool to redirect your attention from their lack of progress.

                        I forecast RedHat staying with Gnome 2 for sometime. That means CENTOS and Scientific can still reliably provide for my own needs. Look how it is becoming.

                        "Canonical is just a false prophet offering the Olive Branch dipped in poison.", me

                        If this company seriously cared about humanity we'd still be using gnome 2.28 with simple bug-fixes and back-ports.
                        Too bad I don't have a fortune to support my vision of a great product.

                        Respectfully,.
                        It's not "starting over", it's "evolution" -- they are different. Starting over means wiping the table clean and re-designing everything from scratch. Evolution means taking what you have and reusing as much of it as possible while creating something new on top. Gnome (and to a lesser degree, Unity) have performed "evolution", not "starting over". Same with Cinnamon (which you may like as a user of Gnome2, BTW).

                        First of all, GTK3 and its underlying GLib library are pure evolutionary compared to their predecessors. Some 98% of GTK2 code can simply be recompiled almost as-is for GTK3. All the old GLib middleware functions are there, and in fact, GLib never even had a "3.0" release -- its version number is still in the 2.x range, so they haven't even broken ABI.

                        Gnome 3's features are in direct response to repeated user requests for a desktop that can takes advantage of today's 3d graphics cards (the more long-standing request), and also which can work well with a touch interface (the much more recent request, which can be seen by e.g. users of Ultrabooks, which are x86 thin laptops with a keyboard and a multitouch screen).

                        I'm sure that if you were using an Ultrabook, you would agree that Gnome 3 is more usable than Gnome 2. So what actually happened is that Gnome changed its target market away from traditional desktop users, towards mobile computing and touch interfaces and people who like eye candy.

                        This is, naturally, going to alienate people who prefer to interact with their desktop primarily using a keyboard and mouse, and who don't give a crap about eye candy. But the perceived demand for eye candy and touch interfaces is so overwhelming that, essentially, Gnome doesn't care that people like you and I are still wanting the old interface.

                        Well I'm sure some of the contributors to Gnome care. But overall, sacrifices in the design have been made, in order to please touch users / small screen users / mobile users, to the almost universal displeasure of workstation users. That's just the way it is. It's no big conspiracy; it's just that the projects naturally want to support the user base that is going to have the most users... and they think that is or soon will be people on mobile devices / tablets / ultrabooks with touch interfaces.

                        BTW, Red Hat is one of the main contributors to Gnome. You can bet your arse that RHEL 7, which will be based on something like Fedora 16 or Fedora 17, is going to ship Gnome 3 (because that version of Fedora does). Tough luck. You'll just have to keep using RHEL 6 forever I guess, long after its 7 years of security updates have expired...

                        Comment


                        • #42
                          I'm evaluating 12.04 in a VM to see if I want to upgrade and so far I'm not sold on Unity. I think I might be able to make it workable in a multi-tasking environment if I can get used to it. I don't know.

                          But what amazes me is just how non-configurable the thing is out of the box. I guess I'll have to download all kinds of tools and crap just to get some kind of sane setup going. Kinda lame.

                          I can't speak for Gnome shell -- since the few times I've tried it I've found it to be 100% unusable for anything more than just staring at the wallpaper -- but Unity looks almost embarrassingly identical to OS X. Between the global menu, big-honkin' dock and the way System Settings is laid out. It's one thing to be inspired by another... but making a carbon-copy just makes one look bad. Not that OS X doesn't look nice and polished... but I still find it kind of hard to use for anything more than basic work.

                          Dash is kinda cool though... at least the search mechanism. Some of the other stuff like automated backup, ubuntu one and the software center have improved nicely over 10.10 and 11.04.

                          Gnome2 is getting long in the tooth and I do want something modern, fresh and slick... even if it's different. So I might end up biting the bullet.

                          Comment


                          • #43
                            Can someone explain what this will mean for the future of Unity-2D in 12.04? If 12.04 is an LTS release, would they drop features during the support period that were present in the initial release?

                            Comment


                            • #44
                              Originally posted by asdx
                              Can't nvidia just help improve nouveau and mesa? I mean, my understanding is that the nvidia blob is very tied to the X11 architecture and it does bypass a lot of things that the kernel provides (DRM, etc).

                              So wouldn't it be easier for them to just work on nouveau instead of having to port the whole blob to another windowing system? Is that even possible with Wayland?
                              I would say it's actually the opposite of what you write here. That because nvidia bypasses parts of the usual infrastructure, they are *not* tied to a specific architecture. They have their own thing, and they can adapt it to whatever. The whole driver is an adaptation from Windows to Linux, for example. But for now, there's just no incentive to adapt to anything other than X. Why should they, the Wayland protocol isn't even finished yet, and what's already there is subject to change until 1.0 is released, and even then there will probably still be changes.

                              Originally posted by asdx
                              Why can't we just forget about nvidia and focus on building Wayland and make it the best it can be?
                              Wait, wait, are you saying here that Wayland devs are pandering to Nvidia, and that if they didn't, they'd be a lot further along? Huh?? You are aware that Weston, the reference compositor, only works on KMS/DRI2, right? At least I think that's still the case.
                              So what makes you think they *aren't* doing what you say here, what makes you think they aren't making Wayland the best it can be? The Wayland protocol itself doesn't care how the mode is set, just that it is set, so implementations can very well work on something other than KMS. But that's not pandering to Nvidia, that's just plain good sense. If you think Nvidia is holding back development of Wayland, that's just dumb.

                              Basically, wake up and realize that there is a real world out there, outside of your idealistic and naive views, and that this real world has real needs that have to be met, no matter how much you're saying "just get rid of X already". Like I said, why haven't you done so yet on your machine?

                              Comment


                              • #45
                                VNC

                                I hope they fix the problem with Unity 3d windows not redrawing over VNC first.

                                Comment

                                Working...
                                X