wiki:Meetings/Meet-2011-01-12

KIELER Meeting 2011/01/12

  • Moderator: haf
  • Protocol: cds
  • Attendees
    • cds
    • chsch
    • ckru
    • cmot
    • haf
    • hdw
    • jes
    • mri
    • msp
    • soh
    • uru
    • rvh
  • Start: 10:00h
  • End: 11:20h

Agenda

  • A Short Survey of Automatic Layout in Ptolemy (cds)
  • Submission to DATE University Booth (rvh)
  • IEditingPart (msp)

A Short Survey of Automatic Layout in Ptolemy (cds)

  • See attachments for the presentation.
  • Slide 11: Request: Add an option to force inputs on the left and outputs on the right. (ticket #1381)
  • Slide 13: Ptolemy does left alignment of actor names. This is not compatible with centered alignment of the layouter.
    Request: Introduce option to layouter to do left alignment. However, this would still be sub-optimal, in particular if the left ports have labels. (ticket #1382)
    Problem: Currently, Ptolemy does not allow to retrieve the bounding box of just the actor. The bounding box computed by Ptolemy always includes the labels. This is right for computing how much space an actor needs, and to allow to route edges around labels. However, it does not allow to do actor alignment relative to the actor (without labels).
    Request: Add to Ptolemy the option to return bounding box without labels. This could perhaps be done by cmot during his next visit to UCB.
  • Slide 16: Placement of comments - this is a very important aspect of automatic layout. The question is whether this could / should be done in the context of cds-dt.
    Could use heuristics that associates upper left corner of bounding box of comment to nearest actor. Perhaps users will also get used to place comments with such an automatic layout heuristics in mind.
  • People seem to have used the wrong layout; how did it come to that?? (ticket #1383)
  • some results at Meetings 2011-01-19

Submission to DATE University Booth (rvh)

IEditingPart (msp)

  • KIML core is now independent of the editing framework used (Graphiti, GMF). This is desirable for multiple other parts of KIELER as well. To this end, msp has introduced IEditingPart. This interface can be used to access multiple editing frameworks through the same interface.
  • Arguably most useful method: EObject getElement(Object), which retrieves the model object from a selected object (usually an EditPart).
  • Request: Why does getEditingDomain(Object) return a TransactionalEditingDomain instead of a simple EditingDomain? Either change that or give a plausible reason. (ticket #1384)
  • Request: Make getEditPart(Object) return EditParts for model objects as well. (ticket #1385)
  • Request: Create a central editing provider service that returns an IEditingProvider implementation for a given editor or edit part. (#1386)
  • Request: Change the name of IEditingProvider to IGraphicalFrameworkBridge. (wins against IGraphicalFrameworkAccess by 7 to 2 votes, with 2 abstentions) (ticket #1387)

Attachments