[AgileWiki] The Columns Ledger Section
Status: Beta
Brought to you by:
blaforge
From: Bill la F. <bil...@su...> - 2006-06-20 02:02:44
|
Now every rolon which has a table for its document content has a table descriptor unit assigned as its descriptor unit, where all table descriptor units have as their assigned descriptor unit, the TableDescriptorUnitDescriptorUnit. And there will be a lot of table descriptor units, one for every kind of table. Every table descriptor unit has a Ledger Section rolon named Columns. And the descriptor unit assigned to all Column Ledger Sections is always the ColumnsDescriptorUnit. (I'm getting a bit dizzy here, methinks.) Now the Columns Ledger Section is itself a table, so of course the descriptor unit assigned to the ColumnsDescriptorUnit is the TableDescriptorUnitDescriptorUnit. (Obviously, right?) But enough fun. There really is a point I want to make here... The Columns Ledger Section of every table descriptor unit has two (2) columns: ColumnName and BriefDescripton. Hey, that's a start, but I can think of two more columns that would be very helpful: Required and FieldType. Now there is a bunch of work to be done here. Sougata has already begun work on a table-based single-entry accounting system. And I've suggested to Niall that a table sort on a column would be useful. But there's much more. For example, we need a command for adding rows to a table. The form for this command would be composed using the information in the Columns Ledger Section. In addition to sorting on a column, we also need to be able to manually reorder rows. And we also need to be able to remove a row from a table, or edit the content of a row. Tables are very important here. They are used in the configuration of the AgileWiki, and will likely be central to most applications. And the good thing is that there is a very limited API that you need to use to work with tables. (Too many things required a very broad-based knowledge of the whole of the AgileWiki, but tables is not one of them.) Bill |