[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kfm-devel
Subject:    Re: Konq: History functionality and the Views
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-06-14 15:42:10
[Download RAW message or body]

On Mon, 14 Jun 1999, David Faure wrote:

> I think the easiest and cleanet way is to
> have the external program register a factory that
> can re-create the view whenever needed
> (meaning that insertview would _not_ be available in the IDL,
> but registerFactory would be instead).
> 
> This way, we don't add bloat to the current mechanism
> (which doesn't need factories)
> and we can have the external program (say a mail reader)
> recreate its view when we want it to.

GREAT IDEA!!!!!

> (We need to ask for a particular servicetype, but also for a particular
> URL, right ?
> say application/x-mailbox and file:/home/dfaure/mail/kde-devel)

Hmm, this is difficult.
I'm still soo unsure about all this, and unfortunately the IDEAS (former
DESIGN) document doesn't help here... ;)

Theoretically we can view any kind of data, as long as two conditions are
true:

1) The data is addressable by an URL

2) KRun (with KMimeMagic and the KIOJobs) is able to successfully detect
   the mimetype of the data addressed by the URL.

Now 1) is 100% clear.

But I fear 2) is not enough for all the stuff written in IDEAS.

I mean: I fear we cannot define a mimetype for all stuff we plan to
display in Konqueror and then let the user browse to the location on his
hdd where the newsgroups folders are stored for example.

In other words:
The iconview/treeview is one way to "guide" the user to the data, for
example to an image.
But IMHO _some_ data can't be really "found" by browsing with the
iconview/treeview, like mailbox folders for example (well, of course you
can, but IMHO it's not very comfortable to search on my hdd where such
data is stored, just in order to be able to browse them with Konqueror) .

One way which comes to my mind are "GUI plugins" , 100% similar (in
appearance) to the plugins in the toolbar you can see in KSpread.

Although this is a pretty limited way, IMHO we should really implement 
this functionality.

Coming back to the original topic: 
What apps for example would want to insert a view via your above described
factory/servicetype(url) idea?

IMHO KMail/Empath/Magellan for example would rather like to add a toolbar
button and/or menu entry somewhere in the mainview's gui, so that the user
can more easily "launch" the view.

But I'm kind of clueless. Perhaps some app really wants to register a view
via a servicetype binding at run-time, instead of the "standard" .desktop
file way?

> (or servicetype="mailbox", simply... how are servicetype currently named ?)

AFAIK there's no real naming standard. I once had a discussion with Alex
on irc about that, and we both agreed that a kind of hierachy makes sense,
similar to the mimetypes. What do you think?

Ciao,
  Simon

--
Simon Hausmann       <hausmann@kde.org>
http://www.kde.org/  <tronical@gmx.net>

[prev in list] [next in list] [prev in thread] [next in thread]