Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-dev] Reusing generic editor features in JDT

Hi Mickael,

Thanks for the feedback, do we have support in the lsp4e to start a LS in-process? Specially if the LS implementation is java ?

Best Regards,

On Wed, 7 Sep 2022 at 12:15, Mickael Istria <mistria@xxxxxxxxxx> wrote:

On Wed, Sep 7, 2022 at 11:56 AM Gayan Perera <gayanper@xxxxxxxxx> wrote:
Hi all


I see that generic editor is getting more features similar to vscode editor with tm4e. Is there a way that we can slowly migrate jdt editor to use the generic editor ? Any ideas or hints ?

I think it's way too early to start thinking about a migration. But it's definitely the right time to start investigating this topic further.
A first step would be to try get JDT-LS started in Eclipse IDE (in the same process, not as a separate one so the Java model is shared between JDT-LS and JDT UI!). With that, it would allow the Generic Editor to provide edition features similar to what vscode-java offers, based on the LSP stuff, but still to also get the JDT UI features (which are mostly commands, builders and other stuff) working on the same model. So things like build and existing refactoring wizards and so on would be able to work on the Generic Editor that would "only" deal with edition assistance.
Once this starts to work, then we can try a feature gap analysis to find out whether the gap can be filled. If it appears the gap is easy to fill, then we can start discussing about the strategy regarding editor(s).
I’m mainly focused on having mote generic views and editors features in eclipse platform to make different language experience some what similar. 

That is indeed one of the purpose of Generic Editor.

platform-dev mailing list
To unsubscribe from this list, visit

Back to the top