Porting PGV to Firebird ...

2013-07-06
2013-07-07
  • Lester Caine

    Lester Caine - 2013-07-06

    Not sure that the 'send email to create new thread' link is actually working so I will try again online :)

    The other post that has not appeared asked when webtrees was forked from the PGV code base. I've identified that now as 18/2/2010 and this ties up with CS5985 in webtrees mirror against CS6804 on the phpgedview mirror, and I can work from that.

    I've also reworked my firebird codebase so that it is documented in a branch of the phpgedview mirror so I can use the Hg tools to manage future work and identify the existing patches. The bottom three items on http://lsces.org.uk/hg/ give the current state of play with the firebird port, along with an hg mirror of the phpgedview SVN and the webtrees SVN, so have everything in one place.

    My own plan has always been to use pgv as the base for a module in our bitweaver framework, http://lsces.org.uk/hg/Bitweaver%20Mirror/phpgedview/ is now well out of sync with things, but does provide an installer to create the pgv database on any engine, and I anticipate that the forked code should work with oracle and postgres in addition to firebird, so it may be worth getting that running stand alone initially, skipping the earlier MySQL database versions and going straight for a current schema.

    I will look to see if webtrees offers anything, but I suspect that it's gone off at a tangent to the sort of framework I prefer, using smarty templates and a modular display structure defined by bitweaver. Certainly I can't stand Zend methods, and will switch to a more easily understood structure. Bitweaver provides a CMS framework for wiki/blog/article/forum/gallery and many specialist add-ons that provide additional information management.

     
  • Gerry Kroll

    Gerry Kroll - 2013-07-07

    There have been no changes to the database tables and structures since webtrees forked from PGV.

     
  • Lester Caine

    Lester Caine - 2013-07-07

    I'm not so bothered by the database schema, it's the poor choices of bulk changes to the code which make the webtrees code difficult to use as a source. I use beyondcompare for comparing code bases, but even it is having trouble with the change from docblock comments to single line ones. That said, it is interesting how much of the original code remains, so merging the cross database stuff may not be out of the question, but I need phpdocumentor back which webtrees has ditched :(
    That is why I will remain with the phpgedview base for the time being.

     
    Last edit: Lester Caine 2013-07-07

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks