#243 auto import for interactions

[R. Matt Barnett]

It would be nice if immediately after compilation each
successfully compiled file’s package was added to the
interaction window’s class path. Many times I find
myself compiling a class and wanting to then observer
its methods in the interactions window—however, each
time I recompile the class the interactions window
requires me to type “import com.whatever.package.*”
before I can create an instance of my class. If the
package was auto imported each time, I go could to
straight to “new” after each compile. I would think
that the package should remain in the interactions
window classpath until the last file which exists in
the given package is closed within DrJava.

[Charles Reis]

Logged In: YES
user_id=429731

This is a duplicate of feature request 642361. Still, it's a good idea that
should be implemented, and the original code that did it was apparently
lost.
http://sourceforge.net/tracker/index.php?func=detail&aid=642361&group_id=44253&atid=438938

[Dan Smith]

Logged In: YES
user_id=1060117

Another cross-reference: request 988082 -- the same functionality
is desired, but with a different interface. Typing imports is
definitely one of the more painful features of the interactions
pane, along with the difficulty in creating test objects (you can
type out List<Integer> l = ..., and then scroll back and change it
to l2, etc. each time you change it; or you can type List<Integer>
l; l = ... and reassign to l each time), and the required casting of
generic results (since they're treated as Objects).

https://sourceforge.net/tracker/
index.php?func=detail&aid=988082&group_id=44253&atid=438938