Meeting 2010-09-03

• attendees: rvh, cmot, jjc, ybe, pkl, nks, bdu, ckru, jes, haf, mmu, chsch, schm (via phone)
• author: ybe

Topics

• cmot, jes: Representation and simulation of state machines in KIELER demo
• mmu: KiVi? demo
• miscellaneous

Representation and simulation of state machines in KIELER (cmot, jes)

• rvh: Are there any similarities to the work of chsch?
• problems with the automatic layout
  • Representation of large labels -> consider using line breaks in labels
• parallel transitions are not executed parallel
  • Is the execution order deterministic?
  • user have to choose execution order himself -> an appropriate representation in the model would be nice.
• dependencies: Mould, Papyrus
• platforms: Linux, MacOS, Windows

KiVi? demo (mmu)

• at this point no automatic layout at window resize -> consider using a window listener etc.
• consider using another color gradient in simulation steps (now: dark blue -> black)
  • consider offering the user a configuration interface for highlighting: #1157
• computation time for large data components takes too long (any number of backward simulation steps is intended)
  • consider using a copy of the data pool -> but we don't want to store any redundant data
  • consider using a configurable cache for an appropriate number of backward steps
• access to the View Manager preferences (general consideration)
  • to use eclipse standard solution or to use an extra build "preferences" button -> the eclipse standard is more user friendly and intuitive
  • use recent preferences list: #1158
• consider hiding the Execution Manager during simulation process, only the play buttons are needed. POSSIBILITIES:
  • provide extra play buttons in the menu bar
  • use a simulation perspective providing model editor, Execution Manager and data table
    • use extension point in the Execution Manager or extra burron in the menu bar for the perspective
  • consider using an extension point providing Execution Manager -> View Manager communication
• general considerations for using zoom-to-fit, component based zoom, etc. in large models during simulation
  • possible use of focus representation or context representation (both structure based or semantics based), e.g. simulation focus on a given region
  • focus and context may be adjustable via preferences
  • perhaps use case specific
  • consider offering use case specific perspectives for structure-based editing
  • Consideration: First zoom and then layout or vice versa?
    • possible use of ordering compute layout -> zoom -> do layout
    • configuration possibilities may be provided from the view management layer
• consider extending SC in order to provide information about transient states

Miscellaneous

• next KIELER release scheduled for late October
• schm requested Oberseminar presentation recordings (rendering and view management desired)
• consider DVD-recorder acquisition