| @@ -1,7 +1,7 @@ |
| -++yellow:This package is currently undergoing a rebuild using the latest version of phpgedview, so the notes at [http://lsces.co.uk/wiki/index.php?page=Port+of+phpgedview+back+to+ADOdb|my site] for more details of the problems.++
|
| +++yellow:This package is currently undergoing a rebuild using the latest version of phpgedview, the notes at my site have disappeared, and I'm not quite sure where they went. The 4.2.2 PGV codebase is now synced with the phpgedview package, and installs - downloads a GEDCOM and provides a few navigation pages. It is probably back to the same level of functionality it had with the PGV3 code and still needs a number of major sections porting to the smarty template structure. But it is stable currently and has most of the user authentication provided by BW now. ++ |
|
|
| !Genealogy Management
|
| -My current genealogy mamangement is via the phpGedView software which allows a comprehensive way of managing the GEDCOM files created using a range of genealogy tools.
|
| +My current genealogy management is via the phpGedView software which allows a comprehensive way of managing the GEDCOM files created using a range of genealogy tools. |
| {img src=http://www.phpgedview.net/header.png link="http://www.phpgedview.net" width=380 height=86 align=centre}
|
| !!phpGedView 4 updates
|
| The latest builds of phpGedView still did not support Firebird, but at least the enabling of Firebird in Pear:DB actually worked, and then I just had to sort out why the package was not working 'lower case' to the result sets. It turned out that I just had to modify the default setting to give ASSOC and lower case. This gave problems in a number of places where the package was looking for NUM result sets, but ASSOC overrides that. After a little playing the code all seems to be playing nicely with ADOdb in Pear mode, now I can look at stripping the config section and replacing it with the bitweaver opening sections.
|
|
|
| @@ -20,7 +20,7 @@ |
| !!Upgrade paths
|
| At the current time, the data I am working with can simply be re-imported into the new GEDCOM structure, but there is no reason why the upgrade mechanisim provided by bitweaver could not be used to import existing phpgedview data into the bitweaver version.
|
| !!Current Status
|
| -The installer will build the required tables, although the user table should be dropped at some point. Currently the login is handled by bitweaver, and so levels of access are managed from that. A group for viewing private data wil be sorted at some point, currently only an admin can see that ( I hope ). Downloading a GECOM can now be handled via the interface, but viewing it still uses the phpgedview templates.
|
| +The installer will build the required tables, and the pgv user table has now been dropped. Currently the login is handled by bitweaver, and so levels of access are managed from that. A group for viewing private data will be sorted at some point, currently only an admin can see that ( I hope ). Downloading a GEDCOM can now be handled via the interface, but viewing it still uses the phpgedview templates. |
| Next step is to start moving the admin stuff to the bitweaver admin sturcture and drop those interfaces that are not needed once a bitweaver/liberty version is available.
|
| Editing is via pop-up windows, and I am working on a short term fix to keep that and may well retain it later as it does provied a nice feel. Perhaps it can be moved to a liberty generic format.
|
| !!Reference Information
|
|
|