Bug 146527 - [Viewers] New JFace viewer for two lists.
Summary: [Viewers] New JFace viewer for two lists.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.2   Edit
Hardware: PC All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL: http://ketan-p.livejournal.com/5694.html
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-06-12 05:40 EDT by Ketan Padegaonkar CLA
Modified: 2019-09-06 16:05 EDT (History)
4 users (show)

See Also:


Attachments
A sample app to demonstrate the viewer. (30.10 KB, application/zip)
2006-06-12 06:12 EDT, Ketan Padegaonkar CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ketan Padegaonkar CLA 2006-06-12 05:40:13 EDT
I stumbled upon a new JFace control when trying to fix this eclipse bug:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=131566.

See https://bugs.eclipse.org/bugs/show_bug.cgi?id=131566#c6 and
http://ketan-p.livejournal.com/5694.html for screenshots.
Comment 1 Ketan Padegaonkar CLA 2006-06-12 06:12:15 EDT
Created attachment 44125 [details]
A sample app to demonstrate the viewer.

This is a sample app to demonstrate the viewer, and the viewer. Run org.eclipse.jface.doublelist.example.DoubleListViewerTest#main
Comment 2 Tod Creasey CLA 2006-06-12 09:08:51 EDT
Ketan - thanks for your contribution. Could you attack your source to this bug - we can't look at it unless you have contributed it via Bugzilla.
Comment 3 Ketan Padegaonkar CLA 2006-06-12 09:36:55 EDT
(In reply to comment #2)
> Ketan - thanks for your contribution. Could you attack your source to this bug
> - we can't look at it unless you have contributed it via Bugzilla.
> 

Hi Tod, 
I have indeed attached by source to comment #2. I've exported the entire project including sources, .classpath and .project files.
Comment 4 Ketan Padegaonkar CLA 2006-06-12 09:40:42 EDT
(In reply to comment #3)
> (In reply to comment #2)
> > Ketan - thanks for your contribution. Could you attack your source to this bug
> > - we can't look at it unless you have contributed it via Bugzilla.
> > 
> 
> Hi Tod, 
> I have indeed attached by source to comment #2. I've exported the entire
> project including sources, .classpath and .project files.
> 

Sorry the above should have been comment #1 instead of #2 :(

Comment 5 Ketan Padegaonkar CLA 2006-07-19 10:52:11 EDT
Any progress on this ?
Comment 6 Boris Bokowski CLA 2006-07-26 19:06:30 EDT
Thank you for the patch - unfortunately I won't be able to look at this until after 3.3 M1. Marking as 3.3 M1 so that this will be on my radar at the end of M1.

Are there any places in the SDK where we could remove custom code by using this viewer?
Comment 7 Boris Bokowski CLA 2006-09-18 10:49:08 EDT
(In reply to comment #6)
> Are there any places in the SDK where we could remove custom code by using this
> viewer?

I am hesitant to put something into JFace that we don't use ourselves.  Could you please point me at existing dialogs/wizards that could use your two-list viewer? Thanks.
Comment 8 Ketan Padegaonkar CLA 2006-09-19 00:35:39 EDT
(In reply to comment #7)
> (In reply to comment #6)
> > Are there any places in the SDK where we could remove custom code by using this
> > viewer?
> 
> I am hesitant to put something into JFace that we don't use ourselves.  Could
> you please point me at existing dialogs/wizards that could use your two-list
> viewer? Thanks.
> 

No there are no places where this viewer could possibly replace/remove custom code. One place where I believe this could be used is to add/remove and change the order of buttons on the toolbar.
Comment 9 Boris Bokowski CLA 2009-11-26 09:54:57 EST
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 10 Eclipse Webmaster CLA 2019-09-06 16:05:50 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.