[umbrello-devel] [umbrello] [Bug 336012] Automate required namespace/package user interaction on c++ import

[Ralf Habacker]

https://bugs.kde.org/show_bug.cgi?id=336012

--- Comment #5 from Ralf Habacker <ralf.habacker at freenet.de> ---
(In reply to Ralf Habacker from comment #4)
> Here is one proposal how to solve this issue:
> 
> Initial situation: 
> 1. On importing Bxx classes the related type Dxx is not known, which has
> currently to be solved by an user action raised through the "namespace or
> class" dialog. 
> 2. In umbrello code uml class objects and package objects are represented by
> an UMLClassifier and UMLPackage instance. 
> 3. Class UMLClassifier is derived from UMLPackage. 
> 4. Class widgets are represented by a ClassifierWidget instance and package
> widgets by a PackageWidget instance. 
> 
> Required changes:
> 1. On creating unknown type Dxx we need to mark this "class-or-package"
> condition somewhere in the uml object
> 2. On importing Class D2 we need to find the already created object with the
> "class-or-package" flag and retype it to a class. 
> 3. On importing namespace D3 we need to find the already created object with
> the "class-or-package" flag and retype it to a namespace. 
> 4. After import has been finished there may still be uml objects with the
> "class-or-package" flag for which a gui action is req
[sorry for sending not complete comment, I pressed accidently send]

uired from the context menu and property dialog to retype the 
"class-or-package" flagged object to be a real class or package.

to discuss: 
1. Because class and package widgets uses different classes it may be useful to
extend class ClassifierWidget to handle package widgets too, otherwise the
ClassifierWidget instance has to be recreated as PackageWidget and reassigned
to all parents/childs

2. How to flag "class-or-package" ? Using "class-or-package" as stereotype has
the advantage, that such widgets are flagged on diagrams out of the box.

Any comment, suggestions or better implementation ?

-- 
You are receiving this mail because:
You are the assignee for the bug.