This is a good idea, but you're right --- wait until the improved version is ready.
The user who wishes to invoke this feature would need "Edit" rights. Also, it might be a good idea to make this feature available only when a new GEDCOM option (similar to Autocomplete) allows it.
I notice that line 49 of the edit_merge.php script is checking the wrong user permission. "Accept", which the script is looking for, does not imply "Edit". Merging of records is clearly an Edit function.
You ask about plans for jQuery. There are no plans for this, unless you wish to take on this project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@Leonhard
Please explain how this change will improve the user's experience of PhpGedView.
If it's easier for you, you can reply in German.
Leonhard:
The PhpGedView community needs your explanation of how this patch will make PhpGedView more useful.
The patch won't appear in the SVN repository without your description. A detailed description is not required -- a "management overview" will suffice.
With this javascript edit_merge.php will be invoked by drag and drop one link (to an individual or family) onto another one.
but i'm working on an improved version, which will be loaded only when a user is allowed to merge records.
Any hints where to include jQuery? Are there any plans to use jQuery generally?
This is a good idea, but you're right --- wait until the improved version is ready.
The user who wishes to invoke this feature would need "Edit" rights. Also, it might be a good idea to make this feature available only when a new GEDCOM option (similar to Autocomplete) allows it.
I notice that line 49 of the edit_merge.php script is checking the wrong user permission. "Accept", which the script is looking for, does not imply "Edit". Merging of records is clearly an Edit function.
You ask about plans for jQuery. There are no plans for this, unless you wish to take on this project.