wiki:Meetings/Meet-2010-11-03

Minutes of Meeting 3.11.2010

attendees: rvh, haf, msp, cmot, mri, chsch, soh, mmu, pkl, ckru, ... protocol by: soh

  • rvh reports about worst case execution time analysis project (OTAWA)
    • analysis of control flow graph
    • use in viewmanagement? (added to list of bachelor/master projects)
  • state of release?
    • KEX:
      • not integrated into nightly build yet, chsch will take care of it
      • already added synccharts/kaom examples
      • still need to add esterel examples
      • explain to group how to add examples in next meeting
      • who is author of examples? support mail-address? ifi-account, forward to multiple (haf)
    • roadmap:
      • review tickets for which milestone (haf, cmot, msp)
    • Papyrus:
      • cmot: don't release, no hierarchy possible, release at a later date
      • haf: only usuable UML editor atm
      • release at 0.4.1 when Papyrus group releases new version
    • Ptolemy:
      • release full instead of tiny
      • state of layout in ptolemy? only a few minor bugs remaining, some on ptolemy side
    • msp will take care of release
  • hooks
    • automatic rejection of files where end-of-line style/mime-type not set by svn
    • annoying on files generated by workflow/other generated codes
    • remove checkstyle warning "newline at end-of-file" (haf)
    • only check mime-type for relevant files? Only check for .java/.c/.html/.xml (tig)
  • highlighting of states possible by changing fill color through appearance tab of properties view
  • metalayout presentation by msp
    • diagram <-> KIML <-> algorithm
    • layoutoptions, use of kgraph
    • different possibilities to set layout options
    • structure of 3 different stores for layout options, integrate all new options into that structure
    • used in viewmanagement when one layout should be done with specific options but no need to store them
    • on the fly layout configuration
    • integrate graphitti by implementing layout manager
    • set layout options through kivi (persistent and on-the-fly)
    • use annotations only when nothing is set in diagram