Implement Tableview as a Topicmap Type
Here is a brief overview on the topics we've discussed as requirements on how to implement the next tableview version as a Topicmap Type:
New Tableviews are created with the "Unified Search & Create Dialog" (as they are now) but with some subtle differences:
- The option to create a new
Tableviewwill not be part of the content topic types but shall be realized as an "Special Menu Item" (extraMenuItem)
- Using a dedicated
Optionscomponent (displayed when Tableview, extraMenuItem) was selected allows the user to directly (flexibly) choose another Topic Type which will become the so called "Table Topic Type" (see #26 (closed))
- The selection menu for the
Table Topic Typeshall allow text-input filtering across all Topic Type Names
Createthen will trigger a custom tableview creation logic (in the backend) which makes sure that simple child topic types on all levels of the selected
Table Topic Typewill be configured as
Table Column(see #26 (closed))
- The Tableview configuration will be persisted as in dmx–tableview-0.1.0 version (no changes must be made to this)
- The name for the given tableview is taken from the first input field in the "Unified search & create dialog"
Creatingthe new tableview map it shall become selected in the "Topicmap" selector and the Tableview map should be loaded successfully by the webclient in its default configuration
Topicmapscolumn is a default column which is to be rendered behind (at the end of) all (other) columns
All other configuration related requirements shall be part of separate ticket which is dedicated to make the column configuration much easier for end-users (following principles of direct manipulation).
This specification is regarfed as a functional `Tableview Topicmap Type" integration.