WebTools code formatting options not used by Wild Web Developer

[nimo23]

Open a css file in generic editor and try to reformat it. User expects that the built in eclipse formatting settings are also work within the "generic editor".

[mickaelistria]

Which specific setting do you have in mind?

[nimo23]

The typical eclipse built in formatter settings used within css files should also be used as the default within the generic editor for css:

[mickaelistria]

This formatter settings are downstream of Eclipse Platform (in WTP), so Wild Web Developer, which doesn't depend on WTP, doesn't and won't care about them. You can just uninstall the other CSS editor and things will be less confusing.
Instead, we can think about a mechanism to allow migration or copy of preferences, and pass them to the language server. But this would first require that we have preferences for CSS code formatting in Wild Web Developer, which we don't have so far. It's somehow related to #225.

[nimo23]

which doesn't depend on WTP, doesn't and won't care about them. You can just uninstall the other CSS editor and things will be less confusing.

Would be fine, if wwd has a seamless integration within eclipse.. I guess, thats the main reason why to use wwd in eclipse instead of, for example, "vs code" or "intellij".

Would be good, to take the best of the both worlds of WTP and language server. This what is bad in the one can be compensated by the other..

Why should the wwd built in eclipse does not care about the overall eclipse platform settings? If I must treat the wwd in complete isolation to the rest of eclipse, why should I use wwd at all?

[mickaelistria]

Why should the wwd built in eclipse does not care about the overall eclipse platform settings?

Wild Web Developer should (and does to some extent) care about Platform settings, but WTP editors are not in Platform, they're a downstream project of Platform and parallel project to Wild Web Developer, and we want to avoid technical intersections between them. However, we can consider some tricks allowing to "transfer" some settings from one project to the other.

But first, we'd need to investigate how to customize the CSS formatting using the VSCode CSS language server, and leverage this customization.
Then, once we know how to customize, we can look for tricks to get the customization loaded according to WTP editors preferences when we have no better input.

[angelozerr]

But first, we'd need to investigate how to customize the CSS formatting using the VSCode CSS language server, and leverage this customization.

Please see my comments #237 (comment)

[dantran]

this long overdue is bug is now impacting Eclipse 2022-03 pom editor nolonger using XML Editor indentation configuration

[agentgt]

@mickaelistria Regardless of WTP why does Wild Web Developer use or rely on the "Generic Editor".

I just recently upgraded Eclipse (for enterprise developers) and found it rather confusing with both WTP and WWD being installed.

It seems like most of the bugs being filed are because fundamentally the only editing config is through Generic/Structured Editor when people expect each mode (e.g. yaml, javascript, etc) would have its own configuration. Combine this with the existing WTP and it is super confusing.

As for Maven it appears the WWD XML Editor takes over the Maven Pom Editor but I'm not sure if that is actually the case. It is very bizarre because the WTP XML editor was used in the past.

I'm just surprised some one OK'd having WWD in base installs of Eclipse for Java Enterprise developers. I don't think it is ready yet.

[mickaelistria]

@agentgt please read https://github.com/eclipse/wildwebdeveloper#-design-and-architecture

I don't think it is ready yet.

It's more ready that former editors that were getting slowly out of sync with most languages/modern features. But some features are also missing. Contributions to fill that gap are welcome.

[dantran]

an alternative would be Spring STS4, which works for me while waiting for this fix

[agentgt]

It's more ready that former editors that were getting slowly out of sync with most languages/modern features. But some features are also missing. Contributions to fill that gap are welcome.

Its not that I don't think it would be useful for things like YAML or Javascript where obviously WTP doesn't work well but things like HTML, XML and arguably CSS were already working fine.

XML especially since Eclipse has always had great support for XML.

@agentgt please read https://github.com/eclipse/wildwebdeveloper#-design-and-architecture

I don't care about the technical reasons of why all modes are configured through one Generic Editor. I care because it doesn't make since and I'm curious how you are going to make each mode configurable since it just uses the Generic Editor. If you say its possible I'm fine with Generic Editor.

For example some modes like XML or HTML I might want tabs for indent and others I might want spaces (which is broken for YAML as I prefer my "Generic Editor" to use tabs).

Also for "Generic Editor" I expect it to be a plain text editor. I'm not a fan of how WWD just commandeers what is normally a plain text editor and then calls it "Generic" regardless of what mode.

So yeah thats what I meant by not ready. Its just not ready to be included with the "Eclipse for Java Enterprise..." but for an addon to get better JS/TS I agree it is superior to WTP.