[Uml-devel] [Bug 86952] New: Rendering of attributes as associations

[Oliver Kellogg]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
      
http://bugs.kde.org/show_bug.cgi?id=86952      
           Summary: Rendering of attributes as associations
           Product: umbrello
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: Linux
            Status: NEW
          Severity: wishlist
          Priority: NOR
         Component: general
        AssignedTo: umbrello-devel.kde.org
        ReportedBy: okellogg users sourceforge net


Version:            (using KDE Devel)
Installed from:    Compiled sources

Code import currently creates aggregations/compositions
for members whose type it can resolve.
This is not necessary, and can actually be bothering.
Instead, create attributes for all data members.
Resolve the types of the attributes, and determine
whether a pointer is involved.
On dragging imported classes from the list view to the
diagram, do as follows:

- If the class representing the type of an attribute
  is not present on the diagram then display the
  attribute in the class' attribute compartment.

- If the class representing the type of an attribute
  is present on the diagram then do not display that
  attribute in the class' attribute compartment.
  Instead, display an appropriate association
  (composition or aggregation depending on whether
  a pointer is involved.)

Implementation note: This implies that
1) the m_pObject of an AssociationWidget may also be
   a UMLAttribute
2) the type of an UMLAttribute is a pointer to a model
   class (not just a string)