Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-vision] Involve important stack holders in this group?
Sounds good with the discussion about the involvement of new people.

Here also my technical points which I consider important for the future of the Eclipse IDE, maybe we can also discuss them in the call. Some might consider them as feature requests but I think a list of the most important IDE features will also help us to guide our effort.

1.) Update the programming model for the Eclipse IDE to Java 8 (or Java 9 once out)

For example provide functional interfaces for SWT listeners. Providing Java 8 in our API will make contributions more attractive and smooth.

2.) No blocking / allow cancellation in the UI by the Builder framework

This one hits me personally at least a few times per day. The automatic builder is running and block me from doing anything else.
AFAIK main issue ishttps://bugs.eclipse.org/bugs/show_bug.cgi?id=329657
See also http://zarnekow.blogspot.de/2014/10/musing-about-eclipse-ux-metaphors.html

3.) Best support for Maven and Gradle

I think that one is already in the list, but I think we should also here what the next build superstar Gradle needs here. Quote from the list:"Some discussion of integration problems between Maven and JDT. Dani thinks there may be a mechanism available to address their classpath problems."

Here is some information I got from Igor Fedorenko on this topic:

------------------------------------------------------------------------------------------------------
Yes, I have pretty good idea what I need from JDT to properly support
multi-module/nested maven projects in m2e. I even did some exploratory
prototype couple of years ago to understand the problem and possible
solutions. Based on that prototype, what we need boils down to two
features.

We need to invoke java compiler from m2e builder directly, bypassing
JavaBuilder. I believe this is relatively small change to JDT,.

We also need to associate java sources+classpath+options with any
workspace folders, not just IProjects. This is a pretty big change, I
believe, and I was not able to implement it without breaking existing
API a little.

Last time I brought this up I was told "it's definitely out of scope for
the JDT team". This is why I decided not to invest any time into this
until we (Takari) can commit resources needed to do this ourselves, and
likely maintain JDT fork for some time.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=356450#c15

------------------------------------------------------------------------------------------------------

4.) Best refactoring, quickfix and content assists support possible

IntelliJ has zero delay for content assists, which makes it feel much more responsive. Shortcut in IntelliJ are more consistent and simpler to use, for example to extract a String you do not have to mark the String first, the cursor position is sufficient. Eclipse leaves several great options unselected in its defaults, i.e., automatic placement of the semicolon.

5.) JDT to open up for Java languages like Groovy

Andy or Dani might be able to tell what is needed here.

6.) Make the Debug perspective obsolete

I think we should integrate the Java debug views into the Java perspective and remove the automatic switch to the Debug perspective. IntelliJ uses the same approach and it is much nicer IMHO for the user.

7.) Implement and use the Job Scheduler parallelization patch from Google

Google promises a factor of 3x for the search and I think this allows to enhance also other functionality in the future.

8.) Give decent error message if Eclipse 64 / 32 bit is started on a 32/64 bit JVM

AFAIK Eclipse just crashes if started on a wrong JVM. This is very annoying for the user. In case it is possible to catch this error and return a user readable error message we would have happier customers of the Eclipse IDE.





On Mon, Nov 17, 2014 at 2:49 PM, Daniel Megert <daniel_megert@xxxxxxxxxx> wrote:
I suggest we quickly discuss and decide during the next meeting,

Dani



From:        Lars Vogel <lars.vogel@xxxxxxxxxxx>
To:        For discussion regarding the future of the platform <platform-vision@xxxxxxxxxxx>
Date:        15.11.2014 21:14
Subject:        Re: [platform-vision] Involve important stack holders in this group?
Sent by:        platform-vision-bounces@xxxxxxxxxxx



Thanks Mike, as a late joiner I was not aware of that. I still think my proposal fits to that requirement.

At least Terrys team is helping with the Eclipse IDE, Andy is AFAIK a JDT core contributor and this Spring IDE team does a lot of Eclipse improvement work. I had email contact to Hans and he told me that he hired someone for his team to work on improved Gradle support for the Eclipse IDE.
Maybe by involving them, we could activate more resources from them. At least inviting them to hear what is important for them, would be interesting for me.

But I wait to hear what the others have to say. As I said earlier, I was a late joiner to this group.
Best regards, Lars

On Sat, Nov 15, 2014 at 9:03 PM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx> wrote:
Lars,

The original idea was to include those who had "skin in the game". E.g. Who were putting resources into the platform. 

That doesn't mean I'm against your suggestions. I'm simply stating what the original rationale was.

Mike Milinkovich
mike.milinkovich@xxxxxxxxxxx
+1.613.220.3223 (mobile)
From: Lars Vogel
Sent: Saturday, November 15, 2014 1:12 PM
To: For discussion regarding the future of the platform
Reply To: For discussion regarding the future of the platform
Subject: [platform-vision] Involve important stack holders in this group?


Hi,
this might have been discussed in the past but would it makes sense to involve important leaders outside our inner circle in this discussion?

For example I could image we would get great input from:

Hans Dockter - Gradle
Andy Clemens - Spring IDE / Groovy
Terry Parker - Google IDE tools lead
I personally can images that these people would have valuable insights for our future work to make the Eclipse IDE greater.

Best regards, Lars

--
Geschäftsführer

vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com


_______________________________________________
platform-vision mailing list
platform-vision@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-vision

_______________________________________________
platform-vision mailing list
platform-vision@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-vision



--
Geschäftsführer

vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com_______________________________________________
platform-vision mailing list
platform-vision@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-vision

_______________________________________________
platform-vision mailing list
platform-vision@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-vision




--
Geschäftsführer

vogella GmbH

Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx, Web: http://www.vogella.com

Back to the top