Hi Mickael, As you know I like the approach of eclipse bluesky. In fact, I am a bit worried about the capacity of WTP team to improve the existing editors. Team members did a great job but there is so much effort in CSS editor to fix all existing problems like formatting.
I think we should replace WTP editors with new ones based on LSP4E/LSP4J Gautier de Saint Martin Lacaze 2017-04-25 22:01 GMT+02:00 Lars Vogel <[email protected]>: > Thanks Mickael, looks great. I personally would love to see the old > WTP editors replaced with this approach. > > Best regards, Lars > > On Tue, Apr 25, 2017 at 6:01 PM, Mickael Istria <[email protected]> > 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: > > * > > https://marketplace.eclipse.org/content/bluesky-web- > development-eclipse-ide-experimental > > * https://github.com/mickaelistria/eclipse-bluesky > > * http://www.screencast.com/t/BaC9DxHIqD > > > > It's relying on VSCode language servers for HTML, CSS, SCSS, SASS, LESS, > > JSON and on https://github.com/sourcegraph/javascript- > typescript-langserver > > 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? > > > > Cheers, > > -- > > Mickael Istria > > Eclipse developer for Red Hat Developers > > My blog - My Tweets > > > > _______________________________________________ > > wtp-dev mailing list > > [email protected] > > To change your delivery options, retrieve your password, or unsubscribe > from > > this list, visit > > https://dev.eclipse.org/mailman/listinfo/wtp-dev > > > > -- > Eclipse Platform UI and e4 project co-lead > CEO vogella GmbH > > Haindaalwisch 17a, 22395 Hamburg > Amtsgericht Hamburg: HRB 127058 > Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel > USt-IdNr.: DE284122352 > Fax (040) 5247 6322, Email: [email protected], Web: > http://www.vogella.com > _______________________________________________ > wtp-dev mailing list > [email protected] > To change your delivery options, retrieve your password, or unsubscribe > from this list, visit > https://dev.eclipse.org/mailman/listinfo/wtp-dev >
_______________________________________________ wtp-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/wtp-dev
