I hope don't bother you if I write a last point before closing this thread:
And thank you very much for your feedback, which I find very helpful.
I have never understood why to limit the user when there is no need to do it.
When you zoom out the diagram, most of the class members lines get truncated even when there are still sufficient space in the box width for displaying them entirely;
Limiting the user is the last thing we want to do. The "..." problem when zooming is due to a technical limitation (Flex doesn't scale properly the fonts) and it is not trivial to overcome. We will provide a solution (I hope to have it in 1.1 version).
this member line appears in the head of the comments panel in a wrapped way, showing its full content, but in multiple lines.
I don't understand this behavior very well; could you send a screen shot?
But if the user has some members too long in the box, must he hide the content of this and the rest of the lines? (and to hide also the lines of all the other classes?).
I prefer the approach of not limiting the user.
If I don't want to make things complex and have to build scroll bars or making possible to wrap lines, I'd give the user at least the ability and the responsibility of hiding or showing the length of the line by himself by re-sizing its container box.
When there will be the style that controls if yes/no the operations display their parameters, I don't think the big classes problem will appear any more. My suggestion of using the filtering to hide ONLY the long methods is just a work around until then.
If I understand correctly, even when we'll have the above style, your suggestion is to have an option to allow resizing with no restriction, even if this implies the creation of scroll bars; am I correct?
The disadvantage of scroll bars within classes is that the class won't "grow" when new attributes/methods are added (from the tree, codesync, etc).
Excuse if I'm seeing the things less complex than they really are, but I like being practical; I don't give more importance to the fact that the lines shine when you move the mouse over them, over the fact that you can not manipulate your design parts.
I totally agree with you. We want our tool to be as friendlier as possible with the developer. This means max of flexibility, productivity and min of limitations.
Thanks again for your feedback.