jung
jung copied to clipboard
jrtom
JUNG: Java Universal Network/Graph Framework
Proposed by @tomnelson and discussed in #163; here are some of the relevant bits: [The idea would be to] put all visualization related property settings in one place, something like...
See comments here for context and a proposed solution: https://github.com/jrtom/jung/pull/159/commits/48df6799d8730600ae301d43a456287e7a59f43a
At the moment, JUNG provides a default size of 600x600 for layouts and views. In my opinion, we should not be providing any defaults: if users want to create a...
`DijkstraDistance` and `DijkstraShortestPath` each (optionally) cache information about previously calculated shortest distances/paths, as a time/space tradeoff in case those distances/paths are needed again. However, they don't do so in a...
Potential areas for improvement: * reduce the number of subpackages and classes * use the Builder pattern to avoid multiple overlapping constructors * generally unify the way in which algorithms...
**tl;dr**: as the lead JUNG designer, I'm looking for feedback on how we should handle this particular issue. Please comment if you have thoughts on this subject. As it currently...
The following items don't work: - [ ] vertex stretching - [ ] displaying voltages (values seem incorrect) - [ ] filter when degree < 4 includes a node with...
This mostly boils down to using `VisualizationServer` (interface) or `VisualizationModel` in place of `VisualizationViewer` (class) where possible.
- [ ] a bunch of places assume that various Predicates or Functions can be null. Either use Optional or require them to be present instead. (Or mark as @Nullable.)...
@jrtom Currently, there are a number of classes in JUNG which seem to be either internal implementation details which nonetheless have the `public` modifier, meaning JUNG users can use them...
