Posted: January 01, 2011 20:50 by javydreamercsw
The current UML module uses the Netbeans Visual Library. This is certainly the most obvious choice for our rewritten module, and in truth it seems quite a good option, but it's still worth discussing alternatives - if there are any?
Problems with the Netbeans Visual Library:
It is not thread-safe - we will have to write our own thread-handling code in order to insulate it from random thread events such as (possibly) our GUI events, as well as external file changes (and others??).
It is not particularly customisable - many of its classes are prescribed "final", where their (careful) overriding might be useful - this is the personal experience of David Bastow whilst trying to write his synchronous diagram/code module.
Only the problems have been listed here because currently we have no alternatives - there are many things that the Netbeans Visual Library does very well!