Re: the UML ClassDialog v/s the generic Dia properties dialog

[Lars Ræder Clausen <lars raeder dk>]

On Wed, 2008-11-19 at 21:34 +0530, Sameer Sahasrabuddhe wrote:
> Hi,
> 
> It seems the UMLClass is the only DiaObject that has its own special
> dialog. The confusion here is that the UMLClassDialog deals with the
> /content/ of the UML Class, and not its "properties" that are relevant
> in the context of Dia. Take a look at the dialog that is presented
> when a UML Class is double-clicked. Of all the things available on the
> dialog, only three things are relevant to Dia, the diagram app:
> 
> Text Color
> Foreground Color
> Background Color

I would posit everything under the "Style" tab, plus the wrapping
widths.

> The rest is just UML content, and rightfully deserves its own separate
> dialog. Making it separate also removes a lot of problems with various
> property-related functions. Note that an analogy can be made with the
> Flowchart Box. Double-clicking the box provides a dialog where you can
> modify various properties of the box, except one: the contents of the
> box! There is a separate interface for doing this, which is by
> clicking in the box and directly editing the text present.

Why shouldn't the UML object follow the style of the Flowchart Box and
allow editing of its contents in-diagram? Having two different dialogs
would introduce a new (third) way to edit contents. Things that cannot
be written directly can be modifiable via the context menu -- which can
be built dynamically based on what part of the object is being pressed.

-Lars