Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [eclipse.org-feep-stakeholders] Friends of Eclipse Enhancement Program: 2017 plan
I'm all in favor of any idea that would make the IDE more modern and appealing. However, I would only try to maximize screen usage via styling. The whole scrollbar story on Windows leads to dirty hacks or some changes at SWT level against its philosophy (which is "use native widgets when avail."). 

The sad thing is that there are APIs on Windows to let you have a modern UI and the same kind of scrollbars as on GTK3/Cocoa: WPF. Unfortunately, the SWT/WPF port has been abandoned (I don't know the reasons though; if anyone knows the story, I would be glad to learn it). 

IMHO, reviving this port is the only way to go forward on Windows. This would also gives us theming facility at the toolkit level as with GTK3 and Cocoa (and the misplaced e4 theming engine could then be ditched). However, I'm reluctant to create a FEEP item for this task as this is a huge one. Any idea how it could be handled?

Cheers,
Mikael

Le 18 nov. 2016 à 19:35, Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx> a écrit :

Hi Mikaël (and FEEP community!),

I haven't brought it up very prominently yet, but I'd like bring up the idea of doing some work to maximize screen usage. Seehttps://bugs.eclipse.org/bugs/show_bug.cgi?id=506042

This kind of work could be split up in several sub-items I think.

What do you think?

Marc-Andre


From: eclipse.org-feep-stakeholders-bounces@xxxxxxxxxxx <eclipse.org-feep-stakeholders-bounces@xxxxxxxxxxx> on behalf of Mikaël Barbero <mikael@xxxxxxxxxxx>
Sent: Friday, November 18, 2016 11:53 AM
To: eclipse.org-feep-stakeholders@xxxxxxxxxxx
Subject: [eclipse.org-feep-stakeholders] Friends of Eclipse Enhancement Program: 2017 plan
 
Dear community,

I'm reaching you out to prepare FEEP for 2017. The Eclipse Foundation is committed to help improving the upcoming Oxygen release. As such it is willing to start to work on new FEEP items very early next year. For that purpose, we would like to gather your ideas / priorities about the work items that should be open for bidding next year. As a reminder, the completed items from last year are listed here https://projects.eclipse.org/development-efforts?field_work_state_value=closedCompleted&sort_by=field_work_projects_nid&sort_order=DESC.

Besides the items that are still opened from this year (https://projects.eclipse.org/development-efforts), I would like to propose these three additional ones:

- SWT/Chromium integration (https://bugs.eclipse.org/bugs/show_bug.cgi?id=405031). Provide a CEF fragment on each major platforms (win 32/64 / linux 32/64 / macos 64) and use it when doing new Browser(parent, SWT.EMBEDDED_CHROMIUM).
- Improve p2 repo download speed by using mirrors for p2 artifacts/metadata repositories (https://bugs.eclipse.org/bugs/show_bug.cgi?id=507657)
- Modernize the Eclipse Help look & feel (https://bugs.eclipse.org/bugs/show_bug.cgi?id=501718).

Do you have comments or concerns about these new items or the old ones? 

Please, give us your suggestions for other bugs or topics that you think should be addressed next year. 

Thanks,
Mikael

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

Back to the top