Menu
▾
▴
Re: [Gramps-devel] Bottom bar/side bar comments
|
From: Nick H. <nic...@ho...> - 2011-01-17 01:39:37
|
Gary, Thanks for your feedback. Gary Burton wrote: > Hello devs > > I like the way that the bottom bar and side bars are evolving in trunk and I > have a couple of comments, I guess probably aimed at Nick, who's implemented > much of this. > > 1) Both areas fulfill similar roles, but the user has to interact with them in > different ways. For example, the side bar uses a context menu to add gramplets > whereas the bottom bar uses buttons to add and remove gramplets. For the side > bar, a list of available gramplets appears in the context menu, but for the > bottom bar there is a dialog window to choose a new gramplet. The bottom bar can > be closed by clicking a button or from the View menu, but the sidebar can only > be closed by toggling the main View menu. Is the intention to choose one > particular approach and apply it to both bottom/side bars so that they work in > the same manner? > > Yes, you are quite right - we need to make both the sidebar and bottombar have the same user interface. At the moment I am working on a single GrampsBar class which will be used for both bars. This will use the tabbed layout of the bottombar, but will be capable of containing a filter page like the sidebar. There are two features that I still need to add: 1. The ability to restore a deleted gramplet. 2. Tabs should be able to indicate if they have content. We will do this as it is done in the editor tabs, by changing the tab text to bold. I have a working solution, but there are a few things that I am not quite happy with yet: 1. The "Add", "Remove" and "Close" buttons don't look right in the sidebar. Maybe a context menu would be better? 2. Should the "Filter" tab have special behaviour. I prevent it from closing. Is this correct or should it behave like the other tabs? 3. GeoView is still a concern. The window resizing and dynamic creation of the filter tab needs some further thought. Perhaps I should just commit what I have and get some more feedback. > 2) When the bottom bar contains a gramplet it can grab quite a large percentage > of screen space on a small device (e.g. a netbook) with no way to resize it > smaller than a certain size. The bottombar height is determined by the height values in the grsamplet plugin data. In the example bottombar gramplets this is 200 pixels. I could override this, change the height of the gramplets, or a combination of both. > Here's an example. My main system runs with a > 1024x760 screen resolution. Benny has said that we need to make it look good on a 800x600 resolution. > Opening the Person View and the bottom bar > (containing just the Person Attributes gramplet), the bottom bar occupies about > a third of the available height and the Person View two thirds. Yes, that is roughly how I defined it. > The bottom bar > height will not shrink any smaller than this. I can change this with a single configuration parameter. > What controls the minimum height > of the bottom bar - default height of a gramplet? I notice the side bar's width > can be shrunk quite a way but not down to zero size. Again, I could easily change this. At the moment the minimum size of the sdiebar is set to the minimum size of the filter bar (as in v3.2). Nick. > It would be useful for > small devices to be able to shrink the height/width of both bars so that the > user can find the best size that suits their device. > > Thanks > > Gary > > > > > ------------------------------------------------------------------------------ > Protect Your Site and Customers from Malware Attacks > Learn about various malware tactics and how to avoid them. Understand > malware threats, the impact they can have on your business, and how you > can protect your company and customers by using code signing. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Gramps-devel mailing list > Gra...@li... > https://lists.sourceforge.net/lists/listinfo/gramps-devel > > > |