wiki:Meetings/Meet-2010-05-10

KIELER Meeting 2010-05-10

  • begin: 10:15 AM
  • end: 12:05 AM
  • moderator: haf
  • participants: abl, bdu, ckru, cmot, chsch, haf, jjc, mmu, mri, msp, nks, pkl, rvh, tam, (11:50 AM: mhei)
  • author: bdu

KEX

  • pkl briefly introduces KEX: KIELER example management

KIELER release

  • compatibility problem with Papyrus
  • but works with compiled plugins

repair functions for synccharts (soh)

  • tam: older synccharts not compliant to latest KIELER version because of errors, e.g. zero priority
  • repair functions: assign new priority to transitions etc.
  • if you have inconsistant old Synccharts that you want to use with the latest KIELER version, then you can use a plugin to correct them syntactically. The plugin will be available soon.
  • haf proposes that soh should hold a demonstration about the features

meta data for plugins (msp)

  • msp: see new page in KIELER wiki: KIELER software practice: plugin metadata guidelines
  • a lot of information stored in files: MANIFEST.MF, plugin.xml etc.
  • check your plugins if they are compliant to guidelines
  • chsch: dependencies: don't specify version numbers in dependencies!
  • msp: version numbers are used for compatibility check
  • version numbers pose a complex problem: we should specify min and max compatibility
  • haf: readjust version numbers for dependencies with every release.
  • haf: we don't need downward compatibility to Eclipse
  • xtext: problems because we are using beta version
  • haf: we actually need a long-term release manager

highlighting conventions for synccharts (mmu/tam)

  • how should terminal state be highlighted?
  • mmu: inconsistency Ptolemy vs. SC simulator
  • in Ptolemy simulator: terminated thread remains highlighted
  • in SC simulator: terminated thread not highlighted
  • SC simulation not working on Mac --> assign ticket to tam (#851)
  • tam: after a simulated thread has terminated in the SC simulator, it cannot be highlighted in the next step
  • rvh proposes: introduce different categories of states for simulation/view management:
    • inactive state
    • in state (in ABRO: wA)
    • entering state (via transition highlight)
    • transient (conditional)
    • thread dead
      • last active (dA/dB)
      • parent active
      • history
  • make it configurable

KViD poll evaluation (jjc)

  • jjc has conducted a poll on the design of KViD
  • jcc presents question set, results, possible approach
  • usability vs. generality
  • graphical displays, e.g. tachometers?
  • keep display data persistantly?
  • intuitive display? Labels, popups or other
  • measurement model: approach deprecated by the majority
  • statistics view: additional feature
  • haf: Ptolemy plot
  • haf: amount of visible data might cause performance issues
  • for compound labels: can eclipse labels have multiple colors/fontstyles?
  • msp: signal is a text label that can be used at different transitions
  • in data flow based editor it is different
  • make it general but ensure usability
  • bdu: Synccharts colors
  • haf: colors should be configurable
  • view management
    • rvh: view management should provide basic functionality, e.g. set transition color
  • popup like in Eclipse debug view
  • filter mechanism for irrelevant values