Re: [Banshee-List] ANNOUNCE: Banshee 1.0 Alpha 3 (0.98.3) Released!
- From: "Gabriel Burt" <gabriel burt gmail com>
- To: banshee-list gnome org
- Subject: Re: [Banshee-List] ANNOUNCE: Banshee 1.0 Alpha 3 (0.98.3) Released!
- Date: Tue, 15 Apr 2008 19:57:28 -0500
On Tue, Apr 15, 2008 at 2:25 PM, LCID Fire <lcid-fire gmx net> wrote:
>
> Gabriel Burt wrote:
> > On Tue, Apr 15, 2008 at 2:04 PM, LCID Fire <lcid-fire gmx net> wrote:
> >> Gabriel Burt wrote:
> >> > On Tue, Apr 15, 2008 at 11:55 AM, LCID Fire <lcid-fire gmx net> wrote:
> >> >> Aaron Bockover wrote:
> >> >> > Hello,
> >> >> >
> >> >> > We've released Banshee 1.0 Alpha 3 (0.98.3), two weeks after our second
> >> >> > 1.0 alpha release, which brings some great new features and lots of bug
> >> >> > fixes and performance improvements.
> >> >> Well I finally tried out the new banshee and it's looks quite good. I
> >> >> love the lastfm features but didn't have the chance yet to play around
> >> >> that much.
> >> >> One thing that got pretty appearent: Please remove the browser frame!
> >> >> The old frame layout was really nice and simple - but not only does the
> >> >> browser frame take much space - it also destroys the simplicity of the
> >> >> ui. The basic idea is great - but I'd like it more to be in the source
> >> >> list than in a seperate frame.
> >> >
> >> > I don't know what you mean. Is your issue with the Last.fm support,
> >> > or general? Can you explain in more detail, or provide a mockup of
> >> > what you want?
> >>
> >> Sorry to be not clear about this.
> >> I have a problem with the general layout. I'd rather have the browser
> >> and the source list merged. Perhaps it gets a little clearer looking at
> >> the following fake screenshot:
> >> http://farm4.static.flickr.com/3060/2416228517_8d8159c66a_b.jpg
> >> This is what I think should be changed. (Look at the source list ;))
> >> My line of argumentation is that I don't need to filter the playlists
> >> anymore because they are already filtered. At least in the way I use
> >> banshee it's not a use case (but I'd be interested what use cases other
> >> people have). So the only thing where I think it makes sense is the full
> >> music library - and therefor a new ChildSource "All artists" could be added.
> >> Did I make myself a little more clear?
> >
> > So the real issue is you don't want the browser to be shown for
> > playlists, right? The way to solve that, if at all, is to remember if
> > you chose to hide the browser on a source (including playlists, etc).
> Not entirely.
> I don't want another frame(!) for the browser to start with (since the
> source list is already some kind of browser) - but I would like to have
> the browser functionality in a slicker layout. This means I like the
> idea - but not the way it is shown in the ui. One solution for this
> would be to merge the source list and browser.
> It's true - I don't need the browser in the playlist - but it wouldn't
> hurt me to have it as long as it would not be a seperate frame.
Sorry to say, but I don't think it's going to be changed. I, for one,
really don't like your mockup, and I think the way our browser works
is slick and what people expect. Other views where you have your
music shown in one list but grouped visually by artist/album etc are
possible/planned. But the browser will stay how it is.
Gabriel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]