faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Not Ready.
by PT on Friday 11/Nov/2005, @17:36
|
As long as slave forwarding doesnt work.
Try opening a .tar.bz2 in media:/whatever. It doesnt work.
Or is it planned for KDE4 only? |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Not Ready.
by Davide Ferrari on Saturday 12/Nov/2005, @00:57
|
Gosh, you're correct, this is really an issue since IOSlaves are going to be the default to navigate through your file system in KDE 3.5 (think of home:/). There is definitely the problem of appending one IOS to another, and the new default will lead to lots of complains, I bet.
|
[
Reply To This | View ]
|
Re: Not Ready.
by superstoned on Saturday 12/Nov/2005, @01:36
|
this still doesn't work? i thought it got fixed... at least you can now burn cd's from media:/ directly with k3b...
|
[
Reply To This | View ]
|
Re: Not Ready.
by Morty on Saturday 12/Nov/2005, @04:44
|
Not exactly the same, this is about using ioslaves in media:/. If you have Ark installed it will handle the compressed file seamlessly, but kio_tar etc will not.
Personally I think the concept of the whole system:/ and media:/ thing are broken, the k3b issues demonstrated it nicely. Inconsistencies keep popping up all over the place requiring constant fiddling with the implementation. And even if you neglect the inconsistency issues, the end result still does not improve usability very much. Which was the whole purpose of the thing.
|
[
Reply To This | View ]
|
Re: Not Ready.
by Davide Ferrari on Sunday 13/Nov/2005, @23:06
|
Well, IMO the idea of abstracting from the regular Unix filesystem is a great one, don't get me wrong, but while Kevin put a lot of effort into it. it's something that has should be postponed for KDE4...it's quite a radical change and as you said the process it's leaving quite a few inconsistencies (being the KIOs append issue one of the most noticeble).
IMO now in RC1 time is even too late to step back, it will lead to even worst problems IMO, so let's hope in the 3.5.x series for some bugfixes and definitely to KDE4 for a major revamp.
|
[
Reply To This | View ]
|
Re: Not Ready.
by Leo on Tuesday 15/Nov/2005, @09:19
|
Yeah, the implementation needs a lot of work. In its current state, it is a huge step backwards from standard paths. For example, take this common task (I just ran into this yesterday)
In kubuntu, plug in a Digital camera, and the media://camera pops up in konqueror. So far so good. Now I want to send a picture to a contact on MSN through Kopete. So logically I go Send file - navigate to the media://camera directory, and choose my picture. But then kopete says that I cannot choose remote files to send. Huh? Remote files? It's on my camera! Now I know enough to copy the pics to the hard drive first, but a normal user would be stumped at this point. I really don't understand why we can't let the distro mount the camera under /media/camera or whatever and open that dir in konqueror when a camera is plugged in. Would make everything much more consistant.
|
[
Reply To This | View ]
|
Re: Not Ready.
by LB on Tuesday 15/Nov/2005, @13:11
|
Another example;
If I put a movie-dvd in the player, it's mounted and shown as media:/hdc, in the media:/-view it's impossible to view the dvd-content (files) in Konqueror, I need to manually go to the mount-path in Konqueror, to be honest this is quite annoying.
|
[
Reply To This | View ]
|
Re: Not Ready.
by Morty on Tuesday 15/Nov/2005, @15:36
|
Leo:
"it is a huge step backwards from standard paths."
"I really don't understand why we can't let the distro mount the camera under /media/camera or whatever and open that dir in konqueror when a camera is plugged in. Would make everything much more consistant."
LB:
"in the media:/-view it's impossible to view the dvd-content (files) in Konqueror. to be honest this is quite annoying."
I can't say anything other than I agree with Leo and LB, the only thing actually achieved by trying to abstract the regular Unix paths with this are making everything less consistent. And having to do lots of work hunting all the different kind of use cases and make them work. And rather than creating better usability, it only creates a inconsistent mess. Introducing another naming scheme for the users to learn. And it's at best only marginally better usability wise, and even useless for legacy applications. IMHO the whole idea should have undergone a real usability review, with lots of why's asked.
|
[
Reply To This | View ]
|
Re: Not Ready.
by Ewan Marshall on Monday 28/Nov/2005, @12:31
|
This is because kopete is detecting the media:// as a remote protocol just like http:// in a web browser. And therefore its upto kopete to modify its code to allow this as a local protocol. The other option would be to take you back to the standard path, but it's more about time to get the new system running consistently with other apps.
|
[
Reply To This | View ]
|
|
Re: Not Ready.
by Nicolas Goutte on Saturday 12/Nov/2005, @01:05
|
Is there already a bug report for this? If yes, can you give the number. (Thank you!)
Have a nice day!
|
[
Reply To This | View ]
|
Re: Not Ready.
by Nicolas Goutte on Saturday 12/Nov/2005, @07:29
|
Bug #73821 is more general and can probably not be implemented in KDE3.
But media: often handles local files and so they should be given to a tar: (or zip:) KIO slave.
Have a nice day!
|
[
Reply To This | View ]
|
Re: Not Ready.
by PT on Monday 14/Nov/2005, @22:14
|
I reported it in august:
http://bugs.kde.org/show_bug.cgi?id=110951
(or bug:110951 for the ALT+F2 lovers out there).
And its not even confirmed yet.
Was I too vague in the bug description?
|
[
Reply To This | View ]
|
|
Re: Not Ready.
by MamiyaOtaru on Saturday 12/Nov/2005, @02:16
|
huh. Zero problems with that here. I can go to media:/sdb1 or whatever and open all the zip, tar.gz or tar.bz2 files I want. (this in KDE 3.4.2). Is there some more specific case you can give me that should fail?
|
[
Reply To This | View ]
|
Re: Not Ready.
by kundor on Monday 14/Nov/2005, @10:35
|
Maybe you should try using the release that is supposed to be broken, ie KDE 3.5, instead of a completely different version?
|
[
Reply To This | View ]
|
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
