Feature Proposal: replace edit table plugin with edit row plugin

Motivation

EditTablePlugin's code dates back to the begining of twiki, and is a shocking mess of shocking code.

it is actually incompatible with twiki topics dating from 2004 (see http://foswiki.org/Tasks/Item11658 for one simple example), and in trying to fix it, I'm finding all sorts of hidden gotcha's.

Description and Documentation

Crawford has been working on EditRowPlugin for ages now, and today, I finally got this reply:

<CDot> the 401 was the last of the big nutcrackers
<SvenDowideit> is there any reason that you know of that ERP is not ready to replace ETP
<CDot> not that I know of
<SvenDowideit> excellent, then we have progress :)
CDot uses it exclusively; does not use EditTable at all

EditRowPlugin

Examples

Impact

WhatDoesItAffect:

%WHATDOESITAFFECT%

edit

Implementation

-- Contributors: SvenDowideit - 22 Mar 2012

Discussion

+1. ERP is great

-- PaulHarvey - 28 Mar 2012

this is now done, all that remains is to find and squash bugs - in a separate task.

-- SvenDowideit - 18 Apr 2012

Does EditRowPlugin do everything EditTablePlugin does? Or will EditTablePlugin still be recommended for older Foswiki's?

It would be nice to see unit tests that cover the spec and can be ran on both plugins, though I appreciate thats a lot of effort...

-- AndrewJones - 18 Apr 2012

yes, EditRowPlugin is a superset of EditTablePlugin . any differences that are bad are considered a bug.

(it'd have to be selenium browser side integration tests - on an unwritten spec )

-- SvenDowideit - 18 Apr 2012