Menu
▾
▴
Re: [Gramps-devel] Re : Proposal to remove topbar filter
|
From: Benny M. <ben...@gm...> - 2010-11-22 12:51:34
|
2010/11/22 Doug Blank <dou...@gm...> > Thanks for all of the feedback! > > It seems all of the arguments so far have been about the UI, which is > fine. That suggests that we can get rid of the two different ways of > functioning and collapse that down to just one (the way that sidebar > works, perhaps with some niceties added). That would get rid of having > to explain differences. > > The problem remaining, then, is how to make a consistent UI that could > use either a simple, topbar filter, or something more (and even > suggest to users that there is something more powerful available). > > Some ideas: > > 1) Have a simplified topbar available for single entry, simple filters > (either a single column, or a single custom filter). > 2) This might require that every field have associated with it a > filter (so that date columns would be searched by the date logic, > "male" would not match "female", note would search the entire text, > etc) > 3) More complex filters could be available by having a "+" button in > the topbar, which would bring up a dialog (not sidebar). That would > prevent real estate from being eaten up. The topbar would become a > button indicating that a more complex filter is in effect. Clicking it > would bring up the dialog (which used to be the sidebar filter). > 4) This would integrate the topbar/sidebar as the topbar would be a > simplified version of the full dialog, and only shown when the dialog > isn't. > 5) This also removes some of the complexity by just making the sidebar > a dialog, which is either opened or closed, and makes it so that its > showing is independent of the gramplet pane. (As an aside, the full > filter dialog could be dockable in the gramplet pane, which would give > nearly the current appearance of the sidebar filter). > > Does anyone see any issue with that type of strategy? > It is hard to envisage what you mean. I suppose the gramplet pane can be closed also. Technically I know very good how topbar/sidebar relates to the view as I rewrote that with Nick for 3.2. The changes you want to do go deep in the core code and are not that simple. What is the global strategy? 1. We still have the problem in trunk that Geoview is broken with panes. That needs a solution, meaning several of us will have to try and fix that. Serge thinks it is a Gtk bug... 2. We want the navigation bar to the left, view center, and a general docking area to the right. Correct? 3. Listviews have a search option shown via topbar or filter bar, geoview a sidebar search possible. 4. Topbar search remains but uses the filter infrastructure instead of the view model/column data 5. Sidebar search becomes a dialog that is dockable in the general docking area? Note that above can be done without having to do 4., that is, it remains possible to keep searching in the columns. Tim's remark gives a hint quite some people are using it. If above is done, best would be to do it in parts. So first 1, the 2/5, .. Benny > > -Doug > > On Mon, Nov 22, 2010 at 5:38 AM, Tim Lyons <guy...@gm...> wrote: > > > > > > Benny Malengier wrote: > >> > >> I don't like the idea of a dialog for search much. This is not a > >> texteditor, > >> but search on a column view, no need to block the view somehow with a > >> dialog. > >> > > > > Sorry, my fault, I confused things by the way I mentioned top filter in > my > > argument. I think you have misunderstood. > > > > Personally I don't think there is much needing a change. Even though I > know > > about the sidebar, I will still use the topbar. > > > > What I meant was, If you want to make a change, then: > > (a) remove the side filter, > > (b) leave the top filter exactly as it is, except > > (c) add 'custom filter' to the bottom of the top filter drop-down, and > > allowing the user to specify one of the filters he had defined in the > filter > > editor > > (d) if the user selects the custom filter, then the filter name he > selects > > could be displayed in the top filter where the filter criterion is > normally > > displayed. > > > > > > -- > > View this message in context: > http://gramps.1791082.n4.nabble.com/Proposal-to-remove-topbar-filter-tp3052501p3053387.html > > Sent from the GRAMPS - Dev mailing list archive at Nabble.com. > > > > > ------------------------------------------------------------------------------ > > Beautiful is writing same markup. Internet Explorer 9 supports > > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > > Spend less time writing and rewriting code and more time creating great > > experiences on the web. Be a part of the beta today > > http://p.sf.net/sfu/msIE9-sfdev2dev > > _______________________________________________ > > Gramps-devel mailing list > > Gra...@li... > > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > > > ------------------------------------------------------------------------------ > Beautiful is writing same markup. Internet Explorer 9 supports > standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3. > Spend less time writing and rewriting code and more time creating great > experiences on the web. Be a part of the beta today > http://p.sf.net/sfu/msIE9-sfdev2dev > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > |