faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
|
Tenor KIO-slave?
by Janne on Wednesday 13/Apr/2005, @23:55
|
Maybe I missed this part in the article, but... How will Tenor be implemented? Will there be a separate Tenor-app that you use, or will it end up being a KIO-slave? I could see benefits in having "tenor://seigo kde-usability png" in file-dialog for example. The example would find all png's that were sent to kde-usability by Aaron J. Seigo. yes, the example is pretty limited, but gets the idea across.
Of course, there is a problem that KDE has even today: how do we tell the users about all the great technology KDE has? I still run in to KDE-users who do not know about audiocd:// or fish://! |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Tenor KIO-slave?
by Scott Wheeler on Thursday 14/Apr/2005, @00:26
|
That's kind of the wrong way of looking at it -- "Tenor" isn't something that users will use directly; it's a framework, not a tool or a specific interface component.
The way that it will show up to users is simply applications that work "smarter", search that works better, desktop browsing (in applications or the file browser) that knows about relationships.
So, it's not a tool and it's not storage abstraction; it's a mechanism to make applications able to work with context.
In this sense -- libkio is something that makes it possible to work with various sorts of input and output in KDE. Tenor is something that makes it possible to work with context.
There probably will be some specific new applications that emerge built completely around its capabilities, but that's the second step. :-)
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Janne on Thursday 14/Apr/2005, @01:01
|
"That's kind of the wrong way of looking at it -- "Tenor" isn't something that users will use directly; it's a framework, not a tool or a specific interface component."
I was under the impression that Tenor is somekind of "Spotlight on steroids" :). As in: a set of technology that can be embedded in to the system. Maybe I should RTFA again :).
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Scott Wheeler on Thursday 14/Apr/2005, @01:41
|
Well, the article is mostly speculative. I'm fundamentally an application developer (that ends up spending more than half of my time on framework components, so...) so when I explained this stuff to Kurt at one point I mostly talked in terms of what people will be able to do with this stuff.
In other words the things that Kurt mentions are the things that I've designed towards; concrete use cases, if you will. But the user visible things will come as applications start to use the framework and new tools are written to take advantage of it. I'll probably write a basic search tool to show off the possibilities and then let the interface guys have fun with it. :-)
Basically Tenor makes it easy to write a "Spotlight on steroids" -- like libkio and KHTML make it easy to throw together a basic webbrowser, but that's not what Tenor itself is.
Part of the problem with explaining some of the stuff is that it's sometimes hard to imagine how something will work when there's nothing popular to really compare it to. Most of the stuff that people think of is a subset of what Tenor makes possible.
|
[
Reply To This | View ]
|
|
Re: Tenor KIO-slave?
by charles on Thursday 14/Apr/2005, @01:06
|
>Of course, there is a problem that KDE has even today: how do we tell the users >about all the great technology KDE has? I still run in to KDE-users who do not >know about audiocd:// or fish://!
I guess I am one of them. When I paste audiocd:// into the location bar on Konqueror, I get a dialogue "Malformed URL audiocd://" The same applies to fish://.
In my protocols config dialog, I have "fish" and it's checked, "audiocd" is missing. I am running kde3.4. Where is the documentation on these protocols? Doing a google search brings up so much information not so useful to a n00b like me. Thanx.
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by anon on Thursday 14/Apr/2005, @01:33
|
Charles.
do you have kde-multimedia installed? I guess you are just missing some part of KDE.
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Daniel Molkentin on Thursday 14/Apr/2005, @02:32
|
It's "audiocd:/" and "fish://" needs to go with a hostname or an IP, e.g. "fish://my.server.tld".
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by charles on Thursday 14/Apr/2005, @14:21
|
That did it, thanx! While I know what ftp:// and http:// or https:// can be used for, I wonder what use could be made of fish://. Since I have no system setup for the fish protocol, could you point me to one? Cb..
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Spy Hunter on Thursday 14/Apr/2005, @18:51
|
That's what's great about fish://, there's no setup, your linux machines are already fish servers (as long as they run an SSH server, which almost all do). For any Linux or Unix machine you have a username, simply use fish://username@machinename to access the filesystem of that machine using that username. Unfortunately, it doesn't work for Windows machines, for that you have to use smb://.
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave? - Wow!
by charles on Friday 15/Apr/2005, @01:51
|
I can only say wooooow! I never knew KDE has this feature and I guess I am missing a lot more. I guess I can put "fish://username@machinename" in the save dialogue to save a file on this machine if everything is setup. This kind of publicity is what we need for KDE. When I get back to the Linux box at home I will try it out! Thanx. What other exciting protocols/goodies are there to exploit?
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave? - Wow!
by blacksheep on Friday 15/Apr/2005, @04:56
|
To get a list of all the available protocols:
$ kcmshell ioslaveinfo
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by jms on Thursday 14/Apr/2005, @02:35
|
Its audiocd:/, and fish://hostname or fish:/
Which distro are you using?
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by blacksheep on Thursday 14/Apr/2005, @02:51
|
My only grip about KIO is that tar, rar, etc should be implemented as pipes or something like that. I mean, it should be possible to view a TAR file from a FTP. Dunno if this is being worked on. My suggestion for how the url would look like is something like this: scp://server.com/file.tar|tar .
Anyway, yes, KIO is one of the best piece of software that lives in KDE. Really useful.
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Illissius on Thursday 14/Apr/2005, @08:28
|
I've always thought something like ftp://ftp.server.com/file.tar#tar:/file/inside/it would make sense -- taking a cue from the webpage.html#anchor-to-jump-to syntax. Don't know whether it would conflict with anything else, though.
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Spy Hunter on Thursday 14/Apr/2005, @19:21
|
It would be great except that somebody might use anchors named tar: in their html file, and even possibly name their html file with a .tar extension. It would be hard to figure out what was meant in every situation.
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by James L on Thursday 14/Apr/2005, @08:38
|
It is actually, and honestly a very annoying/good thing (depending on what I want to do, which I don't expect KDE to be able to telepathically figure out) with my config is that it does show up as the opened tar file over ftp or http. (It's something I forget which under file types, show in embedded viewer as default I believe.)
And tar, gzip, bzip all already are piped through eachother. The tar kio-slave only handles uncompressed tar files (As of at least KDE 2.x, as I last recall looking. I doubt it would have changed), and the appropriate gzip/bzip kio-slave is used automatically.
Ie, tar://home/user/example.tar.gz is really tar://gzip://home/user/example.tar.gz (or something like that)
|
[
Reply To This | View ]
|
Re: Tenor KIO-slave?
by Spy Hunter on Thursday 14/Apr/2005, @12:23
|
Here's my proposal: stack the protocols at the beginning, using the username part of the standard URL format as the file path for the archive. I think this could be implemented with no changes to the KIO framework, all the work would be done in the new IOSlaves.
A simple one: open a zip file on an HTTP server.
zip:/@http://server/file
Open a bzip2 compressed tar file on an HTTP server
tar:/@bzip2:@http://server/file
A complex example: open a particular file in a passworded rar file through fish://.
rar:/rardir/rarfile:rarpass@fish://user:pass@server/file.
|
[
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)
