UsingEclipseToExploreOtherPeoplesCode

From SPA Wiki

• Even though the three Eclipse tools we looked at are exploring tools which

work on a shifting code base, there remains a strong requirement for them to produce snapshots in the form of image export which help communicate the current state of design as an insert to other report documents you may want to produce.

• Not everyone finds graphical representations of code that useful over and

above Eclipse's out-of-the-box Java browsing, depending upon the size, type and existing familiarity with the codebase in question.

• We saw GUI descriptions of filters control class diagram outputs in

AgileJ, and we saw query-based descriptions control tree-based outputs in JQuery; but it would be useful to have query-based descriptions control class diagram outputs.

• Tree-based output of JQuery has the advantage over more spacial outputs of

AgileJ and ISpace in that browsing of the results is possible by keyboard rather than mouse.

• It is annoying that ISpace does not allow multiple views of the same

project - forcing constant expansion and collapse of the packages. However, this can be overcome by a workaround; copying result resources outside of Eclipse then re-opening the copy.

• It would be useful if AgileJ supported browsing of structure along method

calls.