Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[graphiti-dev] Separation between IDiagramContainer and IDiagramContainerUI

Hi FĂ©lix,

 

I checked the methods that are part of the interfaces and see the following methods from IDiagramContainerUI as candidates to move down:

-          Lifecycle methods (we already have isDirty)

o   Close

o   doSave

o   isAlive

o   updateDirtyState

-          Title

o   getTitle

 

What would we additionally need from DiagramEditor?

-          Refresh

o   refreshContent

-          Title

o   getTitleToolTip

 

This looks more consistent to me although it still mingles technical aspects. I would be reluctant to move too many methods down to IDiagramContainer and also to IDiagramContainerUI, at least for the first step.

 

What do you think?

 

Michael


Back to the top