Announcement

Collapse
No announcement yet.

Features Baking For KDE 4.11

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

  • phoronix
    started a topic Features Baking For KDE 4.11

    Features Baking For KDE 4.11

    Phoronix: Features Baking For KDE 4.11

    The KDE 4.11 Beta is due out anytime now and so with that here's a look at some of the features you can expect from this major KDE4 update...

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

  • bwat47
    replied
    Figured out a somewhat hacky workaround to my issue with streaming videos on my lan with kde

    enabled IIS on the windows box and enabled directory browsing. Now I can just browser the videos via http in my web browser and stream them via smplayer just fine. No dealing with mounting shares or fstab silliness.

    Leave a comment:


  • schmalzler
    replied
    Originally posted by Ericg View Post
    One important thing that was missed... the bug that caused the taskbar to randomly re-arrange and overlap has been officially closed (Whether as FIXED or WONTFIX varies on your perspective lol) no one so far as been able to reproduce the behavior in KDE 4.11-- with the new QML based taskbar. So if you hate that bug you have to upgrade to 4.11 to not be affected by it.
    https://bugs.kde.org/show_bug.cgi?id=321181

    If it turns out there really is going on some memory corruption things will get worse thanks to the new QML task bar Debugging memory corruptions is IMHO harder than debugging layouting.

    Leave a comment:


  • bwat47
    replied
    Originally posted by Thaodan View Post
    If you open a file in a smb:// share KDE downloads it for you and says the programm to open the tmp file.
    This doesn't seem to work anymore in most KDE distros that I've tried... Opening the file from dolphin in dragon player or smplayer just does nothing. And even if it did its still far worse than with gvfs because I have to download a huge video file instead of just streaming it.

    Originally posted by GreatEmerald View Post
    I don't see how you can mount a share without configuring anything - you still need to tell the system where the share is found and how to handle it...
    With a file manager that supports gvfs-smb you can do exactly this without ANY configuration. In nautilus or thunar you simply browse to the share just like you would in dolphin, only upon clicking on the share the file manager automatically *mounts* the share on demand via gvfs, making the files on the share available as if they were local files to all application. It works far better than KDE's KIO system for doing things like streaming videos from a smb share. Its very convienient, quick, and requires zero configuration.

    Originally posted by erendorn View Post
    You shouldn't have to be root to mount a network drive.
    You shouldn't have to use fstab to mount a share at a friend's house/client network.
    If you have per user personal network drives, and multi users PCs, well, it doesn't scale well.

    Yes, it is easy to configure fstab, and is ok enough for most cases.
    No, it is not sufficient.
    Agreed! This is exactly the point I'm trying to make
    Last edited by bwat47; 06-15-2013, 09:39 AM.

    Leave a comment:


  • Thaodan
    replied
    Originally posted by erendorn View Post
    You shouldn't have to be root to mount a network drive.
    You shouldn't have to use fstab to mount a share at a friend's house/client network.
    If you have per user personal network drives, and multi users PCs, well, it doesn't scale well.

    Yes, it is easy to configure fstab, and is ok enough for most cases.
    No, it is not sufficient.
    If you open a file in a smb:// share KDE downloads it for you and says the programm to open the tmp file.

    Leave a comment:


  • erendorn
    replied
    Originally posted by GreatEmerald View Post
    Again, I don't have much experience with SMB or gvfs, but using a GUI tool to configure fstab is really not hard. I don't see how you can mount a share without configuring anything - you still need to tell the system where the share is found and how to handle it...
    You shouldn't have to be root to mount a network drive.
    You shouldn't have to use fstab to mount a share at a friend's house/client network.
    If you have per user personal network drives, and multi users PCs, well, it doesn't scale well.

    Yes, it is easy to configure fstab, and is ok enough for most cases.
    No, it is not sufficient.

    Leave a comment:


  • GreatEmerald
    replied
    Again, I don't have much experience with SMB or gvfs, but using a GUI tool to configure fstab is really not hard. I don't see how you can mount a share without configuring anything - you still need to tell the system where the share is found and how to handle it...

    Leave a comment:


  • bwat47
    replied
    Originally posted by GreatEmerald View Post
    Well yea, that's my point – just have it configured in /etc/fstab.
    And my point is that configuring shares in fstab is a huge pain in the ass compared to gnome's gvfs solution. I was not able to get dolphin to mount/unmount the shares with a smb share in my fstab because for some reason mounting a smb cifs share even when its in fstab requires root. It was not even remotely as close to as convenient as using gvfs.

    Users shouldn't be expected to edit /etc/fstab for this kind of simple functionality. I expect to be able to mount/unmount my shares in the file manager on demand as a user, and anything else is not acceptable.

    Dolphin/kde does not handle this "to the best of its ability", because handling it to the best of its ability would either be using gvfs or a gvfs solution to actually mount the shares on the fly so applications can actually use the files on the share. Dicking around with fstab for hours is not my definition of convenience or user friendliness.

    I really like KDE but this is without a doubt a big issue IMO.
    Last edited by bwat47; 06-14-2013, 05:18 PM.

    Leave a comment:


  • GreatEmerald
    replied
    Originally posted by Sho_ View Post
    This isn't relevant for shares configured via fstab, but it is for users who don't want to do that and use apps not using KIO.
    Well yea, that's my point ? just have it configured in /etc/fstab.

    Leave a comment:


  • Sho_
    replied
    Originally posted by Awesomeness View Post
    Well, I get the argument for 4.10 but considering that 4.11 is supposed to be an ?LTS? release some Plasma widgets may actually get new feature releases before PW2 is ready for widespread consumption. Tweaking things like version support in BKO sounds to me like less work than to do a whole ?4.12? just because some QML Plasma applets have been updated and released possibly just released via GHNS.
    If you're referring to making 4.x test releases of PW2 QML widgets, that won't be feasible in most cases because the QML1->2 transition does involve some API breakages (not so much on the QML side, but certainly on the C++ side hosting the QML content, if only by allowing to eliminate more of that C++ side), and there will also be API breakages in the Plasma QML components that have been frozen for a while in 4.x. It wouldn't be feasible to keep releasing the PW2 port of the new Task Manager for 4.x without substantial overhead to maintain two diverged codebases, for example.

    Leave a comment:

Working...
X