wiki:Meetings/Meet-2011-02-02

KIELER Meeting 2011/02/02

  • Moderator: haf
  • Protocol: mri
  • Attendees: chsch, msp, rvh, cmot, haf, mri, cds, ckru, uru, soh, hwe, jes
  • Start: 10:00h
  • End: 12:05h

Table of Contents

  • Annotations, Layout algorithm selection (msp)
  • KAOM Poster (cmot)
  • Project names (conventions) (cds)

The KAOM poster (first draft) (cmot)

  • msp: Viewmanagement focus on hierarchy (comparison to ptolemy)?
    • KIELER concept overview should be present on the poster, hierarchy aspect elsewhere
  • rvh: in general less text instead simple messages and diagrams
  • haf: visualization table in center image is not really good for demonstration (technical)
    • instead show traffic light visualization
  • reduce size of toolbar and data views on center image, focus on editor
  • switch 'Automatic Layout' and 'Meta Modeling' boxes
  • msp: text should not hint features which don't exist (but are possible)
    • e.g. rendering of LabVIEW is possible but not implemented yet
    • this should be made clear
  • image backgrounds transparent? not enough contrast?
  • comparison to older poster: transparent image backgrounds provide sufficient contrast

Demonstration of the Annotations tab in the properties view (msp)

  • visible for KAOM and SyncCharts? editor
  • view, delete, edit and add annotations of different types
  • adding support for the tab to a different editor involves adding extension point data

Demonstration of the layouter selection dialog (msp)

  • dialog shows a tree view of all available layouters in categories
  • a filter can be specified to shorten the tree and search for layouters
  • are the shown graphs sufficient to provide a quick overview over the specific algorithms functionality (e.g. the 'Mixed-Upward-Planarization' is good for class diagrams, the image doesn't hint this)?
  • it would be nice to be able to apply the selected layouter directly to the diagram without closing the dialog

Discussion about problems with setting up an environment using KIELER (started by cds)

  • checking out all plugins works but is not sufficient for systems with limited resources (netbooks)
  • hard to maintain an overview over the plugin dependencies