Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-dev] Alternative to WTP editors with TM4E and LSP4E

Thanks Mickael for your message.

If you have time, please test too and angular2 eclipse

It is based on tsserver and tm4e and it starts working well even with _javascript_ (Salsa)!

There are a lot of features very impressive (thanks to tsserver) with completion, refactoring, quickfix, syntax coloration and the editor is fast (thanks again to tsserver).

I see that JSDT have so many problems with completion, refactoring, etc. Please try

Here some screenshots. Angular2 syntax coloration:

Images intégrées 1

Here a demo with TypeScript quickfix:

Here a demo with tslint quickfix:

See last features at: and

Hope you will like it.

Regard's Angelo

2017-04-25 18:52 GMT+02:00 Gorkem Ercan <gorkem.ercan@xxxxxxxxx>:

Hi Mikael,
This is excellent work. The best use case of what LSP4E/TM4E can do for the Eclipse IDE
I have seen so far.

IMHO we can look at replacing WTP editing components on some of the packages and this should be WTPs way to cater developers going forward.
I do not think we are ready to stop the release of those replaced components though which may actually have adopters.


On 25 Apr 2017, at 12:01, Mickael Istria wrote:

Hi all,

I'd like to share with you some progress about the TM4E and LSP4E projects. Both projects are actually targeting to allow easy implementation of rich editors reusing external resources and to reduce and factorize maintenance effort.
As WTP editors have been in a bad shape (out-of-date, not comfortable, reviews pending for a while....) for several years now, we've started to look at how TM4E and LSP4E, with the right language servers, can allow to have a better web development story in Eclipse IDE than what WTP is currently offering.
Here is the result:

It's relying on VSCode language servers for HTML, CSS, SCSS, SASS, LESS, JSON and on for JS and TS.
It took me about a couple of weeks to bind those with LSP4E and to work on the packaging part (which is actually the only necessary part when dealing with Language Servers). All the features are provided by the language servers and are presented in Eclipse IDE thanks to LSP4E.

Please have a look, give it a try and provide feedback. Contributions (bug reports, code, whatever) are entirely welcome at every layer of that work: on Platform UI, in LSP4E, in BlueSky integration, in language servers directly.

Now, let's just face *the* question: wouldn't it make more sense for our community, "products" and users, to start dropping the unmaintained-like WTP editors and to consider this alternative as an official replacement and to adopt the language server/generic editor approach which happens to work well?

Mickael Istria
Eclipse developer for Red Hat Developers
My blog - My Tweets

wtp-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

wtp-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit

Back to the top