Originally posted by Ericg
View Post
Announcement
Collapse
No announcement yet.
Features Baking For KDE 4.11
Collapse
X
-
Originally posted by Awesomeness View PostI'm pretty sure the QML taksbar also works with 4.10 because kdelibs is in freeze since 4.9 or so now.
Cheers,
Eike, who wrote the new QML version
Comment
-
Originally posted by Sho_ View PostWhile it's possible to build just the library and widget and run them against 4.10, you'll run into runtime problems with some windows not being listed unless "Only show windows from this activity" is disabled in the settings
Incompatible options could be disabled.
Comment
-
Originally posted by Awesomeness View PostSounds like a rather small tradeoff. In such a case I wonder why the QML widgets aren't released to KDE Look or wherever for users to beta test them without getting the beta-quality rest.
Incompatible options could be disabled.
- Releasing something that requires compilation, immediately limiting the audience (and the audience who is fine with compiling is more prone to being fine with just running a beta of the whole set).
- Putting together a new tarball for lib and widget, which involves such things as extracting the relevant translation files from the repositories (they are not kept with the source to make things easier for the translators), writing a new build system, ...
- Making the changes you suggest to deal with the incompatible-features situation, which invites the risk of creating entirely new bugs that result in feedback noise.
- Not to mention that testing against a workspace version it isn't destined to be used with might also turn up additional incompatibilities that were previously unknown, resulting in more feedback noise about things that don't actually need fixing.
- Dealing with the fact that our bug tracker doesn't know a version for this out-of-band release.
And so on, and so on - now imagine every developer doing that for their little piece of the whole, and it's a substantial overhead burden.
Edit: One more: Since the library has third-party users it involves keeping track of whether the changes that were done to it broke the ABI or not, and if it did, naming it differently in the special test release to avoid breaking other widgets the user may be using. More changes = more opportunities for bugs to creep in. This wouldn't be relevant for the actual 4.11 (beta or final) release because we put no ABI stability guarantee on libtaskmanager (unlike with kdelibs), so distros know they're going to have to rebuild downstream users of it.Last edited by Sho_; 12 June 2013, 11:37 PM.
Comment
-
Originally posted by bwat47 View PostWith most other file managers, such as nautilus, thunar, or pcmanfm when you access a network share it mounts it on the fly using GVFS. This makes it so any application can access/play these files because they are treated like local files.
KDE does not mount the share, instead it browses the shares with its own KIO/Kioslaves system, the problem with this is typically only KDE software supports kioslaves, and in some cases even KDE software doesn't support them well enough (for example dragonplayer doesn't seem to support a smb kioslave and simply fails to play videos from a smb share in dolphin). Gnome's GVFS solution works with ALL software, its far superior.
I don't find mounting the share in fstab to be an acceptable solution. This is a laptop and the share is not always available, and with a CIFS mount you can get locking up issues in KDE when the share is not available. To me the only acceptably solution is something where I can easily mount and unmount the shares on the fly, as a user. SMB4k is the best I've found so far for kde but its kind of buggy unfortunately.
Note the "/export/storage on dragon". It's an NFS share. It's not mounted by default. When I click it, it gets mounted. When I right-click it and select Unmount, it gets unmounted.
I set up the whole NFS share not even by editing /etc/fstab, but by just using YaST with these settings (sorry for the localisation, but it should be straight-forward to understand):
Comment
-
Originally posted by Sho_ View PostReleasing something that requires compilation, immediately limiting the audience (and the audience who is fine with compiling is more prone to being fine with just running a beta of the whole set).
Originally posted by Sho_ View PostPutting together a new tarball for lib and widget, which involves such things as extracting the relevant translation files from the repositories (they are not kept with the source to make things easier for the translators), writing a new build system, ...
- Making the changes you suggest to deal with the incompatible-features situation, which invites the risk of creating entirely new bugs that result in feedback noise.
- Not to mention that testing against a workspace version it isn't destined to be used with might also turn up additional incompatibilities that were previously unknown, resulting in more feedback noise about things that don't actually need fixing.
- Dealing with the fact that our bug tracker doesn't know a version for this out-of-band release.
Comment
-
Originally posted by Thaodan View PostWhat are gains when building KDE with c++11?All opinions are my own not those of my employer if you know who they are.
Comment
-
Originally posted by GreatEmerald View PostHmm? It works via fstab just fine. Here's how it looks for me:
Note the "/export/storage on dragon". It's an NFS share. It's not mounted by default. When I click it, it gets mounted. When I right-click it and select Unmount, it gets unmounted.
I set up the whole NFS share not even by editing /etc/fstab, but by just using YaST with these settings (sorry for the localisation, but it should be straight-forward to understand):
Last edited by bwat47; 13 June 2013, 10:22 PM.
Comment
-
Originally posted by Awesomeness View PostWell, 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.
Comment
Comment