Difference between revisions of "User:BACbKA"
(→My GRAMPS-related scratchpad) |
(→My GRAMPS-related scratchpad) |
||
Line 13: | Line 13: | ||
* (This is a known hot issue, see [[How_you_can_help#Web_2.0]]) | * (This is a known hot issue, see [[How_you_can_help#Web_2.0]]) | ||
** can we send out only the stuff that changed? (yet another multisync sub-problem) | ** can we send out only the stuff that changed? (yet another multisync sub-problem) | ||
+ | * Language-aware date display with inflections #{{bug|6926}} -- probably should use http://www.grammaticalframework.org/ for a completely new DateDisplayer/DateParser/libnarrate!!! | ||
* we need a feature usage stats tracker, there's lots of obscure features that probably aren't used much, but contribute to overall complexity. E.g., should we cut some of the report backends? | * we need a feature usage stats tracker, there's lots of obscure features that probably aren't used much, but contribute to overall complexity. E.g., should we cut some of the report backends? |
Revision as of 15:37, 16 September 2013
- merge familylines and relgraph good stuff into a common report
- auto-translation of names, places, etc. - for reports and exports
- and events! see bug #725
- reports & export should have more in common -- in filtering/selecting source set and output data
- new action - filter, expose for cli?
- see also bug #1600 and Filtered_Reports
- what is the best practice for collaboration with other active researchers? Is there a tutorial? Should gramps collab with multisync @sf? or some DVCS? Obvious use cases:
- two (or more) people using GRAMPS. Each wants to be the master of his own DB and vet anything incoming.
- make life easy for people taking periodic exports from gramps
- (This is a known hot issue, see How_you_can_help#Web_2.0)
- can we send out only the stuff that changed? (yet another multisync sub-problem)
- Language-aware date display with inflections #6926 -- probably should use http://www.grammaticalframework.org/ for a completely new DateDisplayer/DateParser/libnarrate!!!
- we need a feature usage stats tracker, there's lots of obscure features that probably aren't used much, but contribute to overall complexity. E.g., should we cut some of the report backends?
Dev bookmarks
- Cairo Tutorial for Python Programmers, by Michael Urman
- python-cairo v3 docs
- pygtk docs slightly outdated wrt the trunk env, e.g., pango.Layout.set_text() doesn't list the mandatatory second argument for string length on my system... python help(pango.Layout.set_text) is the final authority!..