Read Me

The package jung.ext.icon does create subclasses from: 
  classes in the JUNG library,
  classes in the jung.refact (JUNG refactored) library,
  classes in the jung.ext (JUNG extension) library or
  classes in the jung.ext.dag (JUNG DAG extension) library.
  
The extensions as proposed are mainly to support the interface IconVertex
that extends the FamilyVertex interface in the jung.ext.dag library
(that extends the class Vertex from the JUNG package). 
The IconVertex class is quite an application specific class. This package 
is therefore probably not really valuable for the internet community running
on its own. The interface IconVertex adds only getIcon and getTooltip, but
the implementations have for example a function isInterIcon and the extended
swing Icon interface VertexIcon, that makes only sense after reading the 
appropriate documentation. 
This means that these files are not particulary written to provide easy 
handles to extend them further. However, remarks regarding refactoring methods 
that would make them much easier to expand (to be used for your specific 
application) are always appreciated.

Some classes are kept out of the jung.ext.icon library because they are 
- even more - intertwined with the application code or contain in general 
much more code from my hand than of the authors of the JUNG package. 
These classes do use for example the IOManager from the vilaug.io package.

See especially the vilaug.icon library with the VertexIcon class. That class 
is the twin of this class. And does have functionality to return an 
IconVertex like this class can return a VertexIcon. 

See also vilaug.exceptions for Exception classes.

Conventions:
- Regarding names: Vertex -> IconVertex and Graph -> IconGraph.
- Use the Vertex interface when possible, and the specialized interface
  IconVertex when necessary.

Copyright, see JUNG copyright. And about everything I declare GNU (General 
Public License) copyrights. That means in my own words, that you're allowed
to copy, share, distribute and improve everything, but have to publish
your source code. You're allowed to charge for these events, but not for
publishing. Please, let me also know that you used my code.

Author: A.C. van Rossum
Date: dec. 2005
Contact: http://www.annevanrossum.nl/contact/