These recent comments are along the lines of "let's split Eclipse projects into even smaller separately installable pieces", which I think goes in the wrong direction. This might let an expert craft a finely tuned install of exactly the pieces they need, but makes the problem of plugin discovery, configuration, and management more painful. I think this hurts the novice or casual user, and even highly advanced users like Michael Scharf find this cumbersome. I would rather there be fewer choices a user has to make, even if it means bundling in things they might not need.
john
----- Original message -----
From: Kaloyan Raev <kaloyan.r@xxxxxxxx>
Sent by: ide-dev-bounces@xxxxxxxxxxx
To: Discussions about the IDE <ide-dev@xxxxxxxxxxx>
Cc:
Subject: Re: [ide-dev] Ctrl-1 driven development
Date: Sat, Oct 17, 2015 2:27 AM
And one similar question from me :-)
Why I need to install JDT just to have a Properties file editor?
Kaloyan
On Sat, Oct 17, 2015 at 8:39 AM, Maarten Meijer
<mjmeijer@xxxxxxxxxxxxxx> wrote:
Also, why does Platform always include Debug core. Editing and Building/validating make sense for data file type projects, but data files are never run and debugged.
Make Debug an optional feature
Kind regards
Maarten Meijer
Creator EulumdatTools
Op 17 okt. 2015 om 01:30 heeft Michael Scharf <eclipse@xxxxxxxxx> het volgende geschreven:
>>
>> Yeah, my first reaction was, why is the XML editor in WTP? It’s always one of the first things I install into a fresh Eclipse install.
>
> I have the same question about makefile support: why do I have to install CDT?
