chiark / gitweb /
CHANGES -> CHANGES.html in debian scripts too
[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
2eee4b0c
RK
129 <p>Mail is now sent via the system sendmail program, though it remains
130 possible to use TCP to connect to an SMTP server. See <tt>sendmail</tt> and
131 <tt>smtp_server</tt> in disorder_config(5).</p>
132
b0a578cb
RK
133</div>
134
135</div>
136
137<h3>Disobedience</h3>
138
139<div class=section>
140
141 <p>There is now a new user management window. From here you can add and
142 remove users or modify their settings.</p>
143
144 <p>Relatedly, the server will only allow remote user management if you set
145 <tt>remote_userman</tt> to <tt>yes</tt>.</p>
146
147</div>
148
149<h3>Miscellaneous</h3>
150
151<div class=section>
152
153 <p><tt>scripts/setup</tt> now honors command line options, and can
154 set up network play as well as the local default sound device.</p>
155
156</div>
157
158<h3>Bugs Fixed</h3>
159
160<div class=section>
161
162 <table class=bugs>
163 <tr>
164 <th>ID</th>
165 <th>Description</th>
166 </tr>
167
168 <tr>
169 <td><a href="http://code.google.com/p/disorder/issues/detail?id=2">#2</a></td>
170 <td>Search results should link to directories</td>
171 </tr>
172
173 <tr>
174 <td><a href="http://code.google.com/p/disorder/issues/detail?id=6">#6</a></td>
175 <td>Schedule tracks for a particular time</td>
176 </tr>
177
178 <tr>
179 <td><a href="http://code.google.com/p/disorder/issues/detail?id=10">#10</a></td>
180 <td>Non-uniform track selection</td>
181 </tr>
182
183 <tr>
184 <td><a href="http://code.google.com/p/disorder/issues/detail?id=11">#11</a></td>
185 <td>Bias random selection to newly added tracks</td>
186 </tr>
187
188 <tr>
189 <td><a href="http://code.google.com/p/disorder/issues/detail?id=13">#13</a></td>
190 <td>Default encoding for debian setup scripts</td>
191 </tr>
192
193 <tr>
194 <td><a href="http://code.google.com/p/disorder/issues/detail?id=16">#16</a></td>
195 <td>Cookie expiry causes user to be silently logged out and not
196 subsequently redirected to login page</td>
197 </tr>
198
199 <tr>
200 <td><a href="http://code.google.com/p/disorder/issues/detail?id=20">#20</a></td>
201 <td>Broken aliasing rules</td>
202 </tr>
203
204 </table>
205
206</div>
207
208</div>
209
210<h2>Changes up to version 3.0.2</h2>
211
212<div class=section>
213
214 <p>Builds <tt>--without-server</tt> should work again.</p>
215
216 <p>The web interface is a bit more liberal in the cookie value
217 syntax it will accept.</p>
218
219 <p>Clients fail more gracefully if no password is available.</p>
220
221</div>
222
223<h2>Changes up to version 3.0.1</h2>
224
225<div class=section>
226
227 <p>Debian upgrades from 2.0.x should now work better.</p>
228
229</div>
230
231<h2>Changes up to version 3.0</h2>
232
233<div class=section>
234
235 <p><b>Important</b>! See <a
236 href="README.upgrades">README.upgrades</a> when upgrading.</p>
237
238 <h3>Platforms And Installation</h3>
239
240<div class=section>
241
242 <p>Mac OS X and FreeBSD are somewhat supported. There is now a bash
243 script in <tt>scripts/setup</tt> which will automate the setup after
244 <tt>make install</tt>.</p>
245
246</div>
247
248<h3>Server</h3>
249
250<div class=section>
251
252 <p>Users are now stored in the database rather than a configuration
253 file.</p>
254
255 <p>The server now has a built-in list of stopwords and players, so
256 only additions to these need be mentioned in the configuration file.</p>
257
258 <p>The default inter-track gap is now 0s.</p>
259
260 <p>How sound is played is now controlled via the new <tt>api</tt>
261 configuration command. This also controls how the volume is set,
262 which now works with ALSA as well as OSS.</p>
263
264 <p>A bug in the MP3 decoder was fixed (also in 2.0.4).</p>
265
266</div>
267
268<h3>Web Interface</h3>
269
270<div class=section>
271
272 <p>The web interface now uses cookies to remember user identity, and
273 allows online registration of new users. Also it is no longer
274 necessary to manually specify the URL of the web interface (but you
275 can override it if you don't like the value it figures out).</p>
276
277 <p>It is possible to allow users to register via the web interface.</p>
278
279 <p>The web interface's browser support has been improved. It has
280 been tested with Firefox 2, Safari 3, Konqueror 3, Internet Explorer
281 7 and Opera 9.</p>
282
283</div>
284
285<h3>Disobedience</h3>
286
287<div class=section>
288
289 <p>A bug which would cause a crash if you attempt to rearrange the
290 queue while no track was playing has been fixed. There is a new
291 'deselect all tracks' option, mirroring 'select all tracks.</p>
292
293</div>
294
295</div>
296
297<!--
298Local Variables:
299fill-column:79
300End:
301-->