zkharazishvili / sopcast-player

Automatically exported from code.google.com/p/sopcast-player
0 stars 0 forks source link

Add sop:// support to browser #13

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
On windows, we can click a sop:// link and sopcast will automatically
start, I hope that we can implement the same for linux.

Take a look on apturl packege which add apt:// support to browser.

Original issue reported on code.google.com by frankwon...@gmail.com on 27 May 2009 at 5:04

GoogleCodeExporter commented 8 years ago
I will take a look at the viability of this, only roadblock is having to check 
if FF
is installed and tracking down the location of the conf files. I will take a 
look at
the apturl project that you suggested to see how it is implemented in that 
project.

Original comment by flyguy97 on 1 Jun 2009 at 7:13

GoogleCodeExporter commented 8 years ago

Original comment by flyguy97 on 4 Jun 2009 at 9:07

GoogleCodeExporter commented 8 years ago
Might this technique (https://www.spotify.com/en/help/faq/wine/) from Spotify 
work:

Opening spotify URIs from browsers

This has been tested and works with Firefox (Iceweasel), Epiphany and Opera 9.5.

To be abe to open spotify URIs you first need a simple script:

echo '#!/bin/sh' > ~/.browser2spotify
echo 'exec wine "C:\Program Files\Spotify\spotify.exe" /uri "$@"' >> 
~/.browser2spotify
chmod 755 ~/.browser2spotify

(Change the path to the spotify executable if necessary)
Firefox/Epiphany

In Epiphany enter the following in the URI field:

about:config

Right click and select New > Boolean and name it
network.protocol-handler.external.spotify and set it to True

Right click and select New > String and name it 
network.protocol-handler.app.spotify
and set the name to ~/.browser2spotify

Original comment by jackhy...@gmail.com on 17 Jul 2009 at 7:45

GoogleCodeExporter commented 8 years ago
The only issue with this is that it does not gracefully fail. What I mean is 
that if
the executable for sopcast-player is in /bin or ~/bin instead of /usr/bin there 
is no
way of predicting what needs to be entered into the 
network.protocol-handler.external
and network.protocol-handler.app portions of the about:config. If the user 
themselves
want to set these values this is viable but coding it would be very difficult. 
I am
working on an option that will write values to the 
/etc/firefox-3.0/pref/firefox.js
file which is the back door to the about:config option, but again the issue of 
where
this file is located will be critical. It is frustrating that in Linux all the 
paths
to configuration files, executables, even home directories are user-definable, 
but I
guess flexibility is one of the things that make Linux great as well. Thank you 
for
your suggestion, I will look further into what can be done to automate links.

Original comment by flyguy97 on 18 Jul 2009 at 1:54

GoogleCodeExporter commented 8 years ago
This feature has been included in SopCast v0.3.3 for ubuntu.

Original comment by flyguy97 on 24 Nov 2009 at 9:42

GoogleCodeExporter commented 8 years ago
I have sop player 0.4.0 for Lucid lynx ubuntu and there is no sop:// support in
firefox (version 3.6.3). Perhaps this will work with an install of 0.3.0 but I 
just
wanted to draw this to your attention.

Original comment by Michael.Kyles@gmail.com on 2 May 2010 at 1:35