A complete replacement of the UML drawing area control is underway. Currently we use a closed source graphing package. We are now building the UML designer on top of the Netbeans Visual Library .
| From | To | Created | Fixed |
|---|---|---|---|
| Jun 02 | Jun 08 | 45 | 36 |
| Jun 09 | Jun 15 | 27 | 53 |
| Jun 16 | Jun 22 | 33 | 46 |
| Jun 23 | Jun 29 | 50 | 35 |
| Jun 30 | Jul 06 | 25 | 31 |
| Jul 07 | Jul 13 | 67 | 52 |
| Jul 14 | Jul 20 | 18 | 40 |
| Jul 21 | Jul 27 | 20 | 43 |
| Jul 28 | Aug 03 | 18 | 27 |
Sterotypes project feature is something critically missing, UML profiles project feature should be available which should allow users to define new Sterotypes, their attributes etc. and then these profiles can be attached to UML projects.
Sterotypes should have inheritance, should have constraints e.g. <<Facade>> can only be applied to components, it may have attributes like allowTransaction etc.
This will act as a metadata for code generations.
This is something very critical for MDA based projects.
-- Trey Spiva -- Yes we agree. We do have profile support on our roadmap. In a profile editor is planned for the second half of next year. See our road map for more information.
Rahul -Thanks for reading above comments. Just like to add few more lines -
UML Profiles created project will have versions so attached UML modeling projects should have feature of migrating them.
Developers should be able to write custom code generator modules. UML Model reading API framework should allow developers to write custom code generators. So from Netbeans perspective, in future ideally their should be something like create a UML Transformation module.
These modules can be exported as plugins and UML projects should be able to select a transformation module and generate code. This may trigger a callback in Model reading API which will trigger custom templates written in freemaker etc.
I hope it make sense.
I noticed you have the ability to copy projects, or elements within a project to another project, in the roadmap - but listed under "Future". I would like to put in a vote (word?) for it to be given more importance: it seems to me that a very common use of UML is to play "what-if" scenarios, to sketch out potential design alternatives, to then be able to compare them to each other. This is very cumbersome to do now in NetBeans UML, since one may need to recreate the whole project from scratch, in order to have a second copy that can illustrate an alternative design. I teach classes on Java and OO design - and this lack makes using NetBeans UML in class very unattractive...
I wrote a little shell script to allow me to copy a complete NetBeans UML project to a second directory, renaming the internal model tag to make it independent of the first - but it seems that NetBeans does not like to then open two of these projects side-by-side. It would be nice if one could, for example, make a copy of an existing UML sequence diagram, then be able to edit the second copy, without the changes propagating back to the first one - that way, one could show the two designs, side by side...
Happy Modeling!
The performance problems occur when a diagram has scrollbars. After the scollbars appears, any action in the diagram takes a very long time.
With jdk1.5.0_06 the flag "-J-Dapple.awt.graphics.UseQuartz=false" needs to be used to have decent performance on the Mac. However, this flag may cause side-effects in other parts of the IDE. Depending on which other modules are being used, you may or may not ever see these side-effects.
With jdk 1.5.0_07-154 the performance problems are a little better. The performance of selection, and context menu actions are barely usable, however scrolling is still extremely slow.
In jdk1.6 this bug has been fixed for the Intel platform. However, the problem still exist on the Power PC. There are other problem that occur with the jdk 1.6 (see issue 86850). NetBeans has a general refreshing problem with jdk 1.6. One of the refershing issues is show in the below image.
This is a known problem Mac bug: Bug ID#4647508.
It is important to note that this bug is filed against a very specific configuration: PPC Mac with Java1.6
| Document.rtf | ![]() |
1957407 bytes |