Announcement

Collapse
No announcement yet.

KDE SC 4.6.2 Codename Is Dedicated To GNOME 3.0

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

  • devius
    replied
    Originally posted by kraftman View Post
    sometimes you just have to minimize quickly.
    I guess nobody is going to look at porn or play games when they should be working anymore... business owners are going to love the lack of minimization.

    Leave a comment:


  • kraftman
    replied
    Originally posted by Awesomeness View Post
    Yes: Stop minimizing windows.
    When I tried GS it was soon very clear to me that minimizing windows is not something one is expected to do in GS's workflow. Instead new windows should be launched in new workspaces. Workspace management is IMO still lacking refinement but it's just a dot 0 release.
    I just can't adapt to such behavior. Maybe if Gnome 3 will be my first DE in entire life this will be different. Btw. sometimes you just have to minimize quickly.

    Leave a comment:


  • kraftman
    replied
    Originally posted by siban View Post
    It is not completly true, KDE makes big mistakes (and the distros don't check) like for example this last error introduced in 4.6.2. http://bugs.kde.org/show_bug.cgi?id=270228 It was not possible to shutdown the computer for many, many people using Linux, but not (I think) for *BSD users.
    Yes, because of some idiot who thought he will help bsd to gain more attention.

    Leave a comment:


  • bwat47
    replied
    Originally posted by Awesomeness View Post
    Why should unpaid KWin developers fix a driver that's developed by full-time developers working for and paid by a giant corporation?
    You're not making sense.

    Btw, following the economics of a free market: If you can't fix problems yourself, you can always hire someone to do it for you.
    Compiz and XFCE's compositing run perfectly fine on my ati with both fglrx and the oss drivers. Kwin runs horribly. I Don't think it's all ati's fault, especially considering the oss driver is just as bad. I am sure KWin can do something to fix this or at least have some sort of workaround if it is caused by a driver issue.

    Leave a comment:


  • tball
    replied
    Awesomeness

    Originally posted by siban View Post
    But if I launch a windows, then I launch another window, and want to see the first windows, I know it is below the current window, so I click the minimize button With the current sitution in the new Gnome, it will be a problem for many. Let's see what happens.
    As Awesomeness mentioned, you should just avoid minimizing a window. Instead open the first window in the first workspace and the second in the second workspace. When you want to go back to the first windows, press ctrl + alt + up or let your mouse switch workspace for you.

    Leave a comment:


  • siban
    replied
    Originally posted by kraftman View Post
    Normally you don't upgrade KDE and you don't upgrade Gnome if you're using Kubuntu (till you add backports repo) and Ubuntu. If some distribution let's you to upgrade mentioned software its maintainers should take care to give you the smooth upgrade experience. It will be different if KDE would be entire Linux distribution, but it's not.
    It is not completly true, KDE makes big mistakes (and the distros don't check) like for example this last error introduced in 4.6.2. http://bugs.kde.org/show_bug.cgi?id=270228 It was not possible to shutdown the computer for many, many people using Linux, but not (I think) for *BSD users.

    Leave a comment:


  • siban
    replied
    Originally posted by Awesomeness View Post
    Yes: Stop minimizing windows.
    When I tried GS it was soon very clear to me that minimizing windows is not something one is expected to do in GS's workflow. Instead new windows should be launched in new workspaces. Workspace management is IMO still lacking refinement but it's just a dot 0 release.
    But if I launch a windows, then I launch another window, and want to see the first windows, I know it is below the current window, so I click the minimize button With the current sitution in the new Gnome, it will be a problem for many. Let's see what happens.

    Leave a comment:


  • Awesomeness
    replied
    Originally posted by kraftman View Post
    It's somehow hard to discover. I don't know how to minimize the window except right clicking on the title bar and choosing minimize option. I'm sure there must be different way.
    Yes: Stop minimizing windows.
    When I tried GS it was soon very clear to me that minimizing windows is not something one is expected to do in GS's workflow. Instead new windows should be launched in new workspaces. Workspace management is IMO still lacking refinement but it's just a dot 0 release.

    Leave a comment:


  • kraftman
    replied
    Originally posted by tball View Post
    Uhmm do you by any chance use the nvidia proprietary driver? That is known to be slow with GS.
    The open source radeon driver just rocks with GS.
    Sorry for late response. I'm using radeon driver and GS works good on my computer. The problems I mentioned with slowness are not mine, but few other people. They're using nvidia and radeon. I saw there are bug reports at bugzilla about mentioned issues.

    I must also disagree with the lack of usability. I find GS something you have to get used to, but when you do, it is very easy and pleseant to use :-)
    It's somehow hard to discover. I don't know how to minimize the window except right clicking on the title bar and choosing minimize option. I'm sure there must be different way. While Gnome Shell is something new in Gnome3 (for some it's step backward, but opinions are different) I noticed other applications remained the same.

    Leave a comment:


  • Awesomeness
    replied
    Originally posted by smitty3268 View Post
    You're presenting a false choice here. Either the GPU manufacturer OR the KWin developers should care about fixing the issues. That's wrong, they should both care. What one does could help out the other, but it really doesn't matter whether the GPU manufacturer cares or not, the KWin developers still should. Anyway, I'm not necessarily claiming they need to fix the drivers directly - although that is in the spirit of open source - but they could at least do some testing, figure out which effects are broken on currently widespread drivers, and disable them on that hardware. Or even try to rewrite the broken affects to work around driver bugs. It's what everyone else does, after all.
    AMD should fix their radeon driver, KDE should fix bugs in KWin. Neither should work around bugs from the other.
    KWin properly disables effects if they are unsupported but a main problem with the drivers is that they tell applications that feature XY is supported while actually it's not. If a driver announces to support a certain feature, that feature has to be available and properly implemented. It's not the responsibility of hobbyist window manager developers to test against all driver versions out there and maintain a blacklist or anything like that.

    Luckily for the GNOME folks, KWin already paved the way. Thanks to its no workaround policy, the drivers are in much better shape these days, so they should have a less bumpy ride with Mutter and the drivers.

    Leave a comment:

Working...
X