Re: Tenor KIO-slave?

faq
flatforty
contribute
subscribe
configure
search
rdf

main
parent
thread

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. :-)

Related Links

·   Articles on KDE in the News
·   Also by Scott Wheeler
·   Contact author

The Fine Print: The following comments are owned by whomever posted them.
( Reply )

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 ]

The Fine Print: The previous comments are owned by whomever posted them.
( Reply )


		"Ironically, we are working on that right now!" -- Kurt Granroth
KDE®, "K Desktop Environment", "KDE Dot News", "got the dot?" and the KDE Logo® are trademarks or registered trademarks of KDE e.V. in the European Union, the United States and other countries. All other trademarks and copyrights on this page are owned by their respective owners. Comments are owned by the poster. The rest: Copyright © 2000-2008 KDE e.V. for The KDE Project. For further information or comments on this site, please contact the Webmaster.