From kfm-devel Sun Feb 14 11:55:11 1999 From: Simon Hausmann Date: Sun, 14 Feb 1999 11:55:11 +0000 To: kfm-devel Subject: kfm view plugins? X-MARC-Message: https://marc.info/?l=kfm-devel&m=91902935106277 Hi, I've thinking about a possible kfm view plugin interface: (in regard to all the "dreams" about embedded whatever_views :-) 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 :). 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 - - IRCNet #colorfast Life's not fair. But the root password helps. :-)