To address your specific point regarding the cheapness of a PC that can run GenoPro sure, you can get a cheap box, but I doubt that would appeal to the majority of Mac users who have bought an iMac because of its style. The reason this project sparks my interest is because I think GenoPro is the best program in its genre, and given I have some talent in developing Mac applications, I'd like to give it a shot. Embarking on this project isn't about just developing GenoPro Mac so I can avoid buying a PC box. I already have Virtual PC, and in fact I also have 7 Windows-based PCs too.
( this of course excludes the novlety of makeing your very own genopro for mac but im just useing the time cost money equation. I think that it would be much much cheaper to do that rather than spend time developing a mac client or even buying virtual pc for mac I'll take a look through the tag definitions dialog as you suggest.īut a pc that is capable of running genopro is not very expensive ( infact you can probably find one in a dumpster that will run it) It would make sense to follow your tag schema, and therefore make the files compatible. Thanks for that tip As it happens, the application I'm currently in the middle of uses XML, so I have a lot of that stuff buzzing around in my head. The XML tags are not documented yet, however you are welcome to use the Tag Definitions dialog (Menu -> Tools -> Tag Definitions) to get some basic documentation about each tag. You can use the GenoPro XML format if you want. Customers who wants to analyze their data will appreciate to have an XML format available to them. It turned out the XML format is used by customers to create third party tools, or integrate GenoPro with their database by storing the XML text directly in an SQL database. My original goal for XML was to have a backup file format so I can upgrade the internal data structure of the. I would recommend to have an XML import/export right from day one. For details about Unicode, please visit in the section "Unicode".Ģ. Make sure your program can support Unicode text. Your tool will be a great asset for the genealogy community.ġ. I am sure there are lots of users who will be happy to find a good genogram software for Macintosh. If you do a good job, I will put a link to your site. Obviously, I also have no intention of copying the idea, look & feel of GenoPro onto the Mac without your blessing. I am writing this so you know a bit what is ahead of you. If you already have a full-time job to earn your living, you will have little spare time, and after working a full day, the propensity to relax and enjoy life is usually higher than working another 4 to 5 hours of work on another project. Without fundings, you will have to do your programming during your spare time. I have been working full-time on GenoPro for the past 5 years, so you must have a source of fundings, either from your savings, or from someone willing to invest, or from sales of your product (like GenoPro currently does). This means I typed at least 8 million characters to create 8 MB of source code.ĭeveloping software is a full-time commitment. The report generator has more lines of code than this. GenoPro has 220,000 lines of C++ code on 515 files totalizing over 8 MB of source code. For instance, the Table Layout is a mini spreadsheet with over 30,000 lines of code. gno file, undo / redo, copy & paste, that constitutes the bulk of the coding. It is all the stuff behind, such as saving & loading the. The drawing of the genealogy tree / genogram does not require much coding. I am quite open minded, so I will give you a few hints. With the software emulators such as VirtualPC (, ) it is possible to run GenoPro on a Macintosh anyway. I would rather add new features to GenoPro and/or translate GenoPro into other languages ( French, Spanish, Italian, German, etc) than re-writing GenoPro for the Macintosh. I understand there are a lot of Mac users and the likelihood of native version of GenoPro for Macintosh is slim to none.