|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Objectjava.awt.Component
java.awt.Container
javax.swing.JComponent
javax.swing.JPanel
org.argouml.ui.TabSpawnable
org.argouml.uml.ui.PropPanel
org.argouml.uml.ui.foundation.core.PropPanelModelElement
org.argouml.uml.ui.behavior.use_cases.PropPanelInclude
Builds the property panel for an Include relationship.
This is a type of Relationship, but, since Relationship has no semantic meaning of its own, we derive directly from PropPanelModelElement (as other children of Relationship do).
Nested Class Summary |
Nested classes inherited from class javax.swing.JPanel |
JPanel.AccessibleJPanel |
Nested classes inherited from class javax.swing.JComponent |
JComponent.AccessibleJComponent |
Nested classes inherited from class java.awt.Container |
Container.AccessibleAWTContainer |
Nested classes inherited from class java.awt.Component |
Component.AccessibleAWTComponent, Component.BltBufferStrategy, Component.FlipBufferStrategy |
Field Summary |
Fields inherited from class org.argouml.uml.ui.foundation.core.PropPanelModelElement |
|
Fields inherited from class org.argouml.uml.ui.PropPanel |
|
Fields inherited from class org.argouml.ui.TabSpawnable |
|
Fields inherited from class javax.swing.JPanel |
|
Fields inherited from class javax.swing.JComponent |
accessibleContext, TOOL_TIP_TEXT_KEY, ui, UNDEFINED_CONDITION, WHEN_ANCESTOR_OF_FOCUSED_COMPONENT, WHEN_FOCUSED, WHEN_IN_FOCUSED_WINDOW |
Fields inherited from class java.awt.Container |
|
Fields inherited from class java.awt.Component |
BOTTOM_ALIGNMENT, CENTER_ALIGNMENT, LEFT_ALIGNMENT, RIGHT_ALIGNMENT, TOP_ALIGNMENT |
Fields inherited from interface java.awt.image.ImageObserver |
ABORT, ALLBITS, ERROR, FRAMEBITS, HEIGHT, PROPERTIES, SOMEBITS, WIDTH |
Constructor Summary | |
PropPanelInclude()
Constructor. |
Method Summary | |
Object |
getAddition()
Get the current addition use case of the include relationship. |
Object |
getBase()
Get the current base use case of the include relationship. |
boolean |
isAcceptableUseCase(Object modElem)
Predicate to test if a model element may appear in the list of potential use cases. |
void |
setAddition(Object addition)
Set the addition use case of the include relationship. |
void |
setBase(Object base)
Set the base use case of the include relationship. |
Methods inherited from class org.argouml.uml.ui.PropPanel |
addButton, addField, addFieldAfter, addFieldBefore, addLinkField, addSeperator, formatCollection, formatElement, formatNamespace, getButtonPanel, getDisplayNamespace, getModelElement, getProfile, getTarget, getTitleLabel, isRemovableElement, listRoleItemSet, localize, lookupIcon, propertySet, recovered, refresh, removed, removeElement, roleAdded, roleRemoved, setNameEventListening, setOrientation, setTarget, setTitleLabel, shouldBeEnabled, targetAdded, targetRemoved, targetSet |
Methods inherited from class org.argouml.ui.TabSpawnable |
clone, getOrientation, getTitle, setTitle, spawn |
Methods inherited from class javax.swing.JPanel |
getAccessibleContext, getUI, getUIClassID, paramString, setUI, updateUI |
Methods inherited from class java.lang.Object |
equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
Constructor Detail |
public PropPanelInclude()
Method Detail |
public Object getBase()
Note. There is a bug in NSUML, where the "include" and "include2" associations of a use case are back to front, i.e "include" is used as the opposite end of "addition" to point to an including use case, rather than an included use case. Fixed within the include relationship, rather than the use case, by reversing the use of access functions for the "base" and "addition" associations in the code.
MUseCase
that is the base of this include relationship or
null
if there is none. Returned as type MUseCase
to fit in with the
type specified for the org.argouml.uml.ui.UMLComboBoxModel
.public void setBase(Object base)
Note. There is a bug in NSUML, where the "include" and "include2" associations of a use case are back to front, i.e "include" is used as the opposite end of "addition" to point to an including use case, rather than an included use case. Fixed within the include relationship, rather than the use case, by reversing the use of access functions for the "base" and "addition" associations in the code.
base
- The MUseCase
to set as the base
of this include relationship. Supplied as type MUseCase
to fit in with the
type specified for the org.argouml.uml.ui.UMLComboBoxModel
.public Object getAddition()
MUseCase
that is the addition of this include relationship or
null
if there is none. Returned as type MUseCase
to fit in with the
type specified for the org.argouml.uml.ui.UMLComboBoxModel
.public void setAddition(Object addition)
addition
- The MUseCase
to set as the
addition of this include relationship. Supplied as type MUseCase
to fit in with the
type specified for the org.argouml.uml.ui.UMLComboBoxModel
.public boolean isAcceptableUseCase(Object modElem)
Note. We don't try to prevent the user setting up circular include relationships. This may be necessary temporarily, for example while reversing a relationship. It is up to a critic to track this.
modElem
- the MModelElement
to test.
true
if modElem is a use case,
false
otherwise.
|
|||||||||||
PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
ArgoUML © 1996-2004 (20050222) | ArgoUML Homepage | ArgoUML Developers' page | ArgoUML Cookbook |