Sunday, December 16. 2007Mockup for Ampache config
Just as a small aside, a sort of response to Nikolaj's latest entry, he and i have already discussed the usability problems in the Ampache configuration dialog, and the suggested solution was the mockup you can find below. The problem is, of course, as it is in so many of these occurrences that this particular type of dialogue requires more work than the current implementation. Since the current one exists and so much other work needs doing to get Amarok 2 ready, we decided to postpone this work until later on. However, it would not be fair on you guys that we should keep this to ourselves, so here you go, our idea of what a configuration page for Ampache might look like:
 Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
Just wanna say, beautiful GUI. So is Amarok not going to be a KDE app anymore?
Of course not, it's going to be based on Crayon Physics in version 4.0!
No, this is actually according to the KDE HIG which is under development - editing of list configuration should happen inside the list itself whenever possible 
Hmm, this looks kind of nice but the only thing I thought looks a bit out of sorts/ didn't know what it was for was the checkbox on the left -- is this an for an indication that it's being used at the moment or just that it's the selected item?
Also, with the multiple-select box, there should be a default height set for the dialog, because it might end up like the "cool new stuff" where the size of the listbox resizes from like 0 to full width whilst the contents populate. Looks cool though, and I think it'd also work well for something like -- say if Amarok supported more than one of the music-blogging API's for example (even though last.fm is by far the best) then yeah that'd be rad!
The check-box is to show which item is/items are currently active. You can only select one item, and one item will always be selected. This ensures that the list-view's height is always the same, and that item positions are the same as well (i.e. muscle memory is retained). i do hope that we can abstract this out enough that it'll be possible to use the method for other things as well, so... yeah
Hmm, sounds good. But, with the list of items which are enabled / are connecting, are those going to be collapsible as well?
i'm not entirely sure what you mean - only one item will ever be expanded, and one item will always be expanded, namely the selected item.
|
Amarok LinksCalendarQuicksearchCategoriesSyndicate This BlogBlog AdministrationWe Listen To... Powered by
|
