Closed sweetpi closed 10 years ago
- How about this name instead? parseKeyValueMessage
Sound good.
- It should not be a static method because it does not depend on the state of the MpdClient instance. e.g. at the top of the file MpdClient.parseKeyValueMessage = parseKeyValueMessage; and then define parseKeyValueMessage below.
Because it does not depend on the state of MpdClient it should be static, or am I wrong? It is static at the moment (not added to the prototype, but to the constructor function instead). But sure I can move it to the top like the cmd
function.
Oops, my mistake. You did it static already. For some reason I thought it was using prototype. And then I accidentally typed "should not be static" instead of "should be static".
Like the new name and thanks for the cool module. Did the changes.
I published version 1.1.0 so you can use it.
P.S. check out Groove Basin, it supports the MPD protocol and does some things that MPD cannot do.
Thanks!
Really cool project. Definitively giving Groove Basin a try. I'm working on a pimatic plugin for controlling mpd, but maybe it will become a controller for Groove Basin in my setup :).
Btw: On what kind of server is the live demo running? Looking for a cheap node.js hosting solution for a pimatic demo.
Really cool project. Definitively giving Groove Basin a try. I'm working on a pimatic plugin for controlling mpd, but maybe it will become a controller for Groove Basin in my setup :).
Cool! Feel free to file any issues that come your way and I'll try to fix them.
Btw: On what kind of server is the live demo running? Looking for a cheap node.js hosting solution for a pimatic demo.
An EC2 micro instance, which costs 114 USD per year. (They charge per hour, but it's easier to understand a yearly cost in my opinion.)
2 things:
parseKeyValueMessage
MpdClient.parseKeyValueMessage = parseKeyValueMessage;
and then defineparseKeyValueMessage
below.