The only practical way I see is to make the icons choice user
configurable, with a good default set in icons.jar, and the possibility
to use 3rd-party ones.
I, for example, would design and use the 3/4 pie icon for abstract
classes, and a change the colour of enums.

If it were possible to combine icons (ex: add a transparent one, with a
red circle, on top of the "C" class icon),
and assign them based on some simple annotations related rules (ex:
class has a @ToRevise), it could be really powerfull.

You could, for example, tag all the classes you need to "modernize"
(move to JDK5.0) with the @ToRevise annotation,
and they would appear with an additional red circle in the
project/package view.
You would then remove the annotations, one by ones, as you would progress.

Alain

The only practical way I see is to make the icons choice user
configurable, with a good default set in icons.jar, and the possibility
to use 3rd-party ones.
I, for example, would design and use the 3/4 pie icon for abstract
classes, and a change the colour of enums.

If it were possible to combine icons (ex: add a transparent one, with a
red circle, on top of the "C" class icon),
and assign them based on some simple annotations related rules (ex:
class has a @ToRevise), it could be really powerfull.

You could, for example, tag all the classes you need to "modernize"
(move to JDK5.0) with the @ToRevise annotation,
and they would appear with an additional red circle in the
project/package view.
You would then remove the annotations, one by ones, as you would progress.

Alain

The only practical way I see is to make the icons choice user
configurable, with a good default set in icons.jar, and the possibility
to use 3rd-party ones.
I, for example, would design and use the 3/4 pie icon for abstract
classes, and a change the colour of enums.

If it were possible to combine icons (ex: add a transparent one, with a
red circle, on top of the "C" class icon),
and assign them based on some simple annotations related rules (ex:
class has a @ToRevise), it could be really powerfull.

You could, for example, tag all the classes you need to "modernize"
(move to JDK5.0) with the @ToRevise annotation,
and they would appear with an additional red circle in the
project/package view.
You would then remove the annotations, one by ones, as you would progress.

Alain

The only practical way I see is to make the icons choice user
configurable, with a good default set in icons.jar, and the possibility
to use 3rd-party ones.
I, for example, would design and use the 3/4 pie icon for abstract
classes, and a change the colour of enums.

If it were possible to combine icons (ex: add a transparent one, with a
red circle, on top of the "C" class icon),
and assign them based on some simple annotations related rules (ex:
class has a @ToRevise), it could be really powerfull.

You could, for example, tag all the classes you need to "modernize"
(move to JDK5.0) with the @ToRevise annotation,
and they would appear with an additional red circle in the
project/package view.
You would then remove the annotations, one by ones, as you would progress.

Alain

The only practical way I see is to make the icons choice user
configurable, with a good default set in icons.jar, and the possibility
to use 3rd-party ones.
I, for example, would design and use the 3/4 pie icon for abstract
classes, and a change the colour of enums.

If it were possible to combine icons (ex: add a transparent one, with a
red circle, on top of the "C" class icon),
and assign them based on some simple annotations related rules (ex:
class has a @ToRevise), it could be really powerfull.

You could, for example, tag all the classes you need to "modernize"
(move to JDK5.0) with the @ToRevise annotation,
and they would appear with an additional red circle in the
project/package view.
You would then remove the annotations, one by ones, as you would progress.

Alain