Replies: 4 comments 1 reply
-
|
This is great info. Thanks for digging into this. I think it would be easy to serve out that java script from my slingplayer app. You can easily redirect that url locally by editing the "hosts" file on your PC/Linux box. It might be lmhosts on the PC.
PS. would you be interested in a preview of the 3.08 release? My testing has stalled due to a currently 4 day power outage where my slingboxes are located in Nova Scotia. |
Beta Was this translation helpful? Give feedback.
-
|
Sure, I would give it a try. There were a couple changes that I made to get things working for the 500 and I was going to wait and see if the next version of your software fixes. |
Beta Was this translation helpful? Give feedback.
-
|
I would really like to get a hold of the java script (or the whole shooting match). I've been discussing issues with reconfiguring the slingbox after Nov 9 on Reddit |
Beta Was this translation helpful? Give feedback.
-
|
Yea, that all seems to be in the javascript file. You would need to do a bit of reverse engineering, the method calls are generic so might not be easiest to follow. ` function y() { Seems this function call is used a lot to build the URL you listed |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
This may be more trouble then it's worth but I found that the sling player desktop software has a app preference defined which lets you set the starturl which the desktop app launches.
You can find it if you navigate to:
%appdata%\Sling Media\Slingplayer Desktop\Resources\AppPreference.ini
I navigated to the starturl that was defined there and downloaded the entire website, it's an html page and a few jquery ui .js files. Some interesting stuff in there, the .js file is 60k lines of code. Found this, which confirms things from another thread
And the launch URL
I wonder if it's possible to set this code up on a dummy webserver, maybe even part of GerryDazoo's slinger app, to host this code and modify it however we need it to get through a configuration (including to change the launch URL). Then update the starturl to point to the new webserver to keep the desktop app functional.
Also, there is a console.log from the desktop app which has some interesting things in it, including the adminPassword. Which may be helpful for those that did not retrieve the adminPassword before servers shut down, but they have used the desktop app before in the past.
%appdata%\Sling Media\Slingplayer Desktop\Logs\console.log
The console log also listed out the IR codes when you connect to the device.
And there is a folder for remote codes which have been used on the machine before, including some image files,
%appdata%\Sling Media\WebSlingPlayer\Remote
Beta Was this translation helpful? Give feedback.
All reactions