Bug 246874

Summary:	[Viewers] ContainerCheckedTreeViewer should be moved to JFace
Product:	[Eclipse Project] Platform	Reporter:	Jake <jake.cobb>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	Keywords:	helpwanted
Version:	3.4
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Jake

2008-09-10 11:16:01 EDT

Build ID: I20080617-2000

Steps To Reproduce:
ContainerCheckedTreeViewer is currently in the org.eclipse.ui.dialogs package.  This class is very general use, extends directly from a JFace viewer (CheckboxTreeViewer) and has no dependencies on Eclipse APIs that are not included in SWT and JFace.  Therefore, it should be moved to the org.eclipse.jface.viewers package where it can be utilized by standalone SWT/JFace applications.

More information:
I see this as a very easy move since it does not force any other classes, which may not belong there as obviously as this one does, to move to JFace.  I currently have a standalone SWT/JFace application using only jars for:
swt
org.eclipse.core.commands
org.eclipse.equinox.common
org.eclipse.jface
org.eclipse.osgi

Extracting ContainerCheckedTreeViewer and its two inner classes, placing them in a new jar and including that jar in the build path is sufficient to use this class in the standalone app.

Comment 1 Jake

2008-09-11 09:27:09 EDT

Changed severity to enhancement.

Comment 2 Boris Bokowski

2008-09-12 12:29:18 EDT

We're not very happy with this class right now (see bug 170521 and bug 17907) so I would be hesitant to move it somewhere else without having those issues addressed.

Comment 3 Boris Bokowski

2009-11-26 09:55:57 EST

Hitesh is now responsible for watching bugs in the [Viewers] component area.

Comment 4 Eclipse Webmaster

2019-09-06 16:15:55 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.