Fwd: patch for src/playlist/view...

[Nikolaj Hald Nielsen]

whoops, forgot to send this to the list...


---------- Forwarded message ----------
From: Nikolaj Hald Nielsen <nhnfreespirit at gmail.com>
Date: Wed, Jan 14, 2009 at 9:47 PM
Subject: Re: patch for src/playlist/view...
To: Thomas Lübking <thomas.luebking at web.de>


> i sense issues with using plain dnd here:
> 1. you'll need some pretty large stack to drag from
> 2. once dragged inplasce, in you cannot simply e.g. swap artist and
> composer, but will have to drag on in and the other out
> 3. you cannot dnd features as "width" or even "bold" anyway (you could add
> some sort of splitter, but run into the situation where "trackNumber" is
> much wider than "1" ;-)
>
> thus i'd suggest to do a qt-designer similar thing:
> - allow to add a dnd enabled label "element" - yet invalid - autoinserting
> more hboxes on demand (i.e. there needs to be a global "Drag new element
> from here" label) - dropping the label out of the vbox/hbox matrix deletes
> it
>
> - the invalid elements could say "???", the valid one an example value and
> show the element type in a tooltip. thus the user has an idea what his setup
> will actually look like in the end
>
> - the geometry would accord to the set velue in the config dialog and the
> editor geometry (with the config button on the left to ensure it's visible
> even if the user sets widths like "80" - "88" - ... uupps, should have been
> just "8" ... ;-)
>
> - attach a "config" toolbutton that opens a small dialog
>
> - the dialog contains a combo for the values (plylistdefines), checkboxes
> for bool etc, a spinbox for width, maybe a combo for measure..., combos for
> alignment and whatever
>
> - the hbox inheritor (row) removes itself as soon as it contains no more
> widgets
>
> - as soon as the editor is closed, the hboxes are dumped into layout rows
> with the contained labels as elements (and their attributes from the config
> dialog)
>
> if you want me to, i'll implement a draft of this. (there's still a lack on
> handling covers in this, i know...)

If you feel like doing a draft, that would be awesome as it is one of
the major tasks for 2.1.0 and I personally have plenty of other things
on my hands as well. As for covers, that is pretty much just a
checkbox for each item type ( "show cover" yes or no ). As for how
exactly the gui should work , you should talk to Dan who is really our
UI dude, and the original mockup is his.

Dan, get in here! :-D

- Nikolaj