Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 372348

Summary:	Use of non-Eclipse GUI controls due to limitations/bugs in core Eclipse controls
Product:	Community	Reporter:	Michael Jastram <michael>
Component:	Architecture Council	Assignee:	eclipse.org-architecture-council
Status:	RESOLVED WORKSFORME	QA Contact:
Severity:	major
Priority:	P3	CC:	daniel_megert
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Michael Jastram

2012-02-23 10:25:31 EST

I had a specific problem with a JFace control that ultimately pushed me into using a non-Eclipse control, which in turn triggered a CQ.  Wayne suggested to file an issue here to address the more general aspect of this problem:

https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5791#c15

The specific problem was that I need a table control for my Eclipse project.  A critical requirement was the ability to have flexible row heights within the table (as you would expect from any spreadsheet).  Of course I started with the JFace table. This worked in my development environment (Linux).  On Windows, however, all rows in the table had the same height.  I tracked this down to the following bug from 2006:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=148039

As there is no Windows expertise on my team, we could not fix the control.  This was a showstopper for using the JFace table.  We eventually decided to go with AgileGrid, a control hosted on SourceForge. In retrospect, Nebula could have been a better choice:

http://www.eclipse.org/nebula/

The general problem is that developers pick other controls, thereby creating inconsistencies, IP issues, more buggy implementations, etc.

I cannot judge whether this is an isolated problem or a more general problem.  I guess it's more general, otherwise there wouldn't be the need for a project like Nebula.

Comment 1 Eclipse Genie

2014-10-29 18:51:08 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 2 Michael Jastram

2014-10-30 05:35:22 EDT

> or became less pressing for some reason

Considering that the underlying bug (#148039) is now 8 years old, I just moved on with alternative controls.  But it's unfortunate, because the idea of SWT/JFace is good.

Comment 3 Eclipse Genie

2016-10-20 05:43:51 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Dani Megert

2016-10-20 12:51:07 EDT

Closing as WORKSFORME as per comment 2.