by TIV73 » Mon Jul 02, 2018 12:10 pm
Hi PetrCBR,
I fully agree, the new engine is a massive step forward from the old one in MM3/4, no questions here.
I wasn't actually talking about that, though - let me rephrase the question. I wrote a
.net library, which allows external applications to connect to mediamonkey 5. A sample application using this library is a
rainmeter plugin which displays information about the currently playing song in MM5.
The library connects to chromium via the exposed remote debugging api on port 9222 and can send javascripts command to mediamonkey which I then use to read data or send remote control commands.
When writing the original version of the library I didn't really pay much attention to code quality, some of its dependencies aren't being developed anymore and need to be replaced, I wrote the thing before MM5 supported async calls which need to be implemented for performance reasons, etc.. Long story short, the project probably wouldn't pass a code review. That is why I'm thinking of rewriting it.
Hence the question - is the release versions of MM5 planned to still expose port 9222 or is this a alpha/beta thing only? Because if it won't I have to look for alternatives like WMI (which I try to avoid because it's only availale on windows).
Hi PetrCBR,
I fully agree, the new engine is a massive step forward from the old one in MM3/4, no questions here.
I wasn't actually talking about that, though - let me rephrase the question. I wrote a [url=https://github.com/mmuffins/MediaMonkeyNet].net library[/url], which allows external applications to connect to mediamonkey 5. A sample application using this library is a [url=https://github.com/mmuffins/rainmeter-mediamonkey]rainmeter plugin[/url] which displays information about the currently playing song in MM5.
The library connects to chromium via the exposed remote debugging api on port 9222 and can send javascripts command to mediamonkey which I then use to read data or send remote control commands.
When writing the original version of the library I didn't really pay much attention to code quality, some of its dependencies aren't being developed anymore and need to be replaced, I wrote the thing before MM5 supported async calls which need to be implemented for performance reasons, etc.. Long story short, the project probably wouldn't pass a code review. That is why I'm thinking of rewriting it.
Hence the question - is the release versions of MM5 planned to still expose port 9222 or is this a alpha/beta thing only? Because if it won't I have to look for alternatives like WMI (which I try to avoid because it's only availale on windows).