The Following 5 Users Say Thank You to darethehair For This Useful Post: | ||
|
2009-05-29
, 20:22
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#2
|
vitasam:
1) I don't think my program supports Unicode -- at least I made no efforts to do so, unless it 'just works' by accident
2) Yes, I am familiar with GRAMPS. I made my best efforts to support basic GEDCOM reading/writing, which (as you probably know) is the standard exchange format for genealogical data. I would assume that GRAMPS can use/import GEDCOM data in that case (?). Check the README file for everything that I have to say about 'MGedcom'. Originally, it was my intent just to develop a GEDCOM 'reader', but with a lot more effort I tried to turn it into a 'writer' as well -- for the express purpose of being able to use it as a 'field data editor' as you mention. You will need to try it to see if I have succeeded
I suggest that you move this conversation to the 'MGedcom' thread instead of this one.
The Following User Says Thank You to For This Useful Post: | ||
|
2009-05-31
, 20:51
|
|
Posts: 273 |
Thanked: 104 times |
Joined on Mar 2007
@ Manitoba, Canada
|
#3
|
The Following User Says Thank You to darethehair For This Useful Post: | ||
|
2009-05-31
, 21:15
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#4
|
vitasam:
I have done a small amount of reading re: UTF-8 and Unicode, but it is too early to say whether I have the skills required to integrate that into MGedcom or not. What might be useful would be a working sample of your 'Russian' GEDCOM file (?)..
The Following User Says Thank You to For This Useful Post: | ||
|
2009-05-31
, 21:25
|
|
Posts: 273 |
Thanked: 104 times |
Joined on Mar 2007
@ Manitoba, Canada
|
#5
|
The Following User Says Thank You to darethehair For This Useful Post: | ||
|
2009-05-31
, 21:30
|
Guest |
Posts: n/a |
Thanked: 0 times |
Joined on
|
#6
|
vitasam: I have sent you a private email with my private email address
The Following User Says Thank You to For This Useful Post: | ||
|
2009-06-02
, 12:15
|
|
Posts: 273 |
Thanked: 104 times |
Joined on Mar 2007
@ Manitoba, Canada
|
#7
|
By the way. Am I correct, that unicode (or utf-8) is a default encoding table of Maemo platform?
The Following User Says Thank You to darethehair For This Useful Post: | ||
|
2010-01-10
, 04:42
|
Posts: 4 |
Thanked: 3 times |
Joined on Dec 2009
|
#8
|
The Following 2 Users Say Thank You to jam For This Useful Post: | ||
|
2010-01-10
, 04:52
|
|
Posts: 1,684 |
Thanked: 1,562 times |
Joined on Jun 2008
@ Austin, TX
|
#9
|
The Following User Says Thank You to epage For This Useful Post: | ||
|
2010-01-10
, 19:04
|
|
Posts: 273 |
Thanked: 104 times |
Joined on Mar 2007
@ Manitoba, Canada
|
#10
|
darenthehair or others: Does MGedcom run on the N900? Any special tricks or cautions?
The Following User Says Thank You to darethehair For This Useful Post: | ||
Tags |
genealogy, maemo 4 |
Thread Tools | |
|
Two older threads inquired about the availability of 'genealogy' apps for the Nokia Internet Tablets:
http://www.internettablettalk.com/fo...ead.php?t=6066
http://www.internettablettalk.com/fo...ad.php?t=18438
After completing my Python-based 'astronomy' apps, I wanted to continue my Python 'education' by attempting another app based on my hobbies/interests: a GEDCOM reader/writer -- named 'MGedcom' (another 'boring' name following the naming system that I had been following). It is at the bottom of my software page:
http://darethehair.googlepages.com/software.html
The page has some screenshots, as well as a link to the README file for it.
As always, there are a zillion disclaimers. The biggest one is that you should *not* trust my app to manipulate your GEDCOM files with 100% perfection (actually, a lot of *other* genealogy apps also have the same warning!).
What did I learn this time around? Mostly how to do 'tables' (using PyGTK 'treestores') and 'menus'.
To get the most out of this app, you will also need to install the port I did for 'Graphviz', also listed on the same page -- but this is only needed if you want to draw/view a 'graph' of people/family relationships. Actually, I find the nested 'table' approach already quite intuitive for doing this...
As always, I *crave* feedback comments
There is nothing more dangerous than a bored cat.