This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 106464 - Ability to generate class diagram from other languages
Summary: Ability to generate class diagram from other languages
Status: NEW
Alias: None
Product: uml
Classification: Unclassified
Component: Reverse Engineering (show other bugs)
Version: 6.x
Hardware: PC Linux
: P3 blocker (vote)
Assignee: issues@uml
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-13 10:18 UTC by eskild
Modified: 2007-10-19 21:11 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description eskild 2007-06-13 10:19:06 UTC
NetBeans 6 will support other languages -- Ruby, C++, and the generic scripting framework. There's a lot of work being
put into the NetBeans infrastructure to build models of the code people are writing -- we have class views, navigators
and several other things.

But what I really, really miss is the Big Picture. So my thinking is: Wouldn't it be possible, from the models NetBeans
is already building, to generate an overview class diagram of a project?

Note that I'm not requesting round-trip features, code/model synchronization, or anything fancy like that (not at this
time, anyway -- in the future it would be really great to have). All I want is that class diagram which gives me an idea
how the code is organized. You could call it a "code comprehension" feature for people like I, who often have to work on
existing code that I didn't write myself.

How could this work, UI-wise? Well, the feature would develop in phases, I guess:

Phase 1: Generate diagram from entire project -- an overview feature

Phase 2: Generate diagram from set of classes -- drilling down

Phase 3: Move support for other languages up towards the level of Java
  - 3.1: Synchonize code => diagram
  - 3.2: Synchronize diagram => code
  - 3.3: Approach Java functionality

The idea behind the phasing is: Get it out there, learn from it, figure out how such a feature a) should work and b) can
be implemented in the best way. Then, once the groundwork is done, "go for the gold".

Regards.