Welcome to the Second Life Forums Archive

These forums are CLOSED. Please visit the new forums HERE

kde kio-secondlife?

Conny Quaggy
Registered User
Join date: 9 Mar 2007
Posts: 7
05-23-2007 10:12
Hi folks,

first of all, since I started in February I almost only use the linux clients on different Gentoo systems and must say: Absolutely great work!

On my systems there is no difference between the Win32 client and the Linux client when it comes to stability. I would even say, the linux client runs more stable than the win32 one. At least on my systems, but a perfect system where all library dependencies are correct is an absolute prerequisite.

But now my question: Is there a kde kio-secondlife available to handle secondlife://... requests?
Or is there an equivalent for Mozilla's browsers?

And if not: Is it possible to force a running linux-client e.g. by script to TP to a given location? Does it read from STDIN?

Many thanks in advance,
yours Conny
Antonius Misfit
Certifiable Linux Addict
Join date: 13 Jun 2006
Posts: 97
None that I know of, but...
05-23-2007 10:45
From: Conny Quaggy

But now my question: Is there a kde kio-secondlife available to handle secondlife://... requests?
Or is there an equivalent for Mozilla's browsers?

And if not: Is it possible to force a running linux-client e.g. by script to TP to a given location? Does it read from STDIN?


There was a Firefox hack that involved using "about:config" to launch the client with the SLurl as the starting point, but that's obsolete now thanks to Mozilla integration with the client. All you need to do is open up your profile, go to the Web tab, paste the SLurl into the location and hit Load. Immediately the map will pop up with the Slurl as the destination.

As far as the kio-slave for SL is concerned, there's nothing that I've heard of, but it certainly would be a good idea. Anybody know a good tutorial on creating kioslaves?
Still Defiant
Registered User
Join date: 9 Jan 2007
Posts: 5
05-23-2007 18:15
For a simple KDE handler, you can put the following in $KDEHOME/share/services/secondlife.protocol

From: someone

[Protocol]
exec=secondlife -url '%u'
protocol=secondlife
helper=true


The default for $KDEHOME is ~/.kde (or use $KDEDIR for all users) and the 'exec' line can be whatever command you use (must be in $PATH unless you provide the full path yourself).

After adding the file, run "kbuildsycoca" from the command line to update the configuration database.
Antonius Misfit
Certifiable Linux Addict
Join date: 13 Jun 2006
Posts: 97
Wow...
05-23-2007 18:55
I didn't think it would be that easy! It's even easier to implement than the old Firefox hack. But it does have the same drawback: It merely launches a new instance of the client with the SLurl as the starting point. It can't send the Slurl to an already-running instance of SL. Any ideas how to get around that, other than the integrated browser trick I mentioned earlier?
Conny Quaggy
Registered User
Join date: 9 Mar 2007
Posts: 7
05-24-2007 05:26
SLURL handling seems to be broken in the linux client!
Try calling a "secondlife://firstname lastname" slurl.
Even if the url was correctly url-encoded so the link is "secondlife://firstname+lastname" it doesn't work.

I followed the call of the client and the slurl is passed correctly, but the linux client cuts the -url parameter at the first blank.

Do you encounter the same problem?

Yours Conny
Conny Quaggy
Registered User
Join date: 9 Mar 2007
Posts: 7
05-24-2007 08:19
A friend of mine (Henri Boa) provided a fix for the slurl problem.

Please read the thread "SLURL handling seems to be broken" to get it.

Yours Conny
Still Defiant
Registered User
Join date: 9 Jan 2007
Posts: 5
05-24-2007 22:36
From: someone

It can't send the Slurl to an already-running instance of SL. Any ideas how to get around that, other than the integrated browser trick I mentioned earlier?

Skimming the viewer source, I don't see any IPC code to handle that. To get around it... complicated preload tricks (maybe) or xsendkey hacks come to mind. For the standard viewer, though, it's up to JIRA. Nice browser trick, though.