KIELER Meeting 02/09/2011
- Moderator: haf
- Protocol: cmot
- Attendees
- uru
- msp
- rvh
- ckru
- hdw
- cmot
- cds
- Start: 10:10h
- End: 12:25h
Agenda
- Attendance to KIELER meeting
- Dates
- Checkstyle Conventions
- (Comment) Layout Discusssion
- View Management Demo
Attendance
- RTSYS-Hiwi's should also attend to the Meeting
- E-Mail w/ CC to rvh
- (ticket#1441 haf)
Dates
- Oberseminar
- 25.03. (4 votes) [or 29.03. (3 votes)]
- E-Mail an RTALL (ticket#1442 rvh)
- Code Review URU
- haf, msp, uru
- 14.02., 10:00h, R1115
Checkstyle Conventions
- Hidden fields
-
public class MyBla { private int blubb public MyBla(final int blubb) { } public setBlubb(int blubb) { this.blubb = blubb; } }
- blubb hides a field Checkstyle warning
- Final rule enforces that we cannot write blubb = blubb
- Do we want underscores for member variables? (like in C++)
- No
- Is checkstyle able to detect:
- this.blubb = blubb; OK
- int blubb; NOTOK
- (ticket#1443 cds)
-
- Property Checkstyle Warning
- Do not check propery files
- Do this per project
- Is this possible to do this globally?
- (ticket#1444 cds)
- Decision: We do not adapt the Checkstyle rules
KARMA Demo (ckru, cds)
- Comments are connected to model elements using a very simple heuristics
- Heuristics: Spatially closest comments are attached to a model element iff within a given arc radius
- CI-domain/Router2.kaod seems to be broken
- Layout problem (GMF editor?)
- Comments missing (old model?)
- (ticket#1445 cds)
- LongRuns? model
- Interesting comment with line breakes
- Is correctly attached
- Comment boxes seem larger than necessary
- (ticket ckru)
(Comment) Layout Discussion
- Comments are currently not treated specially (msp)
- Comments should not be left to the connected nodes but above
- Use block layout for unconnected elements
- Priority based, give director highest priority, author-comment the second highest priority
- New hierarchy level for KGraph? (haf)
- Same holds for class diagrams (haf)
- Can the box layouter interpret layout preference annotations (maybe set during the import)? (cds)
- Special comment types (during import) (rvh)
- Eclipse View of internally computed layout should be reactivated (haf)
- 'Rule based layout' (vs. MENGES)
- Different styles (e.g., depend to the director) (rvh)
- This should be a special case for 'META LAYOUT' (msp)
- Generic semantic layout options
- How can this be connected to KIML and KIVI? (msp, haf)
- KIML are just special effects for KIVI (haf)
- Different KIVI combinations that MAY (or may not) configure KIML effects (haf)
- All layout preferences currently are collected (e.g., from notation model) (msp)
- Combinations would make persistent changes to the layout preferences (msp)
- Central Question: What should be persistent and what should not be persistent (rvh)
- KIML vs KIVI
- 'KIVI combination scripts' should be persistent (haf)
- Example: Script an 'alternating layout direction rule' (haf)
- We do not want to hard code these rules
- Layout bib vs parametrized layouter (haf, msp)
- Hierarchy should be invisible to specific layouter (haf)
View Management Demo (haf)
- Focus on selecion for KSpace editing
- Hierarchy levels adjustable
- Focus and context effect
- List of elements in focus
- Context should not always be the whole model (rvh)
- Filter effect, possible? (haf)
- How many layers do I want to see to the outside
- Different root element?! (haf)
- Decision: Two counters needed
(FC-Button) Context levels (-)[10](+) Focus level (-)[3](+) All, 1, 2,... All, 1, 2,...
- (FC-Button) not pressed per default
- Focus level select 'all' per default
- To see whole model: Untoggle (FC-Button) and select 'All' as focus level
- Different KIVI Eclipse-View better than usage of tool bar?
- Different parts for different tools (Transformation, Zoom, etc)
- Support buttons, sliders, links, etc
- Use customized selection trigger
- E.g., require additional ALT key to be pressed
- Use case: Rename a state without changing the context
- Decouple zooming from selection (ticket#1448 haf)
- No toggle button but keyboard short cut
- Decision: (see above)
- Preference page settings
- Too far away (ticket#1448 haf)
- Problem with layer counter
- (ticket#1447 haf)
- Minimial size problem
- KAOM 'df adapted coding model'
- Layout of collapsed inner nodes but containing node's size does not change
- Layout maybe in a wrong model state?
- Sleeps?! Synchronization problem?
- Bounding box problem
- (ticket#1446 msp)
- No UI code in constructor, otherwise this could end up in a deadlock
- Turn off validation per default
- (ticket#1449 soh)