RonaldPR wrote:I like the existing lay-out better, especially for classical music, with enough room to display the full information:
(I use UNO, hence the unified grey appearance.)
That one will be perfect, just, instead of Play icon, my album cover appears (ex. looking in the folder for cover.*, poster.* or whatever)
Also the idea with the "Mini mode" would be great!
That was an old discussion based on the old interface. The interface has been changed since, now with controls in he window toolbar. See Play 0.3 or more recent unstable builds.
Joe wrote:I don't know anything about coding but I'd love to have a UI like Exaile or Rhythmbox.
I don't know Exaile, but Rhythmbox is self-consciously intended as an "iTunes clone". Of course, Rhythmbox only clones a subset of iTunes's functionality -- there's so much of it, isn't there? -- but some of that functionality is there and Rhythmbox looks (somewhat) like its model ... only not so polished.
I take it Play is trying to fill a niche in terms of what it does not trying to look unique. Still, so far as looks go, is there much point in copying a copy of something else that's already available to anyone who's running OS X?
I understand that Rhythmbox is intended as an iTunes clone but the "iTunes style" interface improves usability IMO so I don't see any problem with making it more similar. The reason I like Play right now is because it supports ReplayGain and MusicBrainz tagging so I believe that Play has enough differentiating features to separate it from iTunes. Right now I think the way playlist/library setup can be a bit confusing since the panes look identical to each other.
So far in this thread, I have seen little discussion of the reasons for specific UI choices. As I see it, the mockups here show two prioritizations and two types of layout:
Prioritizations
Horizontal Space
(for long titles, esp. for classical music, a key audience for FLAC)
Vertical Space
(to see as many songs as possible onscreen)
Layouts
Horizontal Layout
This maximizes horizontal space for long titles (and for fine control of the seek bar) by stretching visual elements horizontally and arraying controls along a single wide line.
Vertical Layout
This increases vertical space by horizontally compressing titles and the seek bar, and by placing controls into a second column on the side of the title / track / artist display.
Pros and Cons
Horizontal Layout Pros:
Allows long titles / text, as well as fine control of seek bar. Cons:
Can consume vertical space. For users with wide screens and/or few long classical titles, a lot of empty horizontal space may feel wasted or even disorienting. It is difficult to click controls arrayed in a long, thin line. Mousing in a straight horizontal line and stopping accurately at the right spot is relatively difficult for humans.
Vertical Layout Pros: "Clustering" controls (volume, seek, FF/Rew/Play/Skip) in a two dimensional grid is more ergonomic than a straight, thin line. It also allows a better spatial-conceptual map in human memory than a linear map.
A few additional songs may be displayed in the playlist / library without scrolling.
Does not "waste" as much horizontal space on wide displays. Cons:
Reduces horizontal space for long text and precise seeking.
May not allow enough space for text if window is sized too narrowly.
In conclusion, I think that there are compelling reasons to provide both types of layouts.
One idea I have thrown around is having the UI be WebKit based, using customized themes (based on CSS) allowing essentially unlimited layout options that anyone could create. The problem is making something like that a first-class application, because CSS/DOM/Javascript do not present the same capabilities as Cocoa.