Small request: currently the page refreshes automatically when a song is over and playback jumps to the next item. Fine. However it doesn't refresh if the user changes the playing song using the foobar interface.Could the plugin send a refresh request each time someone changes the played item (let's say after a 5 seconds delay so the browser doesn't become crazy if I hit "Random" repeatedly)?
What about an element within the webpage code wich would regularly check if the playing song has changed?
Another suggestion: could we set the default behaviour of the "playlist action"? I would like it to be set on "Focus" by default and to stay that way when I click on an item (currently it switches back to "Start" everytime).
act = [LAST_ACTION];
act = 3;
v0.70 17 May 2008 fix: failed reading template files when foobar path contained non-ascii characters; add: default playlist action reverts to 'Start' after any non-playlist related action; add: display of playback queue length; add: restrictive list of directories allowed to browse;
A small feature request: I'd like to be able to show only files with extensions that foobar2000 supports. Right now I'm just hiding unsupported file types via CSS, but that only fools the average Joe as the file names are still visible in the HTML source.
what exactly for do you need this, may I ask? it's just that this thing is intended for personal use where seeing non playable files in list means no harm, I think.
I'm not motivated and/or interested in going this way. I suppose the better, reliable and much faster way of achieving desired functionality would be a combination of apache, php and foobar COM automation server plugin.
Quote from: oblikoamorale on 17 May, 2008, 07:28:35 AMwhat exactly for do you need this, may I ask? it's just that this thing is intended for personal use where seeing non playable files in list means no harm, I think.In the distant past people had to bring their CDs to parties. In the not so distant past they brought their external hard drives. But now they can can access all their music without bringing anything. I use this plugin in combination with the Icecast server and set foobar2000 to null output and thereby have a remote music jukebox. Though I use password protection I want to leave access open to the "public" after the authentication. But people should do nothing more then to browse my music files. They should definitely not be able to see all my hard drives' contents. And there are music files scattered all over three different drives, so I cannot just restrict access to some folders, or the list of allowed folders would be really long.
<select title="Volume level" onchange="pc('Volume',this.value);">[VOLUME_OPTION]</select>%
<select title="Volume Up" onchange="pc('Volume',this.value);">[VOLUME_OPTION]</select>% <select title="Volume Down" onchange="pc('Volume',this.value);">[VOLUME_OPTION]</select>%
Hancoque: I've reuploaded current version with non playable files filter.
This is a very cool component. Thank you very much for making it.Question 1. I can't see the volume up/down control you added in 0.69. (Firefox 18.104.22.168). How do I add it?
<input name="VolumeUp" type="button" value="V_Up" onClick="pc(this.name, 20);"><input name="VolumeDown" type="button" value="V_Down" onClick="pc(this.name, 20);">
Question 2. Could the htm template be skinned using Flash?
v0.71 21 May 2008 add: multithreaded (restricted up to four simultaneous sessions) mini-web-server, able to serve any files from home directory. the following mime types are supported: css, gif, htm, html, ico, jpg, jpe, jpeg, js, png, xml. add: optional logging of remote ip addresses in console;
document.getElementById('np').style.width=Math.floor(np_width * t_sec / t_length)+"px";
I'm trying to rewrite the HTML templates to the XHTML 1.1 specification using valid code, but there's one thing I cannot fix in the template: The plugin dynamically inserts checked (for checkboxes) and selected (for drop-down menu options) into the code. XHTML disallows this. Instead checked="checked" and selected="selected" has to be used to produce valid code. What speaks against using XHTML for the templates in general?
2. The form element must not contain the attributes name and target. Remove the latter altogether and replace the former by id and use document.getElementById('cmd_form') instead of document.cmd_form.3. The CSS styles width, height and left need to have units specified (like px), otherwise they are not applied if the document is treated as XHTML.
The server sends a charset called utf8. I think it has to be utf-8 instead. The XHTML validator complains that there's a charset mismatch.