Cyclone-Team/gramps
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

* TODO: Some nice features to implement, mostly from RFE at sf.net.

Browse Source 
svn: r1992
This commit is contained in:
Alex Roitman 2003-08-11 23:46:09 +00:00
parent e4c6227dc8
commit 703058bd27
2 changed files with 30 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
ChangeLog
View File

@ -1,3 +1,6 @@
2003-08-11 Alex Roitman <shura@alex.neuro.umn.edu>
* TODO: Some nice features to implement, mostly from RFE at sf.net.
2003-08-11 Tim Waugh <twaugh@redhat.com> 2003-08-11 Tim Waugh <twaugh@redhat.com>
* src/docgen/OpenDrawDoc.py: Fixed tag mismatch. Added report printing * src/docgen/OpenDrawDoc.py: Fixed tag mismatch. Added report printing
support. support.

27
TODO
View File

@ -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, * Allow for multiple notes. A tabbed interface would be really useful,
since there are no titles for notes. Not all objects would necessarily since there are no titles for notes. Not all objects would necessarily
need multiple notes. Determine which ones should and shouldn't. need multiple notes. Determine which ones should and shouldn't.