Wednesday, May 20. 2009
Amarok Dockwidgets - The Followup
Yesterdays blog entry about a prototype QDockWidget based Amarok 2 interface got a nearly overwhelming amount of positive feedback. So let me start out by saying thank you to everyone who commented.
It did make us think about some things though. Since the vast majority of comments would very much like to see this feature included in Amarok, you guys must have some kind of idea what you would actually use this flexibility for, and what kind of layout you want to create. So today we are going to try to do a little experiment based on all this feedback.
What we would greatly appreciate is if you would do a small simple mockup of what kind of layout you think you would create using this feature and post it to imagebin.ca or somewhere similar and then link it in the comments below, if possible with a very short description text. We are not talking about spending hours in the Gimp making a pretty picture, a simple pencil-on-the-back-of-a-napkin type sketch will do just fine. All it should show is how you would, based only on the possibilities show in the video, arrange the main interface elements, which ones would be placed where, hidden completely, or stacked together using tabs. A very important note is that this is not a free form chance to dream up an entirely new interface, but only about what you would change if this new feature became available. To keep things simple, please post each new mockup as a separate top level reply.
We know that the results of this will be quite biased, as what seems like a really good layout in theory might not work when you actually try it out in the real world. So ideally this experiment should really be done after this feature has made it into Amarok, but since there is currently no timeline for that, we are going to do this as best we can anyway!
The really interesting thing to see here is whether everyone has their own personal ideas about what would be a good interface layout, or if many of the suggestions gravitate towards something similar.
If we get enough feedback on this, we will follow up later with another blog post about the result and any lessons learned.
If any of you needs to revisit the video, here is the direct link.
It did make us think about some things though. Since the vast majority of comments would very much like to see this feature included in Amarok, you guys must have some kind of idea what you would actually use this flexibility for, and what kind of layout you want to create. So today we are going to try to do a little experiment based on all this feedback.
What we would greatly appreciate is if you would do a small simple mockup of what kind of layout you think you would create using this feature and post it to imagebin.ca or somewhere similar and then link it in the comments below, if possible with a very short description text. We are not talking about spending hours in the Gimp making a pretty picture, a simple pencil-on-the-back-of-a-napkin type sketch will do just fine. All it should show is how you would, based only on the possibilities show in the video, arrange the main interface elements, which ones would be placed where, hidden completely, or stacked together using tabs. A very important note is that this is not a free form chance to dream up an entirely new interface, but only about what you would change if this new feature became available. To keep things simple, please post each new mockup as a separate top level reply.
We know that the results of this will be quite biased, as what seems like a really good layout in theory might not work when you actually try it out in the real world. So ideally this experiment should really be done after this feature has made it into Amarok, but since there is currently no timeline for that, we are going to do this as best we can anyway!
The really interesting thing to see here is whether everyone has their own personal ideas about what would be a good interface layout, or if many of the suggestions gravitate towards something similar.
If we get enough feedback on this, we will follow up later with another blog post about the result and any lessons learned.
If any of you needs to revisit the video, here is the direct link.
Trackbacks
Trackback specific URI for this entry
No Trackbacks
Comments
Display comments as
(Linear | Threaded)
I'd simply switch context view and the playlist. Needs no drawing, does it?
No... I think that textual description is quite adequate for that case!
Hear hear! Alternatively how about allowing the user to remove the context view entirely, truthfully It's just dead space for me.
I really hope this is for which predefined layout which should be available, and that this lego-function is implemented anyway.
I'd like to put play/stop/pause buttons at the bottom (like 1.4). Something like this:
http://www.kde-look.org/content/preview.php?preview=2&id=93854&file1=93854-1.jpg&file2=93854-2.jpg&file3=93854-3.jpg&name=Amarok2+Look+and+Feel
And I'd like to be able to use a "reduced" layout with only minimal controls (play/stop/next), current track infos and analyzer... something like this:
http://www.kde-look.org/content/preview.php?preview=3&id=93854&file1=93854-1.jpg&file2=93854-2.jpg&file3=93854-3.jpg&name=Amarok2+Look+and+Feel
http://www.kde-look.org/content/preview.php?preview=2&id=93854&file1=93854-1.jpg&file2=93854-2.jpg&file3=93854-3.jpg&name=Amarok2+Look+and+Feel
And I'd like to be able to use a "reduced" layout with only minimal controls (play/stop/next), current track infos and analyzer... something like this:
http://www.kde-look.org/content/preview.php?preview=3&id=93854&file1=93854-1.jpg&file2=93854-2.jpg&file3=93854-3.jpg&name=Amarok2+Look+and+Feel
Sorry, but these things go beyond what is possible with the dock widgets, and what I was asking for was only what people would to with that specific functionality and not what you would like to see in general. So for the purpose of this little experiment, this answer is unfortunately invalid.
I actually think that these mockups go in the general direction of what we saw in the movie.
Having a dock for each of the controll bar, the collection, the context and the playlist. All of the variations of the mockups would then be possible. Even the simplistic mode would just be a matter of hiding the menu and status bars.
Having a dock for each of the controll bar, the collection, the context and the playlist. All of the variations of the mockups would then be possible. Even the simplistic mode would just be a matter of hiding the menu and status bars.
Well... I did not mean exactly like the mockups. For example at 1:15 you put the controls and the rest at the bottom. This for example would be an improvement to the way I use Amarok.
context in tab with browsers(ideally that all browsers were seperate horizontal tabs) and play controls at bottom(once again ideally under just playlist window)
i don't like that context'es lyrics and wiki are being refreshed on every song
i don't like that context'es lyrics and wiki are being refreshed on every song
Once thing is certain, i would place the controls at bottom.
I would like to be able to set the menu bars in KDE/QT applications to 'center horizontally'. I really don't want the tools at one of the screen edges, i wanted them centered. Sort of like windows media player or itunes i guess.
Imagine having the play button in the middle ^_^ that would please a lot of users i think.
I would like to be able to set the menu bars in KDE/QT applications to 'center horizontally'. I really don't want the tools at one of the screen edges, i wanted them centered. Sort of like windows media player or itunes i guess.
Imagine having the play button in the middle ^_^ that would please a lot of users i think.
This is also outside the scope of what was shown in the video to be possible.
My playlist tracks are four rows tall, and I seldom use the playlist for much more than looking at information about the current track. I also use the collection browser sparingly, although I do tweak my dynamic playlists a lot. I prefer to teach Amarok what I like to listen to, and simply skip the track if it chooses incorrectly, so my ideal layout would end up looking something like this:
http://drop.io/download/4a13c112/c53b83768ccee952da3019627e55bc913ab8db98/1e7efbc0-2747-012c-9b34-f74b8465e569/3c299910-2747-012c-ecbe-fa4548ed7466/v2/original_content
http://drop.io/download/4a13c112/c53b83768ccee952da3019627e55bc913ab8db98/1e7efbc0-2747-012c-9b34-f74b8465e569/3c299910-2747-012c-ecbe-fa4548ed7466/v2/original_content
interesting. This should actually be possible, and it is definitely not a setup I had thought about. It certainly gets the most of out the context view.
I took the liberty of converting this image as the link you posted does not work for many people. The mockup can be seen here: http://imagebin.ca/view/aZ8-Tc.html
Dock that center plasma view to the left so i could change between the left view and the plasma view. Usually I have all my favorites on the playlist so I don't need to see my collection at all the time. Having the default "three views" makes it look kind of messy.
+1 to this. And I'd also hide the play/stop/pause widget as well, because the buttons are just huge to look good enough for me
Yes, that is what I would do, too - the way I use amarok, I use both of them regularly, but almost never at the same time. I would then select the context view while playing music, mainly to see the lyrics, and when I re-fill my playlist I would select the collection-playlist-services view since the context view is not really necessary then (though the PUD is quite nice, I have to admit).
Me thinks, flexibility is a goal of FLOSS and especially KDE. So my suggestion is, implement this feature (*please*) and let users decide, what to do with it. Maybe users share favorites via kde-look or somewhere else..
obviously this is the most expected feature (together with the playlist-layout feature to be released with 2.1.0). Combined this could be a killer feature of amarok (flexibility!).
I think I would use several layouts over time...
just my 2¢
obviously this is the most expected feature (together with the playlist-layout feature to be released with 2.1.0). Combined this could be a killer feature of amarok (flexibility!).
I think I would use several layouts over time...
just my 2¢
It looks good I would use it to hide the plasma panel, or maybe stack it below the collection panel, as it takes much space and doesn't offer any important feature. I want most of the space to be given to the playlist, like in amarok 1.4.
I would use it to hide the plasma panel, or maybe stack it below the collection panel, as it takes much space and doesn't offer any important feature. I want most of the space to be given to the playlist, like in amarok 1.4.
Long-time 1.x user, and I agree. Put each element in it's own QDockWidget, each of which can be shown/hidden/resized/etc., and let users decide.
It's hard to say for sure how well this would work, considering there's currently no way to try, but if the feature would be in, I would first try one of these layouts:
http://imagebin.ca/view/1cAjuVeY.html
(kolourpaint ftw :p)
The major gripe I have with amarok (both 1.4 and 2.x), is how wide a window has to be to be really usable. On my second monitor, where I usually put stuff that is always there like amarok, it feels already a bit cramped, even when using the full 1024 pixels width. And preferably I won't have to maximize the window, keeping room for kopete for example. That's one of the reasons I really like the new playlist, it's not as insanely big as the amarok 1.4 one. this however get's compensated for by having the context view seperate from the collection/file browser. While I do very much like the context view to be always visible (the rest of the stuff I only use when I select some cd's to play, the context view I use quite regulary to check lyrics/wikipedia while listening to music. So that makes me think one of those mocks would work quite well.
http://imagebin.ca/view/1cAjuVeY.html
(kolourpaint ftw :p)
The major gripe I have with amarok (both 1.4 and 2.x), is how wide a window has to be to be really usable. On my second monitor, where I usually put stuff that is always there like amarok, it feels already a bit cramped, even when using the full 1024 pixels width. And preferably I won't have to maximize the window, keeping room for kopete for example. That's one of the reasons I really like the new playlist, it's not as insanely big as the amarok 1.4 one. this however get's compensated for by having the context view seperate from the collection/file browser. While I do very much like the context view to be always visible (the rest of the stuff I only use when I select some cd's to play, the context view I use quite regulary to check lyrics/wikipedia while listening to music. So that makes me think one of those mocks would work quite well.
the first one will definitely work, the second one will not as the toolbar can only be placed full width, either at the top or the bottom, as it is really a different kind of object (QToolBar) and not a dock widget as such.
Ah, sorry, I didn't realize it wasn't possible to not have the toolbar not the full width. I'm curious though: why not make the toolbar a dockable widget too? There's probably a good reason, but I'm just curious.
Keep up the good work!
Keep up the good work!
Mainly because the layout of the toolbar requires it to be wide and "flat". If it was made a dockwidget as well, it would have to be adaptable to other shapes, such as a very tall, narrow one. This does not make much sense the way it currently works.
Besides, the toolbar is in for a major overhaul in the 2.2 time frame anyway, we already have some very nice mockups that we will be working on implementing.
Besides, the toolbar is in for a major overhaul in the 2.2 time frame anyway, we already have some very nice mockups that we will be working on implementing.
Ah, makes sence. I'm curious about the new design... is there a place where I could see one of the mockups for the new toolbar?
My usage is quite simple:
Temporarily disable plasma space in the center and make playlist as wide as possible. No, I am not enemy of central space in Amarok2 but playlist in Amarok1 was quite good metadata editor for me and I'd like to use it again from time to time.
Temporarily disable plasma space in the center and make playlist as wide as possible. No, I am not enemy of central space in Amarok2 but playlist in Amarok1 was quite good metadata editor for me and I'd like to use it again from time to time.
+1, along with sorting using the table header, i could sort easily, and see at a glance the metada for all the songs in the playlist
That's not possible because "the toolbar can only be placed full width".
Here is mine: http://www.eikehein.com/amarok.png
(As requested, the layout limits itself to what is shown possible in the video. Ideally, I'd like the Context view to be another one of the vertical tabs of the Content Browser. This would also be possible with dock widgets, if all the invidual Context Browser tabs were dock widgets as well and their tab bar would have the left-hand position.)
(As requested, the layout limits itself to what is shown possible in the video. Ideally, I'd like the Context view to be another one of the vertical tabs of the Content Browser. This would also be possible with dock widgets, if all the invidual Context Browser tabs were dock widgets as well and their tab bar would have the left-hand position.)
If this flexible format is implemented, you realy should make the tabs on the left all seperate widgets, so i can place some of them side by side, if i want.
1.4 isn't a KDE 4 application .
Amarok 1.4 was a popular application, so I'm probably not the only one who liked its layout.
.Amarok 1.4 was a popular application, so I'm probably not the only one who liked its layout.
Ok, in my first one I made the mistake of putting the toolbar full-width.
Updated version: http://www.eikehein.com/amarok2.png
Updated version: http://www.eikehein.com/amarok2.png
I would do it the same way,
just would like to have the context switch tab on playlist...
I don't use the context view very often, but if I use it i want to have enough space...
just would like to have the context switch tab on playlist...
I don't use the context view very often, but if I use it i want to have enough space...
On my laptop I have a very limited resolution (800x600, I know, old...), and I normally have to collapse the collection browser or the (context view + playlist) won't have enough space.
I would probably use a layout like this one on my laptop, so I would only have two columns, and could switch between context and collection when I wanted to change/add something to my playlist.
I would probably use a layout like this one on my laptop, so I would only have two columns, and could switch between context and collection when I wanted to change/add something to my playlist.
Toolbar on top
http://imagebin.ca/view/VtUgDV.html
Toolbar in bottom
http://imagebin.ca/view/1wcr8PuB.html
The greatest flexibility however is to be able to get multiple context views so that one can separate the lyrics, wiki from the now playing widgets, but I suppose this is not the way things are going to be worked out.
http://imagebin.ca/view/VtUgDV.html
Toolbar in bottom
http://imagebin.ca/view/1wcr8PuB.html
The greatest flexibility however is to be able to get multiple context views so that one can separate the lyrics, wiki from the now playing widgets, but I suppose this is not the way things are going to be worked out.
Yeah, if they allowed you to add or remove additional context views and put them where you want the possibilities just went through the roof. /me drools
+1 to the idea of multiple context views! Not sure whether the architecture of plasma or Amarok would allow this or if there are too many singletons involved, but if it's possible that would really rock (especially since the taskbar-like thing in the 2.1 CV becomes unmanageable with more than three or four applets)
I like this mockup, I like the kd3' interface, with tab on the left for Ipod, collection , playlist & co , and always the vision of the current playlist on the right
Many things will be possible
Here is, for example, the simple "playlist only" interface
http://imagebin.ca/view/RxwcdD8.html
Here is, for example, the simple "playlist only" interface
http://imagebin.ca/view/RxwcdD8.html
This 'winamp' mode is actually possible already today:
http://www.student.dtu.dk/~s052580/files/amarok2.0.2.png
(except for some problems with the large buttons)
http://www.student.dtu.dk/~s052580/files/amarok2.0.2.png
(except for some problems with the large buttons)
I believe the video basicly says it all.
What I will use it for:
- Optimise pixel-estate
- Reduce pointer/mousemovements
It might also be beneficial because some functions could be further modularised:
-File/collection/internet/playlist
-The "playbar"
-The modules in the centerfield
I would like to see this kind of flexibility in every single KDE app.
Actually, I cannot think of any app that would not benefit.
What I will use it for:
- Optimise pixel-estate
- Reduce pointer/mousemovements
It might also be beneficial because some functions could be further modularised:
-File/collection/internet/playlist
-The "playbar"
-The modules in the centerfield
I would like to see this kind of flexibility in every single KDE app.
Actually, I cannot think of any app that would not benefit.
Here is mine. The first one shows the regualr Amarok.
http://imagebin.ca/view/4I76pKYt.html
The second one shows what happens when you open a service like magnatune, shoutcast or last.fm. I would separate sevices from collection to enable drag&drop of files into the collection and the playlist.
http://imagebin.ca/view/0JmwcZ.html
Overall I would leave the toolbar where it is, but put the context view below it. Most of the space should be for collection and playlist
http://imagebin.ca/view/4I76pKYt.html
The second one shows what happens when you open a service like magnatune, shoutcast or last.fm. I would separate sevices from collection to enable drag&drop of files into the collection and the playlist.
http://imagebin.ca/view/0JmwcZ.html
Overall I would leave the toolbar where it is, but put the context view below it. Most of the space should be for collection and playlist
The original video is amazing. Thanks for proposing an option to remove the 'context view'. No offense to the devs, but it's absolutely deplorable in 2.0.
Here's my simple layout..
http://imagebin.ca/view/Gpyb7SuN.html
As the Thunderbird guys say, 'Reclaim your music player!'
Here's my simple layout..
http://imagebin.ca/view/Gpyb7SuN.html
As the Thunderbird guys say, 'Reclaim your music player!'
I would also suggest to integrate an option that allows you to switch to the default layout with a simple click to avoid having users complaining that they ruined their layout.
I don't know if I could really make use of this but I am really looking forward to be able to play around with it. For now, I just can't imagine a situation where it could come in handy.
I don't know if I could really make use of this but I am really looking forward to be able to play around with it. For now, I just can't imagine a situation where it could come in handy.
At first I'd probably just replicate the Amarok 1.x layout, with the context browser and other browsers collapsed into a tab-thingie on the left, and the playlist on the right. After that I might experiment with it.
Hi,
I would use different views for different uses or scenarios. For example:
1. I'm editing tags: a full info Playlist view (as in Amarok 1.4)
2. using my netbook (or maybe phone -in a near future?-) I'd probably want a Winamp like layout where I can switch between Collection/ Playlist views
3. I've prepared a playlist (or am using "dynamic" playlists) for a party: only the Context view with Collection and Playlist as tabs(I don't want people jumping to their favorite track in the playlist)
4. I want to show Amarok off: Use the Amarok2 layout
5. I'm discovering my music (i.e. reading Wikipedia, lyrics etc): Context view and Collection with Playlist as a tab.
6. I'm using the (future) karaoke applet: only the Context view (Or maybe Context view and Collection so the next person can browse through the songs)
etc.
OK that last was a bit far fetched (don't want to start a "Amarok is not designed for Karaoke" debate ), but the idea being that different uses of Amarok may require different layouts. Even for the same user.
However, from what I've been reading this will not go into Amarok. I really wonder why its controversial amongst devs.
I'd understand maintenance problems and the such, but from what I can infer from the last few post this is not really the problem.
[Speculation]
It may be due to other technical problems, marketing/product concept problems...
[Opinion within Speculation]
As for product concept problems, i.e. player not recognizable as Amarok, focusing on too many uses and not one main use, product too broadly defined etc. I believe Amarok should be marketed and conceived as an experience rather that the product. In other words, that Amarok should be what enables you to enjoy your music (in whatever way you wish) rather than a program that plays music. Thus, making any concerns on the GUI layout not being recognizable, uses being too broad etc. a non-issue. However, I don’t have all of the inside information on Amarok’s team’s strategy and my opinions could be far from their view.
[/Opinion within Speculation]
[/Speculation]
Finally, thanks for Amarok2 (and 1.4 also obviously) as it is an excellent application and a great example of an active, amusing and friendly open source community.
Sorry for not making up mockups, but I'm at work and can't really do them.
Best regards,
Michael
I would use different views for different uses or scenarios. For example:
1. I'm editing tags: a full info Playlist view (as in Amarok 1.4)
2. using my netbook (or maybe phone -in a near future?-) I'd probably want a Winamp like layout where I can switch between Collection/ Playlist views
3. I've prepared a playlist (or am using "dynamic" playlists) for a party: only the Context view with Collection and Playlist as tabs(I don't want people jumping to their favorite track in the playlist)
4. I want to show Amarok off: Use the Amarok2 layout
5. I'm discovering my music (i.e. reading Wikipedia, lyrics etc): Context view and Collection with Playlist as a tab.
6. I'm using the (future) karaoke applet: only the Context view (Or maybe Context view and Collection so the next person can browse through the songs)
etc.
OK that last was a bit far fetched (don't want to start a "Amarok is not designed for Karaoke" debate
), but the idea being that different uses of Amarok may require different layouts. Even for the same user.However, from what I've been reading this will not go into Amarok. I really wonder why its controversial amongst devs.
I'd understand maintenance problems and the such, but from what I can infer from the last few post this is not really the problem.
[Speculation]
It may be due to other technical problems, marketing/product concept problems...
[Opinion within Speculation]
As for product concept problems, i.e. player not recognizable as Amarok, focusing on too many uses and not one main use, product too broadly defined etc. I believe Amarok should be marketed and conceived as an experience rather that the product. In other words, that Amarok should be what enables you to enjoy your music (in whatever way you wish) rather than a program that plays music. Thus, making any concerns on the GUI layout not being recognizable, uses being too broad etc. a non-issue. However, I don’t have all of the inside information on Amarok’s team’s strategy and my opinions could be far from their view.
[/Opinion within Speculation]
[/Speculation]
Finally, thanks for Amarok2 (and 1.4 also obviously) as it is an excellent application and a great example of an active, amusing and friendly open source community.
Sorry for not making up mockups, but I'm at work and can't really do them.
Best regards,
Michael
Thanks a lot for your post. That is exactly what I was thinking too. You can't talk about the real deal how the interface should look like. Most of the time I would stick with the Amarok 2.0 interface because I really like it (even though most of the people here still stick with the 1.4 layout). But as you said there might be a party mode an edit mode or a netbook compilation. That is the reason why I hope this widget-thing will be implemented.
I already use this flexibility with the new playlist and configured different kinds of playlist-layouts for different purposes.
But maybe you are right it is all about marketing that people recognize amarok as amarok.
I already use this flexibility with the new playlist and configured different kinds of playlist-layouts for different purposes.
But maybe you are right it is all about marketing that people recognize amarok as amarok.
Couldn't the collection and playlist areas be exported/converted/embeded into plasma widgets and then the context view could be the whole main window and people could create almost any layout. I also recall reading somewhere that plasma layouts might be shareable at some point in the future.
+1 to 22 & 23, even if we are dramatically off-topic.... ^^''
"User configurable activities" is the way to go
This concept (minus "customization", that could be the strength of Amarok) is already used by Windows Media Player and showed in an old Amarok mock-up.
http://www.kde-look.org/content/show.php/A+Media+Player+for+KDE4?content=94472
"User configurable activities" is the way to go
This concept (minus "customization", that could be the strength of Amarok) is already used by Windows Media Player and showed in an old Amarok mock-up.
http://www.kde-look.org/content/show.php/A+Media+Player+for+KDE4?content=94472
Hi,
I think this would be really cool. My problem currently is that the plasma view is too small on my laptop so I dont like it much, I keep scrolling and resizing it.
So I would probably stack it in the collection browser and make that left pane wider. And instead of having to resize it I would just have to click on the tab to see it, but it would be wider.
I think this would be really cool. My problem currently is that the plasma view is too small on my laptop so I dont like it much, I keep scrolling and resizing it.
So I would probably stack it in the collection browser and make that left pane wider. And instead of having to resize it I would just have to click on the tab to see it, but it would be wider.
A layout for smaller screens, with hidden menu (or I forgot to copy paste one, whichever one you prefer):
http://tvtel.pt/knuckles/pictures/amarok2-mockup.png
http://tvtel.pt/knuckles/pictures/amarok2-mockup.png
Mine's here. It is similar to what others have posted already...
http://imagebin.ca/view/g7uCW4.html
It does not have to look like any one person's or a group of people's mockup. In my view, the user should be given a choice to make that decision. Today I think I like the one I posted. But depending on circumstances (like usage on a small form-factor computer) I may change my mind and would be willing to sacrifice some of the information visible for more clarity. In such a situation having the 'option' to change the layout is very much desired.
http://imagebin.ca/view/g7uCW4.html
It does not have to look like any one person's or a group of people's mockup. In my view, the user should be given a choice to make that decision. Today I think I like the one I posted. But depending on circumstances (like usage on a small form-factor computer) I may change my mind and would be willing to sacrifice some of the information visible for more clarity. In such a situation having the 'option' to change the layout is very much desired.
When doing this little exercise, i found that the default layout is a pretty good layout. however, i would probably test out these two layouts if this feature was implemented:
http://imagebin.ca/view/IONlVp8.html
http://imagebin.ca/view/IONlVp8.html
http://imagebin.ca/view/aKdeRZK.html
Pretty simple, or how about:
http://imagebin.ca/view/hOX4xE.html
More interesting, tabs for each dock.
Pretty simple, or how about:
http://imagebin.ca/view/hOX4xE.html
More interesting, tabs for each dock.
I've created a couple of quick-n-dirty mockups based roughly on yesterday's video at the 1:06 mark.
They show two vertical panels, each with tabs at the bottom.
Context/Playlist mockup here: http://www.geeksonthebeach.ca/images/my-amarok-context.jpg
Collection/Playlist here:
http://www.geeksonthebeach.ca/images/my-amarok-collection.jpg
They show two vertical panels, each with tabs at the bottom.
Context/Playlist mockup here: http://www.geeksonthebeach.ca/images/my-amarok-context.jpg
Collection/Playlist here:
http://www.geeksonthebeach.ca/images/my-amarok-collection.jpg
Really like that interface...
especially on small displays would it be useful!
especially on small displays would it be useful!
Let me preface this next comment by stating that I say this out of love for the project and with respect for all that's been done: The more I played with the interface while creating the above mockups, the more it became clear to me that the current interface is a dog's breakfast.
It's all jammed in there without much rhyme or reason, and it's full of redundancies.
In creating my mockups (above) I tried to stay within the confines of what was demonstrated yesterday, but truthfully, if someone was willing to push the boundaries a bit, I'm the sure the UI could me made far leaner and more usable.
You and I are technically proficient and have put in the effort to learn the current setup. But I've seen how daunting it is when a noobie tries to make sense of it. My wife and kids take one look and call me.
I'm a web designer with a focus on creating usable and clean interfaces. I'll put the offer out there: If the powers that be want some help, I would love to be of service. Even if it's with an eye towards V2.4.
Email me if you guys are interested. I have some ideas.
It's all jammed in there without much rhyme or reason, and it's full of redundancies.
In creating my mockups (above) I tried to stay within the confines of what was demonstrated yesterday, but truthfully, if someone was willing to push the boundaries a bit, I'm the sure the UI could me made far leaner and more usable.
You and I are technically proficient and have put in the effort to learn the current setup. But I've seen how daunting it is when a noobie tries to make sense of it. My wife and kids take one look and call me.
I'm a web designer with a focus on creating usable and clean interfaces. I'll put the offer out there: If the powers that be want some help, I would love to be of service. Even if it's with an eye towards V2.4.
Email me if you guys are interested. I have some ideas.
I experienced the exact opposit just a few days ago. A friend of mine was sitting in front of Amarok and with the open collection on the left he knew exactly what to do with it.
After two minutes he was more then just impressed by the player he wanted to hav it. Saying that it realy looks great ant he liked especially the lyrics-feature in the middle. That showed me that Amarok is not just a geek-player but something that even the regular user can enjoy.
After two minutes he was more then just impressed by the player he wanted to hav it. Saying that it realy looks great ant he liked especially the lyrics-feature in the middle. That showed me that Amarok is not just a geek-player but something that even the regular user can enjoy.
OMFG! 
Ive just seen the video today and ... WOW!
That would make Amarok PERFECT
i also would ship 2 default layouts and make the user-layouts import/exportable
default layouts would be: current Amarok 2 layout and A Layout that resembles amarok 1.x as close as possible
Ive just seen the video today and ... WOW!
That would make Amarok PERFECT
i also would ship 2 default layouts and make the user-layouts import/exportable
default layouts would be: current Amarok 2 layout and A Layout that resembles amarok 1.x as close as possible
+1
It looks awesome! What are the developers going to do after Amarok becomes absolutely perfect?
It looks awesome! What are the developers going to do after Amarok becomes absolutely perfect?
Why, redefine "absolutely perfect" and make it even better of course!
I personally would change it so it looks like in the video at ~ 1:20:
The context / browser views both on the left, tabbed. And the buttons on the bottom.
Please do not change the UI to something most users want, but rather go for flexibility.
With KDE it was almost always a "good defaults, but still configurable" situation. Please keep this in amarok.
Good defaults are a good thing, but you can still have flexibility at the same time.
Kind regards, and thanks for the good work
Christian
The context / browser views both on the left, tabbed. And the buttons on the bottom.
Please do not change the UI to something most users want, but rather go for flexibility.
With KDE it was almost always a "good defaults, but still configurable" situation. Please keep this in amarok.
Good defaults are a good thing, but you can still have flexibility at the same time.
Kind regards, and thanks for the good work
Christian
Hey.
First of all I would tab the browsers and the context view. So playlist at the right, and at the left one big area that can be switched (by two tabs at the top) between the browsers and the context view. Reason: I never need the browsers and the context view at the same time. Either I am browsing my collection to add new music to the playlist, or I am listening to a song and interested in related information (context view). Both at the same time is not needed for me.
Now, I now this is out of scope for what you asked for, but having a layout that gives more space to the collection browser would also make it easier to play around with different interfaces for the collection browser, e.g. an album gallery or a winamp/itunes style three pane browser. The very limited collection browser (only tree style browsing is possible) is, for me, amarok's biggest caveat. If I want to select a certain song and search for the artists, I need two clicks to expand to the song list (+ on artist, + on album). Likewise, if I am searching for an album name, and three or for artists are returned, I have to expand each first to see the actual album art and title.
So - Dockwidgets would allow to give parts of the interface easily more or less space, and therefore make it easier to try out different interfaces. Which is great. No, not great, amazing. This could finally make Amarok the versatile, easy-to-use, flexible, oh - perfect music player. Go for it.
First of all I would tab the browsers and the context view. So playlist at the right, and at the left one big area that can be switched (by two tabs at the top) between the browsers and the context view. Reason: I never need the browsers and the context view at the same time. Either I am browsing my collection to add new music to the playlist, or I am listening to a song and interested in related information (context view). Both at the same time is not needed for me.
Now, I now this is out of scope for what you asked for, but having a layout that gives more space to the collection browser would also make it easier to play around with different interfaces for the collection browser, e.g. an album gallery or a winamp/itunes style three pane browser. The very limited collection browser (only tree style browsing is possible) is, for me, amarok's biggest caveat. If I want to select a certain song and search for the artists, I need two clicks to expand to the song list (+ on artist, + on album). Likewise, if I am searching for an album name, and three or for artists are returned, I have to expand each first to see the actual album art and title.
So - Dockwidgets would allow to give parts of the interface easily more or less space, and therefore make it easier to try out different interfaces. Which is great. No, not great, amazing. This could finally make Amarok the versatile, easy-to-use, flexible, oh - perfect music player. Go for it.
No sketch needed, just simple textual description: playlist column to the left, browser column to the right. Play controls do eat up to much space in my humble opinion: make them small (single column width) and stack them either on top of the playlist or below it.
Sorry to reply to myself: maybe make the playlist controls two separate elements: one with the buttons, and a separate volume and position control. This gives even more UI freedom.
Here my OpenOffice Calc to see and use what i think.
See Table 1 and 2
http://decembersoul.dyndns.org/~patrick/amarok.ods
See Table 1 and 2
http://decembersoul.dyndns.org/~patrick/amarok.ods
What about something a litle based on opera 9 sidebar.
Move "Widget Configuration" button(or put "Add tab") to the top of the tabs on the left.
Transform the current tabs in docks.
Each Widget is a dock.
Remove the Context View.
Add an options to chose the position of the tabs(left,right,top,bottom).
Add a option to chose what will be showed in the tabs(text,icons,text only in the selected tab like konqueror).
Users can drag any tab out of the side to any place in Amarok.
By default the layout can be just like it is in 2.1 but the with widgets as docks.
I think this will make happy everybody that commented here.
If you need i think i can do a mockup.
Move "Widget Configuration" button(or put "Add tab") to the top of the tabs on the left.
Transform the current tabs in docks.
Each Widget is a dock.
Remove the Context View.
Add an options to chose the position of the tabs(left,right,top,bottom).
Add a option to chose what will be showed in the tabs(text,icons,text only in the selected tab like konqueror).
Users can drag any tab out of the side to any place in Amarok.
By default the layout can be just like it is in 2.1 but the with widgets as docks.
I think this will make happy everybody that commented here.
If you need i think i can do a mockup.
Amarok Links
Calendar
|
November '09 |
|
||||
| Mon | Tue | Wed | Thu | Fri | Sat | Sun |
| 1 | ||||||
| 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| 9 | 10 | 11 | 12 | 13 | 14 | 15 |
| 16 | 17 | 18 | 19 | 20 | 21 | 22 |
| 23 | 24 | 25 | 26 | 27 | 28 | 29 |
| 30 | ||||||
Quicksearch
Categories
Syndicate This Blog
Blog Administration
We Listen To...
Powered by
