From 703058bd279e92a9ab8ebc4443749bf4394f26ab Mon Sep 17 00:00:00 2001 From: Alex Roitman Date: Mon, 11 Aug 2003 23:46:09 +0000 Subject: [PATCH] * TODO: Some nice features to implement, mostly from RFE at sf.net. svn: r1992 --- ChangeLog | 3 +++ TODO | 27 +++++++++++++++++++++++++++ 2 files changed, 30 insertions(+) diff --git a/ChangeLog b/ChangeLog index 125e05629..fbfc3426d 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,6 @@ +2003-08-11 Alex Roitman + * TODO: Some nice features to implement, mostly from RFE at sf.net. + 2003-08-11 Tim Waugh * src/docgen/OpenDrawDoc.py: Fixed tag mismatch. Added report printing support. diff --git a/TODO b/TODO index a20702f2b..cb075b725 100644 --- a/TODO +++ b/TODO @@ -1,3 +1,30 @@ +* History of navigation and the Back button. The RFE 747529, see + http://sourceforge.net/tracker/index.php?func=detail&aid=747529&group_id=25770&atid=385140 + asks for the Back button in the Family View, but it'd be more consistent + to enable it in all navigatable views (People, Pedigree, and Family). + We'd have to keep track of the active persons and enable Back-Forward buttons, + maybe even a history popup with the list of those people. Very similar to + browsers and, therefore, very useful and familiar to users. We already have + bookmarks and home button. + + As for the interface, we can have "Go" menu with Back, Forward, and + Home. Back and Forward can have down-arrow popups. Plus, all the views + can have Back and Forward in the context menus. + +* Remember where the images are added from (RFE 748974). This is actually + very useful when you add 50 new images -- navigating 50 times to the same + place is a nightmare. All that's needed is keeping track of a single + last selected directory and then point gtk.FileSellector there. + +* Presense of Notes for a person/event/whatever_else. RFE 747527 suggested + either a column in the People View or something like boldfaces "Notes" + tab title. I like the latter because it can be uniformly applied to + any notes, not only people's. Not so hard to implement. + +* Following the only child in a family view (RFE 750987). If there's a single + kid, an arrow should clearly follow this child, even if (s)he's not selected. + This is a minor thing and also should not be too hard. + * Allow for multiple notes. A tabbed interface would be really useful, since there are no titles for notes. Not all objects would necessarily need multiple notes. Determine which ones should and shouldn't.