so far I've seen a lot of discussion about the implementation
of this import wizard through Refelection, etc...
But one of the questions we may want to ask is, is the
convenience of the import-wizard enough to justify all
this work ? could this be applied elsewhere ?
Do we really need an import-wizard ? How about a 'jde-tag-wiz' ?
Why restrict ourselves to an import-wizard, when there are plenty
of other instances when we need to complete a class or
package name ?
How about we parse for <a_base_path>.<a_partial_name>[TAB]
and JDE then offers a completion-list of available sub-packages,
classes, or methods/fields ?
example 1:
imports: if I type:
import java.applet.App[TAB]
I get a completion buffer containing:
java.applet.Applet
java.applet.AppletContext
example 2:
fully-qualified class:
logibro.dev.tournet.javalib.util.F[TAB]
I get:
logibro.dev.tournet.javalib.util.Field
logibro.dev.tournet.javalib.util.FieldFormat
example 3:
field/method completion: (here's where Reflection comes in)
java.lang.System.getPr[TAB]
I get:
java.lang.System.getProperty
You could even add in the method signatures to this
later on. Start with fully-qualified names, and once
that works add in completion for already imported/loaded
packages/classes.
Francis Korning
[EMAIL PROTECTED]
--
<PRE>
==============================================================
* Your e-mail has been returned due to insufficient voltage. *
==============================================================
</PRE>
