The way it would work it that a template for tables could contain a link to say, /edittable/TopicName/3, where the /3 denotes the 3rd table on the page. (Perhaps there is a better mechanism for identifying multiple tables?) The editor would list the rows and columns of the table. Each cell, row, or table could contain a check box for deletion or insertion along with an input field for text entry.

a more advanced table editor could use a file like twikicatitems.tmpl to define the content of each field and the cells for data entry. I suppose those tables would have to indentify their type when stored.

This topic and FormDataEntry could ultimately be combined into one by allowing the form data entry mechanism to be used to edit individual fields.

See also: FormDataEntry

-- JamalWills - 02 Aug 2001

ObAol. I'm looking for a way to use TWiki to maintain an inventory and service history for a set of servers, workstations, systems, etc. For initial setup, form-based entry would rock. In maintenance mode, a combination of automated and entered content is necessary. Using TWiki's search capabilities to summarize the data different ways would also be most useful.

-- KarstenSelf - 14 Mar 2002

Karsten: You could define a form defining the fields required by your application. Then you could create new named entries or unnamed entries as individual topics. BugReport and Sandbox.ItemToDo are examples for named entries. You can create unamed entries by generating the topic name as a hidden field based on the time stamp, e.g. InventoryItem%SERVERTIME{"$year$mo$day$hours$min$sec"}% (InventoryItem20260126024616)

-- PeterThoeny - 17 Mar 2002

You may want to look at SimpleTableEntryUsingForms ...

-- ThomasWeigert - 02 Jun 2002

See EditTablePlugin