2011-01-20, 10:26
Pr.Sinister Wrote:#2) What is the proper syntax for VideoPlayer.SeekPercentage ? I have tried pretty much everything i can think of including :
Code:{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": {"": "50"}, "id": "1"}
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": {"": 50}, "id": "1"}
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": {"parameter": "50"}, "id": "1"}
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": [50], "id": "1"}
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", ["50"], "id": "1"}
You haven't tried all the possibilities Currently you'll have to use
Code:
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": 50, "id": "1"}
Code:
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": [50], "id": "1"}
Code:
{"jsonrpc": "2.0", "method": "VideoPlayer.SeekPercentage", "params": {"value": "50"}, "id": "1"}
Fiasco Wrote:The database is either in a sqlite db file or in mysql. The client has access to it.
I used perl via http GET like so
xbmc.pl?genre=horror&type=moviesbygenre
xbmc.pl?type=moviesbydate
And format the output in a way that is readily split on a delimeter and parsed w/ a regex by the controller. Having the response formatted how I need it outweighs any effort required to tweak my select statements should XBMC change the DB table structures around.
Not sure how that exposes the database to mre risk than a json call.
I'm strictly pulling metadata.
This may be all good and well if YOU run a custom script for YOURSELF on YOUR system when it's only YOUR database that is lost when you do something wrong. But as soon as someone wants to write a third-party software which shall be distributed for others to use the risk and possible damage is a lot higher. Furthermore installation instructions like "Install Apache on your computer" etc tend to get people with less computer experience lost and won't allow them to use the software. That's why there's a json rpc api which can be used in combination with already existing json (rpc) parsers. I agree there is a lot of missing functionality but if noone says the out loud topfs2 will have to get his crystal ball from the cellar and try to read everyone's mind