i guess i could write 3rd party xbmc launcher for windows for u guys (and me too
)
i have just question for devs:
lets say i would do something like this - open listening socket on the same port like xbmc http api - after client connected i would immidiately close connection and launch xbmc - how would remote react on such thing - i mean fake xbmc http server that will close as soon as some1 will connect to it?
--edit
ok, done rly quick & dirty windows app that do what i wrote above and it works but its kinda ugly
- xbmclauncher (as i quickly called it) will have to run in background all the time (if ppl would be interested in this, maybe i would rewrote it as windows service if its possible)
- when xbmc remote tries to connect to xbmc host, it actually connect first to xbmclauncher. connection is closed, xbmc remote is displaying message "connection refused" and real xbmc is launched. now just retry connection in xbmc remote and we can use it
just need some time to make editable settings - right now my settings (which are 1. path to xbmc.exe 2. port of xbmc http api) are hardcoded
question for devs - the thing with connection refused is kinda ugly - if ppl would be interested in this maybe we could define some signature that xbmclauncher would send when remote is connecting to it, so the remote instead of refused connection would display "xbmc is launching, please wait"?