Changes between Initial Version and Version 3 of Ticket #315


Ignore:
Timestamp:
03.09.2013 16:09:21 (11 years ago)
Author:
jri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #315

    • Property Status changed from new to accepted
    • Property Cc JuergeN added; joern, tsc removed
    • Property Summary changed from Topic Renderer: make the "Associations" listing optional to Webclient: more user friendly page panel rendering
    • Property Milestone changed from Release 4.1 to Release 4.2
  • Ticket #315 – Description

    initial v3  
    1 The plugin developer could configure this by manipulating the page model via the "pre_render_page" event. 
     1Currently the page panel (right side) lists a lot of information twice. This is because all the topics backed by the selected topic's ''schema definition'', as rendered in the **upper area**, appear another time in the ''schema less'' Associations listing ("what's related?"), as rendered in the **lower area**. This results in a cluttered page panel with a lot of redundancy and user unfriendly computer jargon appearing in the UI ("Aggregation", "Composition", "Instantiation"). 
     2 
     32 measures are proposed: 
     4- Fixed rule: do not render a topic in the Associations listing if the topic appears already in the upper area (schema defined). 
     5- Programmatic configuration: a plugin developer could suppress the entire Associations listing. She could do so by manipulating the page model via the "pre_render_page" event. 
     6 
     7Open question: 
     8- Should the "what's related" Associations listing be grouped by ''Association Type'' (as it is currently) or by ''Topic Type''? Advantage of the latter would be the computer jargon ("Aggregation", ...) to disappear from the UI. This is because Association Type Names are rather technical while Topic Type Names rather origin in the user domain. However, it seems there is no "right" decision per-se as it depends on the respective application data model.