Hi Mickael
Yes. Some editors such as Xtext-based already have such a prompt.
Exploiting EMF improvements [1] at M4 meant that OCL [2] and
QVTd's parasitic use of the Xtext nature was untenable and so for
M5 the Xtext functionality is cloned by OCL and QVTd natures so
that their natures control the auto-build even when that amounts
to more than an auto-validation. OCL and QVTd therefore now have
an add-project prompter. Many other projects, not least EMF [3]
and UML2 [4], could offer a consistent auto-validation if they had
a nature/builder.
Implementing the add-nature/configure-project dialog and
do-not-ask-again preference is a tedious bit of cloning for every
project to implement.
Suggest that an optional "extensions" element for an
"org.eclipse.core.resources.natures" extension point could
identify the file extensions to which an auto-add-nature could
apply.
Regards
Ed Willink
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=418619
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=429479
[3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=528869
[4] https://bugs.eclipse.org/bugs/show_bug.cgi?id=529324
On 10/01/2018 08:06, Mickael Istria
wrote:
Hi all,
While chatting with a recent VSCode users who
switched from Eclipse IDE on Twitter, I was
mentioned one very important thing where VSCode
still excels compared to Eclipse IDE (and others):
auto-configuration of projects when opening a file.
In VSCode, when one opens a file and an extension is
installed for it, VSCode automatically makes the
project usable. That can involve creation of local
files or just startup of the language server,
whatever, the result is the same: it works.
In Eclipse IDE, if I open a C file in a project that
doesn't have the CDT nature, not much happens.
While we've made progress regarding auto-discovery of
possible extensions to install, auto-discovery of project
configuration at import, Eclipse IDE still misses this
important step happening when creating or opening a new
file under an existing project.
I don't think this is something that can easily be provided
by the Platform, as each language-specific extension would
have it's own requirement to configure project. So it would
be up to each specific editor to suggest that when opening a
file.
For example, if I'm in a non-typed project and open a pom.xml
with the m2e editor, this editor could (suggest me to)
configure the project to enable Maven; if I open a Java file
and have JDT installed, the editor could suggest to configure
the Java nature and so on...
This workflow would considerably
improve usability, so please consider it
in your future development ;)
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
