Hi Nicolaj,<br><br>thanks for replying.<br><br><div><span class="gmail_quote">2007/3/1, Nikolaj Hald Nielsen <<a href="mailto:nhnfreespirit@gmail.com">nhnfreespirit@gmail.com</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Now that the context browser is in the center and always visible it might be<br>> a opportunity to rethink it's concept.<br>> This is related to music stores because I don't think the current tree view<br>
> browser will scale when music stores get a bigger catalog. Consider a music<br>> store that has a web-like interface, it's easier to browse, looks better,<br>> albumart, browsing through a catalog based on related artists, genres,
<br>> recommendations, etc.<br>> To implement a store like that we need screen real estate. The only place I<br>> can think of that we have that is in the center pane.<br><br><br>I have to strongly disagre with moving the music store into the center
<br>view at this time, for several reasons:<br><br>1. The one store that we have at this time (<a href="http://Magnatnue.com">Magnatnue.com</a>) works<br>conceptually very much like a browser. The preview tracks can be added
<br>to a playlist in the same way content from any other browser can.<br>There is no real reason to change this store significantly at this<br>time, especially since the site itself does not offer any<br>significantly different ways of browsing their content.
</blockquote><div><br>You know, the magnatune store and other stores implemented like a tree view browser, could coexist with a store using the Center Pane. In fact, those could be 2 views of the same, shared, data.<br></div>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">2. I agree that a store with a significantly larger catalog will need<br>additional features for searching and limiting what is displayed in a
<br>tree view, but this is not something that has been explored at all in<br>the current implementation. Magnatune is adding albums on a monthly<br>basis, so this is something that needs to be taken into account soon<br>anyway. Removing the default "All" genre and only showing artists from
<br>one actual genre at a time would be a good first step I think.</blockquote><div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
3. I think this is my primary objection. There are no concrete plans<br>for collaborating with other stores at this time. While I am not<br>against this at all, I do think it is very dangerous to think up a new<br>glorified way of handling shops when we know nothing about the
<br>features, needs, interface, metadata availability and content handling<br>of any future stores. I am very open to having this discussion again<br>when we know more about what (if any) stores actually wish to<br>integrate into Amarok and what features they offer.
</blockquote><div><br>It seems obvious to me we will implement new ones since there are offers. And concerning your arguments, a flexible framework will allow us to handle just about anything a store can trow at us.<br></div>
<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">4. In many cases I think the center pane can be used to argument a<br>store if they are shown at the same time. Looking up wikipedia data of
<br>the artist selected in the Magnatune store as an addition to the<br>stores own description springs to mind.</blockquote><div><br>I believe the stores will be able to supply most metadata themselves. I don't consider them good stores if they don't.
<br><br>Greets<br></div><br></div><br>