dean blackketter
2002-02-23 14:43:35 UTC
For this particular feature, though, the PIP button might be
appropriate.
...
Now Playing (n of m) + Remaining time
Now Playing (n of m) + Progress bar + Remaining Time
I've added these.appropriate.
...
Now Playing (n of m) + Remaining time
Now Playing (n of m) + Progress bar + Remaining Time
1. It might be hard to distinguish remaining time from elapsed time
quickly, but if you wait a second, it becomes obvious. It might be
hard to flip through the choices and pick the right one.
To distinguish between elapsed and remaining, I've added a - beforequickly, but if you wait a second, it becomes obvious. It might be
hard to flip through the choices and pick the right one.
the remaining time, in imitation of my Sony CD player.
2. This is probably the limit of the number of views we can have for
this button. Otherwise it becomes tedious to find the one you want.
Yeah. My original motivation for not wanting to put these on the PIPthis button. Otherwise it becomes tedious to find the one you want.
button was that I wanted four time modes (Track Elapsed, Track
Remaining, Playlist Elapsed, Playlist Remaining), and that seemed too
many combinations to page through.
we need more combinations.
If you want to take a crack at adding this to the PIP button (check
out lib/SliMP3/Buttons/Playlist.pm) and submit another patch, that
would be great. It would be particularly great if the settings page
for the client had a pop-up menu that allowed the user to select
between all six combinations.
Done. Attached is a new patch is against the CVS sources, not againstout lib/SliMP3/Buttons/Playlist.pm) and submit another patch, that
would be great. It would be particularly great if the settings page
for the client had a pop-up menu that allowed the user to select
between all six combinations.
the CVS sources + my previous patch.
The second problem is more systemic then anything specific to your diff. I
haven't brought this up before, but I think that we need to establish some
kind of naming convention for the strings in strings.txt. Not because I
disagree with what you put in there, though.
Whenever a client or server setting is changed we display some kind of
message as a confirmation. We also display a message if the value was
1) if we have a naming convention like SETUP_parametername and/or
SETUP_REJECT_parametername, we can put the display in setup_evaluation and
do it automatically (provided the string gets added to strings.txt)
2) we can add to the setup hash the string names to use and do it
automatically in setup_evaluation
3) for each parameter in the setup we can add a if exists $changed and an
if exists $rejected block and do the string display there
My preference would be naming convention.
I'll defer on this to people with more experience with this way ofhaven't brought this up before, but I think that we need to establish some
kind of naming convention for the strings in strings.txt. Not because I
disagree with what you put in there, though.
Whenever a client or server setting is changed we display some kind of
message as a confirmation. We also display a message if the value was
1) if we have a naming convention like SETUP_parametername and/or
SETUP_REJECT_parametername, we can put the display in setup_evaluation and
do it automatically (provided the string gets added to strings.txt)
2) we can add to the setup hash the string names to use and do it
automatically in setup_evaluation
3) for each parameter in the setup we can add a if exists $changed and an
if exists $rejected block and do the string display there
My preference would be naming convention.
handling web input.
-dean
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Sponsored by VeriSign - The Value of Trust
Secure all your Web servers now - with a proven 5-part
strategy. The FREE Server Security Guide shows you how.
http://us.click.yahoo.com/iWSNbC/VdiDAA/yigFAA/rIp0lB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
slimp3-dev-unsubscribe-***@public.gmane.org
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/