Collection View/Playlist Ideas

[Ian Monroe]

I agree about how it should be tabs. I hadn't thought of been all been
toggable.

On 5/11/07, Jeff Mitchell <kde-dev at emailgoeshere.com> wrote:
> Here's a couple ideas that were floated on IRC:
>
> The Kopete style scrolling could be implemented such that it toggles when the
> user either holds down or clicks the middle mouse button.  This way, it's
> easily accessible for those that want it, but not forced on those that don't
> (and not made into a menu option).  Users can pick which way they want, when
> they want.

And what if the user wants to just scroll? This is almost more
confusing. Personally from using kopete I find it very easy to use
(though we'll have to see with really long lists) and should just be
the default.

> Regarding my Pop-Up Dropper idea, the Context View is right next to the
> Collection View and is a QGraphicsView -- which is designed to display
> graphical items and scroll, zoom and scale them quickly (plus I'm assuming
> OpenGL eye candy could be added if we wanted).  So on a drag start, the
> Collection View could trigger the Context View to shade what's currently
> there, and pop up these new items and handle them...when the user gets too
> far away or stops the drag, those new items are disabled and the rest of the
> scene is re-enabled.  Or something like that...I don't know much about it,
> but it seems like it might be doable.  Anyone's thoughts/revelations/know-how
> is appreciated.  But I gotta say, if we have this large QGraphicsView in the
> center of our app, we may as well use it   :-)

Couldn't we just have a qgraphicsview widget just be like a popup
thing over whatever is under. I'm not sure how this would work, but it
would be nice to not have to make assumptions about the contextview.

Ian