ruby-mpd 0.3.1 → 0.3.2

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA1:
3
- metadata.gz: d97d6dfaa6b5323b36dcd22fba6c4bcd43bf562c
4
- data.tar.gz: 5b006f249e407ff97378887b8bf60ad94035c97c
3
+ metadata.gz: 49bd6de309c1177f46f4ab1c1f049cf5139bebe4
4
+ data.tar.gz: 718d011451c59c356bf32260fd2c512dc444e68b
5
5
  SHA512:
6
- metadata.gz: e7c25979f1d9af125916c1f3072d0f5678bbe8afdb4b7c7b2c7804062cd5e154658097958418fbca579801ec441ab86e08a2b5202403fd440b6bc73cc42cd3c0
7
- data.tar.gz: dda3e10e3c3a74433a48832178c78a25188c947ee407fb7897e0944a49f5b0d8557691bf1fd8515a2d4ff4e1487e83ec2f2fb37c581de608cb722c4da4b2582b
6
+ metadata.gz: 4c78a607aa4a0242dae9535c9404800352579c9566bb8a6b4e19445fc32183e524a194fd57bcf7c9d7ca83a2cbbb5167ab19621bee7072d056372002cc801dea
7
+ data.tar.gz: d7484a6502644919540a4148782b39e67d85cc4ac78f3cab32b525e52cf5168639273f45b2162202e08195c37377fc183066a45409924a0edb3df673b063800e
data/.gitignore CHANGED
@@ -1,22 +1,21 @@
1
1
  *.gem
2
2
  *.rbc
3
- .bundle
4
3
  .config
5
- coverage
4
+ .yardoc
5
+ /.bundle/
6
+ /.yardoc
7
+ /_yardoc/
8
+ /coverage/
9
+ /doc/
10
+ /Gemfile.lock
11
+ /pkg/
12
+ /spec/reports/
13
+ /tmp/
14
+ _yardoc
15
+ config.yml
16
+ Gemfile.lock
6
17
  InstalledFiles
7
18
  lib/bundler/man
8
- pkg
9
19
  rdoc
10
- spec/reports
11
20
  test/tmp
12
21
  test/version_tmp
