Ticket #104 (closed Enhancement: fixed)
Nested content panel rendering
Reported by: | jri | Owned by: | jri |
---|---|---|---|
Priority: | Major | Milestone: | Release 4.1 |
Component: | DeepaMehta Standard Distribution | Version: | 4.0.4 |
Keywords: | Cc: | ||
Complexity: | 3 | Area: | GUI |
Module: |
Description
The content panel's rendering should reflect the type-specific hierarchy that underlies each topic. E.g. Person -> Address Entry -> Address -> City
This is an issue in particular with the "many"-cardinality. E.g. a person has *many* Address Entries. Each one is a composite unit.
Change History
comment:2 Changed 13 years ago by Jörg Richter
Begin of "Nested content panel rendering" (#104).
Change Field Renderer framework:
A field renderer constructor got only one parameter: "field_model" (a FieldModel? object).
The former "topic" parameter is accessible as field_model.toplevel_topic
The former "rel_topics" parameter is dropped.
Add "interface" FieldRenderer?.
It will provide default method implementations and serves for documentation purposes.
Add to webclient.css: box styles for each nesting levels.
No visible results yet.
See ticket 104
comment:3 Changed 13 years ago by Jörg Richter
Webclient: nested content panel rendering (#104).
The content panel visualizes the composite structure as nested boxes, filled with a distinct color for each nesting-level.
Change Field Renderer contract:
- The render_field() method gets a "parent_element" and is responsible for rendering into that. At calling time the parent_element is already part of the DOM.
Nothing is to be returned.
- The same applies to the render_form_element() method.
- The post_render_form_element() method is dropped.
See ticket 104
comment:4 Changed 13 years ago by jri
- Status changed from new to closed
- Resolution set to fixed
Complete in nested-panel branch.
comment:5 Changed 13 years ago by Jörg Richter
Begin of "Nested content panel rendering" (#104).
Change Field Renderer framework:
A field renderer constructor got only one parameter: "field_model" (a FieldModel? object).
The former "topic" parameter is accessible as field_model.toplevel_topic
The former "rel_topics" parameter is dropped.
Add "interface" FieldRenderer?.
It will provide default method implementations and serves for documentation purposes.
Add to webclient.css: box styles for each nesting levels.
No visible results yet.
See ticket 104
comment:6 Changed 13 years ago by Jörg Richter
Webclient: nested content panel rendering (#104).
The content panel visualizes the composite structure as nested boxes, filled with a distinct color for each nesting-level.
Change Field Renderer contract:
- The render_field() method gets a "parent_element" and is responsible for rendering into that. At calling time the parent_element is already part of the DOM.
Nothing is to be returned.
- The same applies to the render_form_element() method.
- The post_render_form_element() method is dropped.
See ticket 104
comment:7 Changed 13 years ago by Jörg Richter
Begin of "Nested content panel rendering" (#104).
Change Field Renderer framework:
A field renderer constructor got only one parameter: "field_model" (a FieldModel? object).
The former "topic" parameter is accessible as field_model.toplevel_topic
The former "rel_topics" parameter is dropped.
Add "interface" FieldRenderer?.
It will provide default method implementations and serves for documentation purposes.
Add to webclient.css: box styles for each nesting levels.
No visible results yet.
See ticket 104
comment:8 Changed 13 years ago by Jörg Richter
Webclient: nested content panel rendering (#104).
The content panel visualizes the composite structure as nested boxes, filled with a distinct color for each nesting-level.
Change Field Renderer contract:
- The render_field() method gets a "parent_element" and is responsible for rendering into that. At calling time the parent_element is already part of the DOM.
Nothing is to be returned.
- The same applies to the render_form_element() method.
- The post_render_form_element() method is dropped.
See ticket 104