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

List:       kfm-devel
Subject:    Re: KFM Error
From:       Matthias Elter <me () kde ! org>
Date:       1999-03-29 13:40:38
[Download RAW message or body]

On Mon, 29 Mar 1999, David Faure wrote:
> On Mon, Mar 29, 1999 at 09:36:55AM +0200, Matthias Elter wrote:
> > On Sun, 28 Mar 1999, Simon Hausmann wrote:
> > > On Sun, 28 Mar 1999, David Faure wrote:
> > > 
> > > > On Sun, Mar 28, 1999 at 06:50:28PM +0200, Rob Kaper wrote:
> > > > > "The requested action
> > > > > get telnet://capsi.cx:2300/
> > > > > is not implemented yet."
> > > > > 
> > > > > Looks to me this is a rather simple one to hack into kfm.. launch a kvt (or
> > > > > whatever Terminal program has been specified with -e telnet, voila.
> > > > 
> > > > This is right. kfm is not developed anymore, but this a nice feature for
> > > > the successor of kfm, called 'konqueror' (or konqy).
> > > > 
> > > > Simon, while making the plugin mechanism, can you think of a way to
> > > > specify, in a plugin kdelnk : for the protocol "telnet:", something like ;
> > > > launch konsole -e telnet %host  ?
> > > > 
> > > > 
> > > > This will allow the same kind of protocol support for other protocols as
> > > > well, without hacking the code.
> > > > I can think of "rlogin:", and even of somebody wanting to use, say, ncftp
> > > > for "ftp:" transfers, and netscape for "http:" transfers.
> > > > (For this we need to make plugins chosen before hardcoded protocols
> > > > (kio_http for http:, ...)
> > > > Users love be customize everything, and a lot of them want to use kfm/konqy 
> > > > as file manager only and netscape as web browser... which can be
> > > > understood, especially if there is java in the pages ;)
> > > 
> > > 100% agree.
> > >  
> > > a) completely override libkio for configured protocols
> > >    Before executing KRun we check to protocol and call the appropriate
> > >    application.
> > >    I think the problem here is the configuration: How do we find out
> > >    which application supports protocol xyz?
> > >    How do applications "tell" Konqy that they support a certain protocol?
> > >    (for MimeTypes this was kind of easy: KRun did the job of finding an
> > >     application. Then we just checked the .kdelnk file. But how to do
> > >     without KRun? How to find the .kdelnk? )
> > > 
> > > b) integration in libkio
> > >    Perhaps someone has a nice idea of a possible integration in the
> > >    ProtocolManager (without breaking KIOJob ;) ) ?
> > 
> > I like the idea of plugin protocols but what does a user have from typing
> > netscape://www.kde.org instead of http://www.kde.org. 
> Nothing. We never said that (or I misunderstand).
> telnet is a protocol, rlogin too, hence the URLs "telnet://host" and "rlogin://host".
> 
> netscape is not a protocol, but a handler that could be set for "http://".
> So the user would still enter "http://" and that would open netscape, if
> such a plugin exists.

Ops I was tired this morning...I perhaps read the netscape thing between
the lines. I hate these summer/winter time changes here in Europe. Sorry :-)

> > IMHO if a user want's to
> > use netscape for web browsing instead of konqy it would be nice to simply being
> > able to associate a application with a protocol. For example a user
> > could want to associate "http://" with netscape and konqy would launch netscape
> > every time a user clicks on a "http://" link.
> > But perhaps a dialog to assign all sorts of protocols to commands is to hard to
> > configure for novice users. Perhaps a konqy option "Follow remote links with
> > netscape" would be enough.

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