
Some parts of this message have been removed.
Learn more about Nabble's
security policy.
Hello,
I have to admit my deception after trying to model my components using the UML module of Netbeans.
I feeled like the authors didn't do any intense debugging and counted too much on the 60cat program to find the bugs for them.
... and I feel that not a lot of people in the 60cat program really tested the UML part.
1) After 10 min of creating "components" and name them on a component diagram, I save it. Then, I realize that the node of the diagram lost its name and can't be opened. No choice, I had to delete it.
2) Thankfully, the components that I created are still in the model section, and I just needed to create a new empty diagram and drag them there. But I ran into other kind of problems:
- I can't drag and drop more than 1 component at the same time and had to do the gesture 12 times to put them all on my new diagram.
- Some of the dependencies that I made between the components doesn't show up on the diagram.
- The arcs that represent the dependencies are represented as set of segments and when I move the component within the diagram, the joins between the segments don't move at all, leaving me in front of a big graphical mess.
- There is no way to know the direction of the dependency from the project view when we see the dependencies of a component (they use the same icon for both directions).
Sorry guys, but I think I lost my illusion of "the only IDE I need" for tonight and I am gonna use my whiteboard and a pen.
Vincent Cantin
Besoin d'un e-mail ? Créez gratuitement un compte Windows Live Hotmail, la boîte e-mail entièrement personnalisable !
Windows Live Hotmail