in Dakar SVN is from 10 Dec 2005 and was based on a version from 05 Mar 2005.
The version from TWiki.org is 16 Sep 2004.
Several updates and features have been missed.
The result is that quite many TWikApplications
fail when upgrading to Dakar because EditTablePlugin
is very popular. For example radio buttons are heavily used.
The version from Twiki.org should be put on SVN and the CSS update applied to it.
Forgot to select Extension field
I compared the Twiki.org version and the SVN version.
The SVN version is totally out of date. There is a factor 10 more code in the TWiki.org version. I tried to compare the two to see if it was easy for me to patch the changes done on the SVN version to the TWiki.org version but the TWiki.org version is a complete rewrite. The TWiki.org version also uses one of the deprecated handlers. So this is way above my skill level.
Did you mean "The version from TWiki.org is 16 Sep 2005
"? I'm confused.....
According to svn log, the most recent synchronisation was:
r4975 | maphew | 2004-05-06 21:29:55 +0100 (Thu, 06 May 2004) | 4 lines
*non-maintainer update* synchronized with released zip version, which was ahead of the cvs version
Internal plugin version: 07 Apr 2004
Zip version: 1.20 (http://twiki.org/cgi-bin/viewfile/Plugins/EditTablePlugin?rev=1.20&filename=EditTablePlug
So the CVS version must have been really old.
The SVN version lacks this changes.
| 16 Sep 2004
|| Added radio buttons and checkbox controls; escaped "|" pipe symbol found in input fields to preserve tables
And it is pretty important because it is a major feature enhancement. Both radio buttons, checkbox controls are heavily used - and quite smart in a TWiki App I may add.
On the SVN version these two changes have been made.
So it is not that trivial a merge to do. But since this is one of the essential plugins it should be done before release. I can do a lot of testing of it the next days if the merge is done to make sure the result is robust.
OK, I merged in the changes from the zip. Note that there doesn't seem to be any kind of tests for the plugin, even in the plugin topic; it might be an idea to generate a suitable test topic to make future merges easier.