We don't guarantee that we'll implement everything requested here, but we'd like to have your input. If you'd like to indicate your support for a proposal, just add your name (in parentheses) after the request.
I've been idling around the idea of implementing a 3D layer over JUNG visualizations... not always useful, but sometimes interesting.
A nested layout would be useful, so that any node could contain a graph itself.
Is anyone working on a hierarchical layout for Jung (ala Kozo Sugiyama's method or similiar)? This would open up Jung usage to a whole new class of users who view these kind of graphs!
Importers / file loaders for just a few more formats, e.g. jgraph's jgx
It would be really useful to include new network structure measures like Burt's structural hole measures. An implementation of these has been donated and will hopefully be included in the next release, thanks to Diederik van Liere--Joshua.
moved over from HowTo:
There are two places where filters can be placed. It seems like the deprecation of getVisibleVertices in the class Layout makes clear that there is confusion about the 'perfect' place of filtering. Not everything can be done in the PluggableRenderer. For a large graph, the layout should pass a limited set and the subsequent modules in the viewer shouldn't need to filter them themselves.
The MutationVisualizationViewer is a quasi-MVC approach, like Swing's and the current JUNG implementation. Instead of a separate Controller I have extended the VisualizationViewer? by mutation functionality. When this subclass turns out to function it can be made the default VisualizationViewer? again.
The GraphMLAttributes? can be read with GraphMLFile? and GraphMLFileReader?.
The ability for an Edge to be the starting point (or ending point) of another Edge.