On Mon, Aug 4, 2008 at 8:53 PM, martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Thibaut VARENE <[EMAIL PROTECTED]> [2008.08.04.1537 -0300]: >> The module doesn't use (yet) any kind of database, so it is impossible >> to do any other grouping/ordering than the one existing on the >> filesystem of your computer (ie: the module cannot reorder files in a >> different way than the way they are stored on your computer) > > I think what he means is that the left column should show top-level > directories, and the right column shows second-level directories for > each, such as: > > David Bowie Heroes > Young Americans > Scary Monsters > The Beatles Help > Sgt. Peppers > Yellow Submarine
This assumes a very specific directory structure, "a la iTunes": Root / Artist / Album This is an assumption I'm not willing to make, not everyone organizes their music this way, and I want the module to be as generic as possible > This would be doable without a database and could be formatted with > CSS. It would even be compatible with the current column count > setting, so in the above, I'd simply have > > MusicDirPerLine 1 > RecurseFolderLevels 1 > > I second this; it would be a very nice addition to the web > interface. I see 2 problems with this: 1) recursion in Apache is extremely expensive: it's already a major burden to the module to just display the icons right below directory names in the directory listing (try building with --disable-pretty folders and enjoy an at least 30x performance improvement) 2) For an even reasonable amount of folders, unlimited recursion as suggested could yields table with thousands of elements, which would be i) difficult to read and ii) probably long (time-wise) to render by the browser (not mentioning its memory usage) I don't really like this idea very much. -- Thibaut VARENE http://www.parisc-linux.org/~varenet/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
