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

List:       kfm-devel
Subject:    kfm view plugins?
From:       Simon Hausmann <tronical () gmx ! net>
Date:       1999-02-14 11:55:11
[Download RAW message or body]

Hi,

I've thinking about a possible kfm view plugin interface:
(in regard to all the "dreams" about embedded whatever_views :-)

<example>
When currently clicking on an image the appropriate image viewer loads up, in a
new window.
What I'd like to have is the configurable option to embedd the image viewer
instead of letting it pop up as yet another new window.
In order to support this kind of embedding the image viewer has to "export" an
image-view as part (or opview) (of course :).
</example>

What remains is the problem of how to find out whether an application supports
this kind of embedding.

My idea is quite simple:
Every app which supports embedding as part has additional entries in it's
.kdelnk file (maybe like: SupportsPartPlugin=Yes; PartPluginExec=appname
--server;RepoID:Whatever/Anything:Bla.Bla;ActivationMode:Blahgubla) .
Now if embedding is enabled for a specific mime-type kfmrun can handle this by
looking if the app supports embedding as part (via the .kdelnk file) and tell
kfmgui to open a new part view (hello kmultipanner-discussion-guys :-) )

What do you think?

(
What remains is imho the problem of activating these parts, 'cause currently
OpenParts does not support persistent menus which will lead to the situation
that when activating an embedded part all konqueror menus will get lost (in
the current implementation of kfmgui as part itself)
(of course they will get restored again when re-activating kfmgui again)
)

Bye,
 Simon

--
Simon Hausmann - Tronical^Colorfast - <tronical@gmx.net> - IRCNet #colorfast

Life's not fair. But the root password helps. :-)

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