[RFC] One ioslave to rule them all...
lauri at kde.org
Sun Jun 26 23:04:24 BST 2005
On Sunday 26 June 2005 23.16, Kévin Ottens wrote:
> Le Dimanche 26 Juin 2005 21:27, Alexander Neundorf a écrit :
> I don't think so... I think that remote:/ is overcrowded already, it was
> meant to be simple and now we have already several entries in it. I don't
> see the point of accessing bookmarks in a filesystem tree, it's normally
> tied to the web browser use, but maybe I'm missing some use cases.
Not so much showing the Konqueror bookmarks, but bookmarks *into* the file
system, especially on remote shares, make an enormous amount of sense to me.
I have to deal with SMB url's like
"//SERVER/SHARE/Ny Mapp (2)/Märknadsföring/Bilder/originellt/2005-05-25/miljö
bild/grön/" or "//SERVER/SHARE/Media/pdfer/ny pdfer/att maila/hemmet/reklam
A lot of them are either fairly short lived, or apparently randomly named by
whoever made them, or sometimes both (I sometimes find things that were meant
to be short lived, but were so randomly named, they're still there 5 years
You better believe I bookmark them. I'd never find them again otherwise.
I presume I am not the only person doomed to suffer a fate of working with
insane people who name things strangely and have enormous file servers and so
are never motivated to clean things up. Which leads me to believe that
anyone dealing with very long paths on very big file servers, will find
bookmarks useful for things that you have to look at reasonable often, or at
least, more than once, but not enough to warrant a full mount, or cluttering
up remote:/ with. In any case, bookmarks I can organise by project, by
projected longevity, by who put stuff in them, mounts and remote:/ url's I
KDE Documentation: http://docs.kde.org
KDE on FreeBSD: http://freebsd.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
More information about the kde-core-devel