Hi Dag,
On 11.05.05, Dag Wieers wrote:
On Wed, 11 May 2005, Joerg Lehmann wrote:
On 10.05.05, Dag Wieers wrote:
I've got a few comments/requests as a user :)
- Is there some way to have the 'cursor' move with the current playing track ? (ie when it changes song, look if the cursor was highlighting the previous song and move it to the next song) This way the info-window displays the current song at all times, if once selected.
No, this does not currently work and actually I don't like this idea too much. Suppose you were editing the playlist and then a new song comes and all of a sudden the cursor moves.
Fair enough. Still when you're not editing (which is what I'm doing more than 99% of the time), the info window is useless as it shows the cursor position while I'm more interested to see the information of the currently playing song. Maybe there's some more clever way to achieve the same thing.
Actually, one could make the contents of the info window switchable between the currently selected item, the song currently being played on the first player, and (if configured) the same info for the second player.
- Can I support multiple music directories and/or temporary music directories (like USB storage or CD/DVDs) ? What I would like is to be able to specify multiple locations and have pytone manage each of these. And when a location suddenly gets unmounted/remounted, have it act upon that.
PyTone supports more than one music directory (just add multiple [database.*] sections in the config file). But this support is currently static in the sense that you cannot add/remove databases when PyTone is running. However, you can at any time request a rescanning of the database by selecting the database and pressing 'u'.
Interesting, I must say the default config file is a bit overwhelming because of the sheer volume of comments :) I wonder if we can trim it a bit.
I know, but the idea was to use this a form of documentation. But certainly, one could do this better.
I've trimmed mine a bit (the first few sections) and attached it for review. It gets rid of some of the redundancy, is a bit more consistent.
I like it.
What I would like to change (still) is to provide different sections that work by themselves (instead of giving alternatives inside the same section). It's easier if you can go over the self-explained examples.
If you could do that, I would really appreciate the help.
Also I would prepend comments with a triple hash, so that you can comment out configuration options with a single hash. Makes it more readable and easier to skim for something.
Looks nicer and is more practicable.
- I would also prefer to rename /etc/pytonerc into /etc/pytone.conf and
have a per user configuration file in ~/.pytone/pytone.conf that either overrides the default or extends the default.
Ok, the pytonerc name comes from vimrc :) But rc vs .conf doesn't matter too much, does it? Concerning the system wide and user configuration: that's exactly how it works currently: /etc/pytonerc stores the system-wide configuration which can be overridden by the user in ~/.pytone/pytonerc.
Jörg