13
- tmp
14
-
15
- # YARD artifacts
16
- .yardoc
17
- _yardoc
18
- doc/
19
-
20
- Gemfile.lock
21
-
22
- config.yml
data/Gemfile ADDED
@@ -0,0 +1,6 @@
1
+ source 'https://rubygems.org'
2
+
3
+ # Specify your gem's dependencies in ruby-mpd.gemspec
4
+ gemspec
5
+
6
+ gem 'pry'
data/LICENSE.txt ADDED
@@ -0,0 +1,339 @@
1
+ GNU GENERAL PUBLIC LICENSE
2
+ Version 2, June 1991
3
+
4
+ Copyright (C) 1989, 1991 Free Software Foundation, Inc.,
5
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
6
+ Everyone is permitted to copy and distribute verbatim copies
7
+ of this license document, but changing it is not allowed.
8
+
9
+ Preamble
10
+
11
+ The licenses for most software are designed to take away your
12
+ freedom to share and change it. By contrast, the GNU General Public
13
+ License is intended to guarantee your freedom to share and change free
14
+ software--to make sure the software is free for all its users. This
15
+ General Public License applies to most of the Free Software
16
+ Foundation's software and to any other program whose authors commit to
17
+ using it. (Some other Free Software Foundation software is covered by
18
+ the GNU Lesser General Public License instead.) You can apply it to
19
+ your programs, too.
20
+
21
+ When we speak of free software, we are referring to freedom, not
22
+ price. Our General Public Licenses are designed to make sure that you
23
+ have the freedom to distribute copies of free software (and charge for
24
+ this service if you wish), that you receive source code or can get it
25
+ if you want it, that you can change the software or use pieces of it
26
+ in new free programs; and that you know you can do these things.
27
+
28
+ To protect your rights, we need to make restrictions that forbid
29
+ anyone to deny you these rights or to ask you to surrender the rights.
30
+ These restrictions translate to certain responsibilities for you if you
31
+ distribute copies of the software, or if you modify it.
32
+
33
+ For example, if you distribute copies of such a program, whether
34
+ gratis or for a fee, you must give the recipients all the rights that
35
+ you have. You must make sure that they, too, receive or can get the
36
+ source code. And you must show them these terms so they know their
37
+ rights.
38
+
39
+ We protect your rights with two steps: (1) copyright the software, and
40
+ (2) offer you this license which gives you legal permission to copy,
41
+ distribute and/or modify the software.
42
+
43
+ Also, for each author's protection and ours, we want to make certain
44
+ that everyone understands that there is no warranty for this free
45
+ software. If the software is modified by someone else and passed on, we
46
+ want its recipients to know that what they have is not the original, so
47
+ that any problems introduced by others will not reflect on the original
48
+ authors' reputations.
49
+
50
+ Finally, any free program is threatened constantly by software
51
+ patents. We wish to avoid the danger that redistributors of a free
52
+ program will individually obtain patent licenses, in effect making the
53
+ program proprietary. To prevent this, we have made it clear that any
54
+ patent must be licensed for everyone's free use or not licensed at all.
55
+
56
+ The precise terms and conditions for copying, distribution and
57
+ modification follow.
58
+
59
+ GNU GENERAL PUBLIC LICENSE
60
+ TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
61
+
62
+ 0. This License applies to any program or other work which contains
63
+ a notice placed by the copyright holder saying it may be distributed
64
+ under the terms of this General Public License. The "Program", below,
65
+ refers to any such program or work, and a "work based on the Program"
66
+ means either the Program or any derivative work under copyright law:
67
+ that is to say, a work containing the Program or a portion of it,
68
+ either verbatim or with modifications and/or translated into another
69
+ language. (Hereinafter, translation is included without limitation in
70
+ the term "modification".) Each licensee is addressed as "you".
71
+
72
+ Activities other than copying, distribution and modification are not
73
+ covered by this License; they are outside its scope. The act of
74
+ running the Program is not restricted, and the output from the Program
75
+ is covered only if its contents constitute a work based on the
76
+ Program (independent of having been made by running the Program).
77
+ Whether that is true depends on what the Program does.
78
+
79
+ 1. You may copy and distribute verbatim copies of the Program's
80
+ source code as you receive it, in any medium, provided that you
81
+ conspicuously and appropriately publish on each copy an appropriate
82
+ copyright notice and disclaimer of warranty; keep intact all the
83
+ notices that refer to this License and to the absence of any warranty;
84
+ and give any other recipients of the Program a copy of this License
85
+ along with the Program.
86
+
87
+ You may charge a fee for the physical act of transferring a copy, and
88
+ you may at your option offer warranty protection in exchange for a fee.
89
+
90
+ 2. You may modify your copy or copies of the Program or any portion
91
+ of it, thus forming a work based on the Program, and copy and
92
+ distribute such modifications or work under the terms of Section 1
93
+ above, provided that you also meet all of these conditions:
94
+
95
+ a) You must cause the modified files to carry prominent notices
96
+ stating that you changed the files and the date of any change.
97
+
98
+ b) You must cause any work that you distribute or publish, that in
99
+ whole or in part contains or is derived from the Program or any
100
+ part thereof, to be licensed as a whole at no charge to all third
101
+ parties under the terms of this License.
102
+
103
+ c) If the modified program normally reads commands interactively
104
+ when run, you must cause it, when started running for such
105
+ interactive use in the most ordinary way, to print or display an
106
+ announcement including an appropriate copyright notice and a
107
+ notice that there is no warranty (or else, saying that you provide
108
+ a warranty) and that users may redistribute the program under
109
+ these conditions, and telling the user how to view a copy of this
110
+ License. (Exception: if the Program itself is interactive but
111
+ does not normally print such an announcement, your work based on
112
+ the Program is not required to print an announcement.)
113
+
114
+ These requirements apply to the modified work as a whole. If
115
+ identifiable sections of that work are not derived from the Program,
116
+ and can be reasonably considered independent and separate works in
117
+ themselves, then this License, and its terms, do not apply to those
118
+ sections when you distribute them as separate works. But when you
119
+ distribute the same sections as part of a whole which is a work based
120
+ on the Program, the distribution of the whole must be on the terms of
121
+ this License, whose permissions for other licensees extend to the
122
+ entire whole, and thus to each and every part regardless of who wrote it.
123
+
124
+ Thus, it is not the intent of this section to claim rights or contest
125
+ your rights to work written entirely by you; rather, the intent is to
126
+ exercise the right to control the distribution of derivative or
127
+ collective works based on the Program.
128
+
129
+ In addition, mere aggregation of another work not based on the Program
130
+ with the Program (or with a work based on the Program) on a volume of
131
+ a storage or distribution medium does not bring the other work under
132
+ the scope of this License.
133
+
134
+ 3. You may copy and distribute the Program (or a work based on it,
135
+ under Section 2) in object code or executable form under the terms of
136
+ Sections 1 and 2 above provided that you also do one of the following:
137
+
138
+ a) Accompany it with the complete corresponding machine-readable
139
+ source code, which must be distributed under the terms of Sections
140
+ 1 and 2 above on a medium customarily used for software interchange; or,
141
+
142
+ b) Accompany it with a written offer, valid for at least three
143
+ years, to give any third party, for a charge no more than your
144
+ cost of physically performing source distribution, a complete
145
+ machine-readable copy of the corresponding source code, to be
146
+ distributed under the terms of Sections 1 and 2 above on a medium
147
+ customarily used for software interchange; or,
148
+
149
+ c) Accompany it with the information you received as to the offer
150
+ to distribute corresponding source code. (This alternative is
151
+ allowed only for noncommercial distribution and only if you
152
+ received the program in object code or executable form with such
153
+ an offer, in accord with Subsection b above.)
154
+
155
+ The source code for a work means the preferred form of the work for
156
+ making modifications to it. For an executable work, complete source
157
+ code means all the source code for all modules it contains, plus any
158
+ associated interface definition files, plus the scripts used to
159
+ control compilation and installation of the executable. However, as a
160
+ special exception, the source code distributed need not include
161
+ anything that is normally distributed (in either source or binary
162
+ form) with the major components (compiler, kernel, and so on) of the
163
+ operating system on which the executable runs, unless that component
164
+ itself accompanies the executable.
165
+
166
+ If distribution of executable or object code is made by offering
167
+ access to copy from a designated place, then offering equivalent
168
+ access to copy the source code from the same place counts as
169
+ distribution of the source code, even though third parties are not
170
+ compelled to copy the source along with the object code.
171
+
172
+ 4. You may not copy, modify, sublicense, or distribute the Program
173
+ except as expressly provided under this License. Any attempt
174
+ otherwise to copy, modify, sublicense or distribute the Program is
175
+ void, and will automatically terminate your rights under this License.
176
+ However, parties who have received copies, or rights, from you under
177
+ this License will not have their licenses terminated so long as such
178
+ parties remain in full compliance.
179
+
180
+ 5. You are not required to accept this License, since you have not
181
+ signed it. However, nothing else grants you permission to modify or
182
+ distribute the Program or its derivative works. These actions are
183
+ prohibited by law if you do not accept this License. Therefore, by
184
+ modifying or distributing the Program (or any work based on the
185
+ Program), you indicate your acceptance of this License to do so, and
186
+ all its terms and conditions for copying, distributing or modifying
187
+ the Program or works based on it.
188
+
189
+ 6. Each time you redistribute the Program (or any work based on the
190
+ Program), the recipient automatically receives a license from the
191
+ original licensor to copy, distribute or modify the Program subject to
192
+ these terms and conditions. You may not impose any further
193
+ restrictions on the recipients' exercise of the rights granted herein.
194
+ You are not responsible for enforcing compliance by third parties to
195
+ this License.
196
+
197
+ 7. If, as a consequence of a court judgment or allegation of patent
198
+ infringement or for any other reason (not limited to patent issues),
199
+ conditions are imposed on you (whether by court order, agreement or
200
+ otherwise) that contradict the conditions of this License, they do not
201
+ excuse you from the conditions of this License. If you cannot
202
+ distribute so as to satisfy simultaneously your obligations under this
203
+ License and any other pertinent obligations, then as a consequence you
204
+ may not distribute the Program at all. For example, if a patent
205
+ license would not permit royalty-free redistribution of the Program by
206
+ all those who receive copies directly or indirectly through you, then
207
+ the only way you could satisfy both it and this License would be to
208
+ refrain entirely from distribution of the Program.
209
+
210
+ If any portion of this section is held invalid or unenforceable under
211
+ any particular circumstance, the balance of the section is intended to
212
+ apply and the section as a whole is intended to apply in other
213
+ circumstances.
214
+
215
+ It is not the purpose of this section to induce you to infringe any
216
+ patents or other property right claims or to contest validity of any
217
+ such claims; this section has the sole purpose of protecting the
218
+ integrity of the free software distribution system, which is
219
+ implemented by public license practices. Many people have made
220
+ generous contributions to the wide range of software distributed
221
+ through that system in reliance on consistent application of that
222
+ system; it is up to the author/donor to decide if he or she is willing
223
+ to distribute software through any other system and a licensee cannot
224
+ impose that choice.
225
+
226
+ This section is intended to make thoroughly clear what is believed to
227
+ be a consequence of the rest of this License.
228
+
229
+ 8. If the distribution and/or use of the Program is restricted in
230
+ certain countries either by patents or by copyrighted interfaces, the
231
+ original copyright holder who places the Program under this License
232
+ may add an explicit geographical distribution limitation excluding
233
+ those countries, so that distribution is permitted only in or among
234
+ countries not thus excluded. In such case, this License incorporates
235
+ the limitation as if written in the body of this License.
236
+
237
+ 9. The Free Software Foundation may publish revised and/or new versions
238
+ of the General Public License from time to time. Such new versions will
239
+ be similar in spirit to the present version, but may differ in detail to
240
+ address new problems or concerns.
241
+
242
+ Each version is given a distinguishing version number. If the Program
243
+ specifies a version number of this License which applies to it and "any
244
+ later version", you have the option of following the terms and conditions
245
+ either of that version or of any later version published by the Free
246
+ Software Foundation. If the Program does not specify a version number of
247
+ this License, you may choose any version ever published by the Free Software
248
+ Foundation.
249
+
250
+ 10. If you wish to incorporate parts of the Program into other free
251
+ programs whose distribution conditions are different, write to the author
252
+ to ask for permission. For software which is copyrighted by the Free
253
+ Software Foundation, write to the Free Software Foundation; we sometimes
254
+ make exceptions for this. Our decision will be guided by the two goals
255
+ of preserving the free status of all derivatives of our free software and
256
+ of promoting the sharing and reuse of software generally.
257
+
258
+ NO WARRANTY
259
+
260
+ 11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY
261
+ FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN
262
+ OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES
263
+ PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED
264
+ OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
265
+ MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS
266
+ TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE
267
+ PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING,
268
+ REPAIR OR CORRECTION.
269
+
270
+ 12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
271
+ WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR
272
+ REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES,
273
+ INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING
274
+ OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED
275
+ TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY
276
+ YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER
277
+ PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE
278
+ POSSIBILITY OF SUCH DAMAGES.
279
+
280
+ END OF TERMS AND CONDITIONS
281
+
282
+ How to Apply These Terms to Your New Programs
283
+
284
+ If you develop a new program, and you want it to be of the greatest
285
+ possible use to the public, the best way to achieve this is to make it
286
+ free software which everyone can redistribute and change under these terms.
287
+
288
+ To do so, attach the following notices to the program. It is safest
289
+ to attach them to the start of each source file to most effectively
290
+ convey the exclusion of warranty; and each file should have at least
291
+ the "copyright" line and a pointer to where the full notice is found.
292
+
293
+ <one line to give the program's name and a brief idea of what it does.>
294
+ Copyright (C) <year> <name of author>
295
+
296
+ This program is free software; you can redistribute it and/or modify
297
+ it under the terms of the GNU General Public License as published by
298
+ the Free Software Foundation; either version 2 of the License, or
299
+ (at your option) any later version.
300
+
301
+ This program is distributed in the hope that it will be useful,
302
+ but WITHOUT ANY WARRANTY; without even the implied warranty of
303
+ MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
304
+ GNU General Public License for more details.
305
+
306
+ You should have received a copy of the GNU General Public License along
307
+ with this program; if not, write to the Free Software Foundation, Inc.,
308
+ 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.
309
+
310
+ Also add information on how to contact you by electronic and paper mail.
311
+
312
+ If the program is interactive, make it output a short notice like this
313
+ when it starts in an interactive mode:
314
+
315
+ Gnomovision version 69, Copyright (C) year name of author
316
+ Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'.
317
+ This is free software, and you are welcome to redistribute it
318
+ under certain conditions; type `show c' for details.
319
+
320
+ The hypothetical commands `show w' and `show c' should show the appropriate
321
+ parts of the General Public License. Of course, the commands you use may
322
+ be called something other than `show w' and `show c'; they could even be
323
+ mouse-clicks or menu items--whatever suits your program.
324
+
325
+ You should also get your employer (if you work as a programmer) or your
326
+ school, if any, to sign a "copyright disclaimer" for the program, if
327
+ necessary. Here is a sample; alter the names:
328
+
329
+ Yoyodyne, Inc., hereby disclaims all copyright interest in the program
330
+ `Gnomovision' (which makes passes at compilers) written by James Hacker.
331
+
332
+ <signature of Ty Coon>, 1 April 1989
333
+ Ty Coon, President of Vice
334
+
335
+ This General Public License does not permit incorporating your program into
336
+ proprietary programs. If your program is a subroutine library, you may
337
+ consider it more useful to permit linking proprietary applications with the
338
+ library. If this is what you want to do, use the GNU Lesser General
339
+ Public License instead of this License.
data/README.md ADDED
@@ -0,0 +1,276 @@
1
+ # ruby-mpd
2
+
3
+ ruby-mpd is a powerful object-oriented client for the [Music Player Daemon](http://www.musicpd.org), forked from librmpd. librmpd is as of writing outdated by 6 years! This library tries to act as a successor, originally using librmpd as a base, however almost all of the codebase was rewritten. ruby-mpd supports all "modern" MPD features as well as callbacks.
4
+
5
+ ## MPD Protocol
6
+
7
+ The Music Player Daemon protocol is implemented inside the library. The implementation brings the entire set of features to ruby, with support of the newest protocol commands. However some commands were remapped, some were converted to objects, as I felt they fit this way much more into ruby and are more intuitive.
8
+
9
+ ## Usage
10
+
11
+ Add to your `Gemfile`:
12
+
13
+ ```ruby
14
+ gem 'ruby-mpd'
15
+ ```
16
+
17
+ Then `bunde install`, require and make a new MPD instance:
18
+
19
+ ```ruby
20
+ require ‘ruby-mpd’
21
+ mpd = MPD.new 'localhost', 6600
22
+ ```
23
+
24
+ You can also omit the host and port, and it will use the defaults.
25
+
26
+ ```ruby
27
+ mpd = MPD.new 'localhost'
28
+ mpd = MPD.new
29
+ ```
30
+
31
+ Once you have an instance of the MPD class, connect to the server.
32
+
33
+ ```ruby
34
+ mpd.connect
35
+ ```
36
+
37
+ When you are done, disconnect by calling disconnect.
38
+
39
+ ```ruby
40
+ mpd.disconnect
41
+ ```
42
+
43
+ *Note*: In the past, one had to tackle the issue of the server possibly disconnecting the client at any time due to inactivity. Since 0.3.0, this is handled automatically via a reconnect mechanism.
44
+
45
+ Once connected, you can issue commands to talk to the server.
46
+
47
+ ```ruby
48
+ mpd.connect
49
+ mpd.play if mpd.stopped?
50
+ song = mpd.current_song
51
+ puts "Current Song: #{song.artist} - #{song.title}"
52
+ ```
53
+
54
+ Command documentation can be found [here](http://www.rubydoc.info/github/archSeer/ruby-mpd/master/MPD).
55
+
56
+ ## Commands
57
+
58
+ Some commands require URI paths. `ruby-mpd` allows you to use `MPD::Song` objects directly and it extracts the file paths behind the scenes.
59
+
60
+ ```ruby
61
+ song = mpd.songs_by_artist('Elvis Presley').first # => MPD::Song
62
+ mpd.add song
63
+ ```
64
+
65
+ ### Options
66
+
67
+ Some commands accept "option hashes" besides their default values. For example, `#move` accepts an ID key instead of the position:
68
+
69
+ ```ruby
70
+ mpd.move(1, 10) # => move first song to position 10.
71
+ mpd.move({:id => 1}, 10) # => move the song with the ID of 1 to position 10.
72
+ ```
73
+
74
+ Commands that accept ID's: `#move`, `#delete`, `#play`, `#song_priority`. `#seek` accepts both `:pos` and `:id`. *Note*: `#swap` and `#swapid` are still separate!
75
+
76
+ ### Ranges
77
+
78
+ Some commands also allow ranges instead of numbers, specifying a range of songs. ruby-mpd correctly handles inclusive and exclusive ranges (`1..10` vs `1...10`). Negative range end means that we want the range to span until the end of the list.
79
+
80
+ For example, `#queue` allows us to return only a subset of the queue:
81
+
82
+ ```ruby
83
+ mpd.queue.count # => 20
84
+ mpd.queue(1..10).count # => 10
85
+ mpd.queue(5..-1).count # => 15 (from 5 to the end of the range)
86
+ mpd.queue(5...-1).count # => 15 (does the same)
87
+ ```
88
+
89
+ Move also allows specifying ranges to move a range of songs instead of just one.
90
+
91
+ ```ruby
92
+ mpd.move 1, 10 # => move song 1 to position 10.
93
+ mpd.move 1..3, 10 # => move songs 1, 2 and 3 to position 10 (and 11 and 12).
94
+ ```
95
+
96
+ Commands that support ranges: `#delete`, `#move`, `#queue`, `#song_priority`, `#shuffle`, `MPD::Playlist#load`.
97
+
98
+ ## Searching
99
+
100
+ The MPD protocol supports two commands `find` and `search`, where `find` is strict and will be case sensitive, as well as return only full matches, while `search` is "loose" -- case insensitive and allow partial matches.
101
+
102
+ For ease of use, ruby-mpd encapsulates both `find` and `search` in one method, `MPD#where`.
103
+
104
+ Searching is case *loose* by default, meaning it is case insensitive, and will do partial matching. To enable *strict* matching, enable the `strict` option.
105
+
106
+ This does not work for `Playlist#searchadd`.
107
+
108
+ ```ruby
109
+ mpd.where({artist: 'MyArtiSt'}, {strict: true})
110
+ ```
111
+
112
+ Multiple query parameters can also be used:
113
+
114
+ ```ruby
115
+ mpd.where(artist: 'Bonobo', album: 'Black Sands')
116
+ ```
117
+
118
+ Query keys can be any of of the tags supported by MPD (a list can be fetched via `MPD#tags`), or one of the two special parameters: `:file` to search by full path (relative to database root), and `:any` to match against all available tags.
119
+
120
+ While searching, one can also enable the `add` option, which will automatically add the songs the query returned to the queue. In that case, the response will only return
121
+ `true`, stating that the operation was successful (instead of returning an array).
122
+
123
+ ```ruby
124
+ mpd.where({artist: 'MyArtiSt'}, {strict: true, add: true})
125
+ ```
126
+
127
+ ### Queue searching
128
+
129
+ Queue searching works the same way (except by using `MPD#queue_where`), and it also accepts multiple search parameters (which seems to be undocumented in the MPD protocol
130
+ specification).
131
+
132
+ Same as `#where`, it is "loose" by default, and it supports a `:strict` option.
133
+
134
+ ```ruby
135
+ mpd.queue_where(artist: 'James Brown', genre: 'Funk')
136
+ mpd.queue_where({artist: 'James Brown', genre: 'Funk'}, {strict: true})
137
+ ```
138
+
139
+ ## Playlists
140
+
141
+ Playlists are one of the objects that map the MPD commands onto a simple to use object. Instead of going trough all those function calls, passing data along to get your results, you simply use the object in an object-oriented way:
142
+
143
+ ```ruby
144
+ mpd.playlists # => [MPD::Playlist, MPD::Playlist...]
145
+ playlist = mpd.playlists.first
146
+ p playlist.name # => "My playlist"
147
+ playlist.songs # => [MPD::Song, MPD::Song...]
148
+ playlist.rename('Awesomelist')
149
+ p playlist.name # => "Awesomelist"
150
+ playlist.add('awesome_track.mp3')
151
+ ```
152
+
153
+ To create a new playlist, simply create a new object. The playlist will be created in the daemon's library automatically as soon as you use `#add` or `#searchadd`. There is also no save method, as playlists get 'saved' by the daemon any time you do an action on them (add, delete, rename).
154
+
155
+ ```ruby
156
+ MPD::Playlist.new(mpd, 'name')
157
+ ```
158
+
159
+ Currently, one also has to pass in the MPD instance, as playlists are tied to a certain connection.
160
+
161
+ ## Callbacks
162
+
163
+ Callbacks are a simple way to make your client respond to events, rather that have to continuously ask the server for updates. This allows you to focus on displaying the data, rather that working overly hard to get it. This is done by having a background thread continuously check the server for changes.
164
+
165
+ To make use of callbacks, we need to:
166
+
167
+ 1. Setup a callback to be called when something happens.
168
+ 2. Create a MPD client instance with callbacks enabled.
169
+
170
+ Firstly, we need to create a callback block and subscribe it, so that will get triggered whenever a specific event happens. When the callback is triggered, it will also recieve the new values of the event that happened.
171
+
172
+ So how do we do this? We use the `MPD#on` method, which sets it all up for us. The argument takes a symbol with the name of the event. The function also requires a block, which is our actual callback that will get called.
173
+
174
+ ```ruby
175
+ mpd.on :volume do |volume|
176
+ puts "Volume was set to #{volume}!"
177
+ end
178
+ ```
179
+
180
+ One can also use separate methods or Procs and whatnot, just pass them in as a parameter.
181
+
182
+ ```ruby
183
+ # Using a Proc
184
+ proc = Proc.new { |volume| puts “Volume was set to #{volume}.” }
185
+ mpd.on :volume, &proc
186
+
187
+ # Using a method
188
+ def volume_change(value)
189
+ puts “Volume changed to #{value}.”
190
+ end
191
+
192
+ handler = method(:volume_change)
193
+ mpd.on :volume, &handler
194
+ ```
195
+
196
+ ruby-mpd supports callbacks for any of the keys returned by `MPD#status`, as well as `:connection`. Here's the full list of events, along with the variables it will return:
197
+
198
+ * *volume*: The volume level as an Integer between 0-100.
199
+ * *repeat*: true or false
200
+ * *random*: true or false
201
+ * *single*: true or false
202
+ * *consume*: true or false
203
+ * *playlist*: 31-bit unsigned Integer, the playlist version number.
204
+ * *playlistlength*: Integer, the length of the playlist
205
+ * *state*: `:play`, `:stop`, or `:pause`, state of the playback.
206
+ * *song*: An `MPD::Song` object, representing the current song.
207
+ * *songid*: playlist songid of the current song stopped on or playing.
208
+ * *nextsong*: playlist song number of the next song to be played.
209
+ * *nextsongid*: playlist songid of the next song to be played.
210
+ * *time*: Returns two variables, `total` and `elapsed`, Integers representing seconds.
211
+ * *elapsed*: Float, representing total time elapsed within the current song, but with higher accuracy.
212
+ * *bitrate*: instantaneous bitrate in kbps.
213
+ * *xfade*: crossfade in seconds
214
+ * *mixrampdb*: mixramp threshold in dB (Float)
215
+ * *mixrampdelay*: mixrampdelay in seconds
216
+ * *audio*: Returns three variables: sampleRate, bits and channels.
217
+ * *updating_db*: job id
218
+ * *error*: if there is an error, returns message here
219
+
220
+ * *connection*: Are we connected to the daemon? true or false
221
+
222
+ Note that if the callback returns more than one value, the callback needs more arguments in order to recieve those values:
223
+
224
+ ```ruby
225
+ mpd.on :audio do |sampleRate, bits, channels|
226
+ puts bits
227
+ end
228
+
229
+ # or
230
+ mpd.on :audio do |*args|
231
+ puts args.join(‘,’)
232
+ end
233
+ ```
234
+
235
+ Finally, the easiest step. In order for callbacks to work, create a MPD instance with callbacks enabled:
236
+
237
+ ```ruby
238
+ MPD.new ‘localhost’, 6600, { callbacks: true }
239
+ ```
240
+
241
+ Easy as pie. The above will connect to the server like normal, but this time it will create a new thread that loops until you issue a `disconnect`. This loop checks the server, then sleeps for two tenths of a second, then loops.
242
+
243
+ ## Not yet implemented
244
+
245
+ This section documents the features that are missing in this library at the moment.
246
+
247
+ ### Command lists
248
+
249
+ Command lists are not implemented yet. The proposed API would look like:
250
+
251
+ ```ruby
252
+ mpd.command_list do
253
+ volume 80
254
+ repeat true
255
+ status
256
+ end
257
+ ```
258
+
259
+ What makes me not so eager to implement this is that MPD returns all values one after another. This gets fixed with `command_list_ok_begin`, which returns `list_OK` for every command used, however then we still get more than one response, and I can't think of a reasonable way to retun all of them back to the user. Maybe just ignore the return values?
260
+
261
+ ### Idle
262
+
263
+ To implement idle, what is needed is a lock that prevents sending commands to the daemon while waiting for the response (except `noidle`). An intermediate solution would be to queue the commands to send them later, when idle has returned the response.
264
+
265
+ Idle seems like a possible way to reimplement callbacks; make a separate connection and just use idle and when it returns, simply use idle again and again.
266
+
267
+ ### Tests
268
+
269
+ Tests fail at the moment, as they are 6 years old. The entire MPD server mock class either needs to be rewritten, or a `mpd.conf` along with a sample database and instructions for a controlled environment needs to be written.
270
+
271
+ ## TODO list
272
+
273
+ * `MPD::Song`, `MPD::Directory`.
274
+ * Make stickers a mixin for `Playlist`, `Song`, `Directory`…
275
+ * Namespace queue
276
+ * Merge `where` and `queue_where`, by doing `where(..., { in_queue: true})`?