Re: Proposed New Structure (starter for 10)

Stephen Leake <[email protected]> writes:

> [email protected] (Phillip Lord) writes:
>
>> After this my vision is subtly different. I believe that JDEE should be
>> relatively small and do as little as possible, while allowing Emacs and
>> the environment to do most or all of the things that you speak off.
>
> +1. However, JDEE needs to provide some things to "the rest of Emacs" to
> leverage that properly.
>
>> So, project support. Eric has already mentioned EDE. 
>
> JDEE needs to provide an EDE java project.

I think this is sounds sensible, but I am not sure what it would bring.
In particular, I'd be worried if it involves duplicating information
between Emacs and what-ever build tool is being used (probably maven),
unless we know how to completely automate this.


>> Combine this with rapid navigation tools like projectile, 
>
> I suggest we stick to Emacs core functionality when we can. That means
> xref, here (in Emacs 25). If xref is insufficient, we can help extend it.
>
>> Auto-completion -- we should support completion-at-point-function, using
>> a connection to the JVM, and a Java (or JVM) based completion library.
>> Actual completion can be done by company, auto-complete or what ever.
>
> There is a trade-off here when editing code; if the code has syntax
> errors, you may get better results from Semantic than from the java
> compiler. So we should design for a choice of completion backends, to
> allow experimenting.

Sorry, my fault, it is `completion-at-point-functions' i.e. plural. So
this comes off the shelf, I think. And user configurable. So, we can,
for example, do completion in comments as well whcih neither semantic
nor java will naturally support.

Phil

------------------------------------------------------------------------------