PDA

View Full Version : Fishbone Interface change suggestion



Robin Bowes
2005-09-25, 12:33
Hi,

I'd like to suggest a change to the interface used by the Fishbone skin.

Instead of each track having it's own "Next", "Play", "Add" and "Remove"
icons, I think it would be a cleaner and more functional interface if
there were a checkbox against each line and a single drop-down list and
button at the top/bottom of the list containing "Next", "Play", etc.

Does that make sense?

If it does, what do you think? Good idea?

This would clean up the interface, i.e. it would look less clutter. It
would also allow for adding, say, 4 out of 8 tracks to the playlist
(e.g. playing one symphony from two on a disk).

Comments? Code :)

R.
--
http://robinbowes.com

If a man speaks in a forest,
and his wife's not there,
is he still wrong?

kdf
2005-09-25, 14:57
as long as you do not call it the fishbone skin,( so that I'm not
expected to provide support for it), then I am 100% behind your right
to steal any and all code you need, making any changes you want to
create your own skin. At one time, there were quite a number of people
making custom skins and posting them (some just slight variations on a
core, some more radical). Unfortunately, they seemed to lose interest
in keeping them up-to-date and they eventually disappeared. it would be
great to see more websites with skin choices out and about.

While I'm not personally a big fan of a page full of checkboxes and
pulldowns, my curiosity is very much engaged to see if anyone can do it
with javascript alone.

-kdf

Robin Bowes
2005-09-25, 16:01
kdf said the following on 25/09/2005 22:57:
> as long as you do not call it the fishbone skin,( so that I'm not
> expected to provide support for it), then I am 100% behind your right to
> steal any and all code you need, making any changes you want to create
> your own skin. At one time, there were quite a number of people making
> custom skins and posting them (some just slight variations on a core,
> some more radical). Unfortunately, they seemed to lose interest in
> keeping them up-to-date and they eventually disappeared. it would be
> great to see more websites with skin choices out and about.
>
> While I'm not personally a big fan of a page full of checkboxes and
> pulldowns, my curiosity is very much engaged to see if anyone can do it
> with javascript alone.

This is used in phpMyAdmin:

function setCheckboxes(the_form, do_check)
{
var elts =
(typeof(document.forms[the_form].elements['selected_db[]']) != 'undefined')
? document.forms[the_form].elements['selected_db[]']
:
(typeof(document.forms[the_form].elements['selected_tbl[]']) != 'undefined')
? document.forms[the_form].elements['selected_tbl[]']
: document.forms[the_form].elements['selected_fld[]'];
var elts_cnt = (typeof(elts.length) != 'undefined')
? elts.length
: 0;

if (elts_cnt) {
for (var i = 0; i < elts_cnt; i++) {
elts[i].checked = do_check;
} // end for
} else {
elts.checked = do_check;
} // end if... else

return true;
} // end of the 'setCheckboxes()' function


However, I'm really out of my depth here - I'm no UI guru.

R.
--
http://robinbowes.com

If a man speaks in a forest,
and his wife's not there,
is he still wrong?

JJZolx
2005-09-25, 16:30
Hi,

I'd like to suggest a change to the interface used by the Fishbone skin.

Instead of each track having it's own "Next", "Play", "Add" and "Remove"
icons, I think it would be a cleaner and more functional interface if
there were a checkbox against each line and a single drop-down list and
button at the top/bottom of the list containing "Next", "Play", etc.

Does that make sense?

If it does, what do you think? Good idea?

This would clean up the interface, i.e. it would look less clutter. It
would also allow for adding, say, 4 out of 8 tracks to the playlist
(e.g. playing one symphony from two on a disk).

Comments? Code :)
The biggest usability issue I see is that you have no control of the track ordering in the playlist when you add multiple tracks at once (unless your JavaScript can keep track of the order in which you click the checkboxes, which isn't really intuitive with the way most web forms behave).

Another is that it ends up requiring three times as many clicks to add just one track from an album.

As KDF alludes, there might not even be the ability to add multiple tracks. This is more an issue at the reciveing end of the form submit, so doing it in JavaScript might be a real trick, if even possible.

One way to clean up the interface (if you don't like looking at all of the controls) that is probably compatible with the current method, would be to use mouseovers to display the individual next/play/add controls.

kdf
2005-09-25, 22:14
On 25-Sep-05, at 4:01 PM, Robin Bowes wrote:
>
> However, I'm really out of my depth here - I'm no UI guru.
>
out of mine too, which is why I've always avoided it :)
maybe checkboxes could be avoided if a series of onclick events could
add items to a listref, highlighting the items along the way. the
server can take a list for a play command.
-k

Jacob Potter
2005-09-26, 18:34
On 9/26/05, kdf <slim-mail (AT) deane-freeman (DOT) com> wrote:
> out of mine too, which is why I've always avoided it :)
> maybe checkboxes could be avoided if a series of onclick events could
> add items to a listref, highlighting the items along the way. the
> server can take a list for a play command.

I'm looking at this from a DHTML point of view :)

On the server side, I have an addition to RPC.pm that'll take an
arbitrary array of song search hashes, like so:
[
{ genre : 2, artist : 7 },
{ genre : 2, artist : 3 },
{ album : 31 },
15 // equivalent to { id : 15 }
]

Each of the hashes is passed straight to $ds->find(), and the
resultant list of songs is loaded/added/deleted from/inserted to the
playlist. I don't yet have a way to generate those hashes on the
client, as Pages.pm only provides the attributes list in URL-encoding.
Shouldn't be too hard to parse them out though.

However, I'm no good at UI design either. It'd be nice if someone
could come up with a mock-up of how it should look...

- Jacob