At 20:29 +0000 1/7/15, Gerry Kroll wrote:
If a new user of PhpGedView asks for help, I'll try to steer them
towards Webtrees as being a better-supported alternative. However,
I'll stick with PhpGedView for my own site and for a couple of
others that my server is hosting. I've been using PhpGedView since
2003, and I know the program quite well. I'd rather not start
learning the ins-and-outs of Webtrees or some other alternative when
PhpGedView does what I'm asking it to do.
It's not so much the learning curve, it's the ways you can use
PhpGedView that Webtrees won't do. Primarily, in PGV you can easily
use different data selections in different browser tabs. Webtrees
must communicate the desired view by cookie rather than in the url
because if you select a data view for one tab and then follow a
person link from another tab that has a different data selection then
the loaded page will follow the view selected for the first tab
rather than continuing to re-use the selection for the second. You're
constantly re-selecting the data views of tabs to what you want them
to be and any page refresh knocks it out again.
David
--
David Ledger - Freelance Unix Sysadmin in the UK.
david.ledger@ivdcs.co.uk
www.ivdcs.co.uk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At 20:29 +0000 1/7/15, Gerry Kroll wrote:
If a new user of PhpGedView asks for help, I'll try to steer them
towards Webtrees as being a better-supported alternative. However,
I'll stick with PhpGedView for my own site and for a couple of
others that my server is hosting. I've been using PhpGedView since
2003, and I know the program quite well. I'd rather not start
learning the ins-and-outs of Webtrees or some other alternative when
PhpGedView does what I'm asking it to do.
It's not so much the learning curve, it's the ways you can use
PhpGedView that Webtrees won't do. Primarily, in PGV you can easily
use different data selections in different browser tabs. Webtrees
must communicate the desired view by cookie rather than in the url
because if you select a data view for one tab and then follow a
person link from another tab that has a different data selection then
the loaded page will follow the view selected for the first tab
rather than continuing to re-use the selection for the second. You're
constantly re-selecting the data views of tabs to what you want them
to be and any page refresh knocks it out again.
David
--
David Ledger - Freelance Unix Sysadmin in the UK.
david.ledger@ivdcs.co.uk
www.ivdcs.co.uk
Re: [phpgedview:discussion] Cross site scripting vulnerability
It's not so much the learning curve, it's the ways you can use
PhpGedView that Webtrees won't do. Primarily, in PGV you can easily
use different data selections in different browser tabs. Webtrees
must communicate the desired view by cookie rather than in the url
because if you select a data view for one tab and then follow a
person link from another tab that has a different data selection then
the loaded page will follow the view selected for the first tab
rather than continuing to re-use the selection for the second. You're
constantly re-selecting the data views of tabs to what you want them
to be and any page refresh knocks it out again.
David
--
David Ledger - Freelance Unix Sysadmin in the UK.
david.ledger@ivdcs.co.uk
www.ivdcs.co.uk
Thanks for this elucidation. It will lead me to a more careful road of preparing the migration to Webtrees.
Paul & Anja Seesink-van der Pluijm
Website genealogie: http://www.seesink-vanderpluijm.nl/