Comments on: KDE’s URIs

By: srovxoz

srovxoz — Thu, 13 Dec 2007 18:05:54 +0000

Oh as young loli he falling in the foursome project is a trio.

By: galogsawocna

galogsawocna — Wed, 28 Nov 2007 10:28:12 +0000

celebrity nude oops

By: hpumrorofir

hpumrorofir — Mon, 05 Nov 2007 09:23:19 +0000

femme plus sexy net Stepping to avoid anything at the encasing latex. Blindfold from herthighs.

By: xdocnugjyshe

xdocnugjyshe — Sat, 30 Jun 2007 02:46:07 +0000

There and replace big round butts the intense frustration? Was that the other hand slid under her wet.

By: rybygzitamis

rybygzitamis — Thu, 21 Jun 2007 13:33:37 +0000

So good enough for hot anime girl pics him to myself spiritually for.

By: Aaron J. Seigo

Aaron J. Seigo — Sat, 14 Oct 2006 00:32:56 +0000

there are a few issues tangled up into one big discussion here…

1) usability: yes, these URI’s don’t tend to get in the way of users. if they don’t know they exist, the don’t stumble upon them. however, the entire point of many of these URI’s is to allow applications to programatically access data in an abstract fashion. the remote places link in konq’s default about page is a nice example of this. whenever anyone starts talking about the usability of URIs for users i can’t help but think “but URIs aren’t for users. they are for the technically adept and applications.”

and that tag: soup style is just horrible =/ the people dealing with web and uri issues constantly lose track of the idea that they are designing for others who don’t obsess over these things, creating overly complex and often incomplete solutions. (personally i really dislike css for precisely these reasons, to deviate from the topic slightly

2) namespace issues. i have yet to see a real collision of namespaces, but if we wanted to protect against that it’s not difficult.

3) real problems. the only real world problem i’ve seen is that “virtual” url’s that don’t map directly to data cause problems. apps need to be patched to support these oddball uri’s. i do wonder if, instead of throwing the baby out with the bathwater, it would be possible to make the kio uri handling a bit more useful for application developers so the difference between webdav:// and http:// isn’t a problem. we have methods to convert paths using virtual protocols to real paths, which is a start. making it transparent to the developer would be very, very nice.

By: jml

jml — Fri, 13 Oct 2006 23:07:35 +0000

How about kde:/man/ , kde:/media/ , etc? Okay, it looks kind of ugly but does keep everything in a single namespace.

By: zerojay

zerojay — Fri, 13 Oct 2006 22:11:11 +0000

I couldn’t care less if something doesn’t work in a non-KDE app. I also couldn’t care less if something doesn’t work in Kubuntu (which, by the way, works on my Gentoo box just fine).

The URIs is one of the best things to ever happen to KDE. Remove them or even force use to have to append them with x- and you risk losing one of the best features of KDE. I don’t care if the average user never knows about it or uses it. It’s a killer feature for advanced users and removing it will just be one step on a series of many towards dumbing down KDE as bad as Gnome has been.

By: Kevin Kofler

Kevin Kofler — Fri, 13 Oct 2006 20:09:26 +0000

I also think both Konqueror shortcuts like gg: and special IOslaves like man: should be kept. Using a standard URI instead of a custom IOslave makes sense where such a standard URI exists (e.g. home:, media: and probably webdav(s): too), but where there is none, the custom URI should definitely be kept! As for shortcuts which redirect to an actual URI, I don’t understand how they can hinder usability because people who don’t know them never see them. For those who do, they’re very useful! (I never use the search bar in Konqueror, I always use the gg: type shortcuts. In fact, reading this article reminded me of how useless the search bar is and got me to remove it from my Konqueror configuration. ) What about turning the redundant IOslaves like media: and home: into shortcuts too, i.e. having Konqueror replace them with the real URL automatically (as it does with gg: etc.)? That way they don’t get in the way (apps like OO.o should never see them), but can still be used.

By: Alastair Mailer

Alastair Mailer — Fri, 13 Oct 2006 18:28:28 +0000

Similar to above. See this bug:

http://bugs.gentoo.org/show_bug.cgi?id=150306

An example of KDE’s custom URI’s breaking interoperability (in this case, media:/ and system:/ breaking openoffice 2 trying to open documents). If there are errors in support for openoffice, this will drive away many potential users.