chiark / gitweb /
CHANGES -> CHANGES.html
[disorder] / CHANGES.html
CommitLineData
b0a578cb
RK
1<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML//EN">
2<html>
3<head>
4<title>DisOrder Change History</title>
5<style type="text/css">
6body {
7 color: black;
8 background-color: white;
9 font-family: times,serif;
10 font-weight: normal;
11 font-size: 12pt;
12 font-variant: normal
13}
14
15div.section {
16 margin-left:1em
17}
18
19h1 {
20 background-color: #e0ffe0;
21 font-family: helvetica,sans-serif;
22 padding: 0.2em
23}
24
25h2 {
26 background-color: #e0ffe0;
27 font-family: helvetica,sans-serif;
28 padding: 0.2em
29}
30
31h3 {
32 background-color: #f0f0f0;
33 font-family: helvetica,sans-serif;
34 padding: 0.2em
35}
36
37h4 {
38 font-family: helvetica,sans-serif
39}
40
41table.bugs {
42 width: 100%
43}
44
45table.bugs th {
46 text-align: left
47}
48
49span.command {
50 font-family: monospace
51}
52</style>
53</head>
54
55<body>
56<h1>DisOrder Change History</h1>
57
58<p>This file documents recent user-visible changes to DisOrder.</p>
59
60<h2>Changes up to version 3.1</h2>
61
62<div class=section>
63
64 <h3>Server</h3>
65
66<div class=section>
67
68 <p>The <tt>gap</tt> directive will no longer work. It could be
69 restored if there is real demand.</p>
70
71 <h4>Event Scheduling</h4>
72
73<div class=section>
74
75 <p>It is now possible to schedule events to occur in the future.
76 Currently the supported actions are playing a specific track, and
77 changing a global preference (thus allowing e.g. random play to be
78 turned on or off). See the <tt>schedule-*</tt>
79 commands described in disorder(1).</p>
80
81</div>
82
83<h4>Random Track Choice</h4>
84
85<div class=section>
86
87 <p>This has been completely rewritten to support new features:</p>
88
89 <ul>
90
91 <li>tracks in the recently-played list or in the queue are no longer
92 eligible for random choice.</li>
93
94 <li>there is a new <tt>weight</tt> track preference allowing for
95 non-uniform track selection. See disorder(1) for details.</li>
96
97 <li>there is a new configuration item <tt>replay_min</tt> defining
98 the minimum time before a played track can be picked at random.
99 The default is 8 hours (which matches the earlier behaviour).</li>
100
101 <li>recently added tracks are biased up; see <tt>new_bias</tt> and
102 <tt>new_bias_age</tt> in disorder_config(5).</li>
103
104 </ul>
105
106</div>
107
108<h4>Web Interface</h4>
109
110<div class=section>
111
112 <p>This has been largely rewritten. The most immediate benefits are:</p>
113
114 <ul>
115
116 <li>the search page is integrated into the choose page, and
117 includes links to parent directories.</li>
118
119 <li>if you try to do something you have insufficient rights for,
120 instead of getting an error page or nothing happening, you are
121 redirected to the login page.</li>
122
123 </ul>
124
125 <p>Customizers should find their lives easier: the syntax is less onerous, it
126 is possible to define macros to avoid repetition, and the documentation is
127 less monolithic (see disorder.cgi(8) as a starting point).</p>
128
129</div>
130
131</div>
132
133<h3>Disobedience</h3>
134
135<div class=section>
136
137 <p>There is now a new user management window. From here you can add and
138 remove users or modify their settings.</p>
139
140 <p>Relatedly, the server will only allow remote user management if you set
141 <tt>remote_userman</tt> to <tt>yes</tt>.</p>
142
143</div>
144
145<h3>Miscellaneous</h3>
146
147<div class=section>
148
149 <p><tt>scripts/setup</tt> now honors command line options, and can
150 set up network play as well as the local default sound device.</p>
151
152</div>
153
154<h3>Bugs Fixed</h3>
155
156<div class=section>
157
158 <table class=bugs>
159 <tr>
160 <th>ID</th>
161 <th>Description</th>
162 </tr>
163
164 <tr>
165 <td><a href="http://code.google.com/p/disorder/issues/detail?id=2">#2</a></td>
166 <td>Search results should link to directories</td>
167 </tr>
168
169 <tr>
170 <td><a href="http://code.google.com/p/disorder/issues/detail?id=6">#6</a></td>
171 <td>Schedule tracks for a particular time</td>
172 </tr>
173
174 <tr>
175 <td><a href="http://code.google.com/p/disorder/issues/detail?id=10">#10</a></td>
176 <td>Non-uniform track selection</td>
177 </tr>
178
179 <tr>
180 <td><a href="http://code.google.com/p/disorder/issues/detail?id=11">#11</a></td>
181 <td>Bias random selection to newly added tracks</td>
182 </tr>
183
184 <tr>
185 <td><a href="http://code.google.com/p/disorder/issues/detail?id=13">#13</a></td>
186 <td>Default encoding for debian setup scripts</td>
187 </tr>
188
189 <tr>
190 <td><a href="http://code.google.com/p/disorder/issues/detail?id=16">#16</a></td>
191 <td>Cookie expiry causes user to be silently logged out and not
192 subsequently redirected to login page</td>
193 </tr>
194
195 <tr>
196 <td><a href="http://code.google.com/p/disorder/issues/detail?id=20">#20</a></td>
197 <td>Broken aliasing rules</td>
198 </tr>
199
200 </table>
201
202</div>
203
204</div>
205
206<h2>Changes up to version 3.0.2</h2>
207
208<div class=section>
209
210 <p>Builds <tt>--without-server</tt> should work again.</p>
211
212 <p>The web interface is a bit more liberal in the cookie value
213 syntax it will accept.</p>
214
215 <p>Clients fail more gracefully if no password is available.</p>
216
217</div>
218
219<h2>Changes up to version 3.0.1</h2>
220
221<div class=section>
222
223 <p>Debian upgrades from 2.0.x should now work better.</p>
224
225</div>
226
227<h2>Changes up to version 3.0</h2>
228
229<div class=section>
230
231 <p><b>Important</b>! See <a
232 href="README.upgrades">README.upgrades</a> when upgrading.</p>
233
234 <h3>Platforms And Installation</h3>
235
236<div class=section>
237
238 <p>Mac OS X and FreeBSD are somewhat supported. There is now a bash
239 script in <tt>scripts/setup</tt> which will automate the setup after
240 <tt>make install</tt>.</p>
241
242</div>
243
244<h3>Server</h3>
245
246<div class=section>
247
248 <p>Users are now stored in the database rather than a configuration
249 file.</p>
250
251 <p>The server now has a built-in list of stopwords and players, so
252 only additions to these need be mentioned in the configuration file.</p>
253
254 <p>The default inter-track gap is now 0s.</p>
255
256 <p>How sound is played is now controlled via the new <tt>api</tt>
257 configuration command. This also controls how the volume is set,
258 which now works with ALSA as well as OSS.</p>
259
260 <p>A bug in the MP3 decoder was fixed (also in 2.0.4).</p>
261
262</div>
263
264<h3>Web Interface</h3>
265
266<div class=section>
267
268 <p>The web interface now uses cookies to remember user identity, and
269 allows online registration of new users. Also it is no longer
270 necessary to manually specify the URL of the web interface (but you
271 can override it if you don't like the value it figures out).</p>
272
273 <p>It is possible to allow users to register via the web interface.</p>
274
275 <p>The web interface's browser support has been improved. It has
276 been tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer
277 7 and Opera 9.</p>
278
279</div>
280
281<h3>Disobedience</h3>
282
283<div class=section>
284
285 <p>A bug which would cause a crash if you attempt to rearrange the
286 queue while no track was playing has been fixed. There is a new
287 'deselect all tracks' option, mirroring 'select all tracks.</p>
288
289</div>
290
291</div>
292
293<!--
294Local Variables:
295fill-column:79
296End:
297-->