We’ve had discussions about an IDE commons project where things like the Launch Bar could go. Wayne was still interested in that last we talked about it.
Of course, everything we put in an IDE Platform should be consumable by JDT, which means JDT would have to separate from the Platform build. I’m not sure how warm everyone is to that idea.
Anyway, I don’t see much changing there at the moment. I’d rather focus on making sure we have the right features, no matter what project they are hosted in. If everyone contributes to every project and earn committer rights, we end up with one project
at the end anyway :).
It sounds like what you are proposing is an "IDE Platform". That is, a layer above Platform that provides core functionality for building an IDE. Most likely Debug and LaunchBar would be belong there, and possibly Resources as well.
Switching non-guidelines related discussion to ide-dev.
On 2016-09-19, 10:50 AM,
"ui-best-practices-working-group-bounces@xxxxxxxxxxx on behalf of Lars
Vogel" <ui-best-practices-working-group-bounces@xxxxxxxxxxx on behalf of
>> At this point, the issues users are facing have much more to do with
>>the language plug-ins than they do
>> with the Platform.
>I completely agree but IMHO the platform work is still very important.
>The way I see it, if we in platform (and I tend to think of platform
>as the "Eclipse top-level project including JDT and PDE) do a good
>job, we make it easier for the others to make a good job.
That¹s true to a certain extent. But platform fixes don¹t get you Gradle
support in Andmore, for example :). Or does/should it? Very similar to the
XML editor discussion happening now on eclipse-dev.
In the past, there has seemed to be an artificial barrier that IDE things
shouldn¹t end up in the Platform, only things that the IDE shares with
RCP. But then the Resources and Debug plug-ins are platform which teaches
us that that wasn¹t always true.
In fact, people point at e4 being the end. I can make a plausible argument
that RCP was really the end ;).