Re: [PATCH] - New sidepanel plug-in for Gtk bookmarks and places
- From: Alexander Larsson <alexl redhat com>
- To: Jamie McCracken <jamiemcc blueyonder co uk>
- Cc: Nautilus <nautilus-list gnome org>
- Subject: Re: [PATCH] - New sidepanel plug-in for Gtk bookmarks and places
- Date: Thu, 30 Jun 2005 17:16:14 +0200
On Wed, 2005-06-29 at 18:45 +0100, Jamie McCracken wrote:
> >Alexander Larsson wrote:
> > The behavour you want for the places part of the tree sidebar is:
> > * separator between the roots and the shortcuts
> > * Allow expansion of tree sidebars
> > * But, don't consider them "roots" when auto-expanding due to a location
> > change.
> > * Allow dnd of folders to the empty part of the sidebar, meaning "add
> > bookmark"
> >
> > The main problem I can see with using the tree sidebar as a places
> > sidebar is that the tree auto-expands when you navigate the tree, thus
> > the shortcuts are almost always scrolled out of view.
>
> yes I noticed!
>
> >
> > I can see two main ways to solve this:
> > * Add a preference about auto-expansion on location change. (This really
> > makes sense as a preference, because it works with the way some use the
> > tree, but not with others.) It also solves a similar issue with the
> > auto-expansion of the tree hiding the mounted volumes below.
>
> Not sure about that. I only use the tree view for navigating deep
> hierarchies and in those case I would want it to auto-expand. Having to
> goto prefs and constantly change the setting would be irritating.
Yeah, I agree. I don't think this solution is very good.
> > * Somehow split into two trees and pack the trees such that expanding
> > something in the volumes part never totally hides the shortcut part of
> > the tree.
> > I tried to figure out a way to do this, and it may be possible if you
> > have a custom container widget for the splitting and a slightly
> > customized GtkScrolledWindow that size_requests the full height of the
> > child. However, its not obvious how the splitting up should work (i.e.
> > in the case of both trees being tall, how should we split? 50% each?)
> > Another way would be to put the trees in a vpane and let the user change
> > the relative sizes.
>
> vpane makes more sense IMO - user gets to control it but the tree view
> already suffers from lack of space anyway so this will just make it
> worse. Still it offers a way to split out the tree view from the places
> if the lower pane always shows the hierarchical tree for the current
> location (without any places) and the upper pane just the non-expandable
> places and volumes.
Yeah, this is probably the best approach for this. Can you experiment
with that a bit?
If it doesn't work out well I guess the places sidebar makes more sense.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Alexander Larsson Red Hat, Inc
alexl redhat com alla lysator liu se
He's a fiendish sweet-toothed barbarian haunted by memories of 'Nam. She's a
warm-hearted gold-digging bodyguard from a different time and place. They
fight crime!
[
Date Prev][Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]