Rationale for double click and project view and can we bring back following the global setting?
Andreas Pakulat
apaku at gmx.de
Fri Aug 14 20:01:17 UTC 2009
On 14.08.09 21:17:23, David Nolden wrote:
> Am Freitag 14 August 2009 20:58:21 schrieb Andreas Pakulat:
> > If you look at the QTest treeview, you'll notice that with adding
> > _anything_ you'll end up with even less space. The treeview is already
> > pretty small and also tries to conserve space by making the spacing
> > smaller. Adding a 16x16 icon/checkbox/clickable-thing for selection
> > takes away even more space.
> >
> > Not to mention, that IMHO checkboxes in such a tree look really really
> > ugly.
> That is true, but we can also implement that logic without using _real_
> checkboxes.
>
> Idea: Do the same thing dolphin does when hovering the icon of a file in
> 'details' treeview mode:
Thanks, I think I need to use that app more often, it does have some
nice UI ideas. Thats constructive discussion. Indeed that could work, do
you know wether this is in kdelibs? If not it should be.
> - If the item is not part of the build-set, blend in a 'plus' sign, and show a
> tooltip "Add top buildset"
> - If the item already is in the build set, blend in the 'minus' sign, and show
> tooltip "Remove from buildset".
> Then we can add a permanent highlighting of items that are part of the
> buildset, and have a well-working selection interface if we define 'build-set
> = selection'.
Hmm, I think the idea is good, but I'd like to keep the buildset list
still. Two reasons:
a) It allows to order items
b) It allows to more easily see all items in the buildset
Also the selection is "published" to the complete app, hence it can also
be used for other things.
> For all the rest of the treeview, we can then use whatever mouse behavior we
> like. Although I think for group-headers it should then be 'always
> expand/unexpand on single-click', as it already was temporarily.
I think with the above being implemented we should then adhere to
kde-setting for single/double click for activation. And for me
activating a folder means expanding it.
Andreas
--
Do not overtax your powers.
More information about the KDevelop-devel
mailing list