|
Hi
Today, we have no default functionality, so every project does
its own thing, or worse doesn't.
Providing an AbstractXXXNature.configure() that exploits an
optional "extensions" element provides an easy extensible default
for boring projects that are happy with a default. Something is
facilitated. Nothing is broken.
Advanced projects such as JDT and CDT are still free to
not-implement or re-implement and so do whatever is good for their
community. Nothing is imposed. Nothing is inhibited.
(Again today, JDT actually offers nothing. I've been meaning to
raise a Bugzilla about the missing "Convert to Java project",
which forces me to cut and paste nature/builder lines between
.project files.)
Regards
Ed Willink
On 12/01/2018 14:18, Daniel Megert
wrote:
Using #configure
sounds interesting but that lives in the core layer. But to
correctly set
up e.g. a Java project you need input from the user.
> I
believe the diversity of possible actions makes it almost
impossible to
find a generic solution to this problem that can cover all
legacy and future
stories.
+1
Dani
From:
Ed
Willink <ed@xxxxxxxxxxxxx>
To:
ide-dev@xxxxxxxxxxx
Date:
10.01.2018
10:50
Subject:
Re:
[ide-dev] Auto-configuring projects when opening editors
Sent
by: ide-dev-bounces@xxxxxxxxxxx
Hi Mickael
Indeed and all those diverse actions
can be orchestrated by the XXXNature.configure() which currently
has to
be 100% cloned; an AbstractProjectNatue could offer standard
functionality.
If XXXNature.configure() neglects to invoke
project.setDescription(), no
XXX nature would actually be added leaving XXXNature.configure()
as a transient
tool for some irregular form of configuration.
Regards
Ed Willink
On 10/01/2018 09:36, Mickael Istria
wrote:
On Wed, Jan 10, 2018 at 10:29 AM, Ed
Willink <ed@xxxxxxxxxxxxx>
wrote:
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.
I think natures are too restraining
here.
While it's used in most cases, there are other ways an editor
can configure
a projet or its own enablement (preferences, project settings, a
builder,
starting a Run configuration, show a wizard...). I believe the
diversity
of possible actions makes it almost impossible to find a generic
solution
to this problem that can cover all legacy and future stories.
--
Mickael Istria
Eclipse
IDE developer,
at Red
Hat Developers
community
Elected Committer Representative at
the
Eclipse
Foundation
board of directors
_______________________________________________
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
_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from this list, visit
https://urldefense.proofpoint.com/v2/url?u=https-3A__dev.eclipse.org_mailman_listinfo_ide-2Ddev&d=DwICAg&c=jf_iaSHvJObTbx-siA1ZOg&r=1UITCR5rxUZHSFczvfaNFK4ymEbEiccRX7VKchpqz0Y&m=IQKsEFqNC36EsBw0zS4WX9nSDUydia_pChJMrLGS8tA&s=AHXmULzSOVmCjHyyvurj_4viK6EvNe4T2q3rWYfOMC0&e=
_______________________________________________
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
|
