On Fri, Apr 24, 2009 at 4:01 PM, Aaron R. Short <fuzzyfonzy@yahoo.com> wrote:

You are right, but we are also thinking about the library parts of GRAMPS. There may be parts that could be shared, especially after we get a nice separation between backend and frontend. In any event, this will come later, if it comes at all.


ah so like the gedcom handling but shouldn't just those pieces be taken out and made into site-package libraries? It seems heavy handed to make a different app that just wants to use a library of ours to have to install the whole app. Shouldn't a library be focused? ie one thing and one thing well. gramps does so many things that i'd think that seperating it out makes more sense... just a thought.

Yes, that's what I meant: there could be gramps libraries in site-packages, and the gramps app installed as we do now. This would make it easy, for example, to have a web-app that would re-use the libraries.


Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensign option that enables unlimited
royalty-free distribution of the report engine for externally facing
server and web deployment.
Gramps-devel mailing list