Community
Participate
Working Groups
I20050510-0010 The new open java type dialog has a significantly different user interface than the open resource dialog. The open resource dialog should probably be updated to behave the same.
*** Bug 94443 has been marked as a duplicate of this bug. ***
Info from Nick: In the UI summit call, the suggested approach to making Open Resource be consistent with Open Type was: - look at the Open Type implementation in JDT - push down parts of it that are generally useful (e.g. dialog structure, background population, camel-casing) - implement Open Resource in terms of this - make it so that JDT can migrate Open Type to this framework, time-permitting (needs to be easy for them)
I will look at this for 3.2 M3.
By the way. it would be nice to get rid of those annoying modal progress dialogs duting this integration. There are at least two cases when they appear - initial indexing and index verification (generally after any switch from and back to Eclipse). Second one appears for about 10 seconds and it is definetely too long intervention.
Eugene, this can't be done in the general framework since it is specific for JDT. Major improvements have already be done for 3.1.1 and 3.2 M1. Verifications beside the first one which can't be avoided are only done when types are removed. So this occurrs far less. Another optimization is to do the verification in background. I have the code ready and it will go into M3. Needs some testing first since its not trivial ;-).
Dirk, actually that is what I meant. Please move this stuff to the background and show progess in a Open Type dialog itself (similar to search progress)
Adding TC for comment on jobs+background progress reporting inlined in the dialog.
Tod, the open type dialog has support for showing embedded background job progress. See ProgressUpdateJob in TypeInfoViewer.
Moving to M4, still working on some other items for M3.
note to self: see discussion in bug #93162
Susan, have you started any work here. I am working on a second instance of the open type dialog and might be able to provide some abstractions.
No, I've not started, but plan to do so this week, hopefully by Tuesday. So please keep me posted on what's happening and I'll annotate this bug when I start.
Moving milestone to M5. I have been looking at this on and off, but won't get it finished in time. There are two parts to this: 1. Factoring out the behavior for filtering, history, etc. (Dirk has already completed a good first pass at this and I've got a prototype that's been brought into Platform UI). It will likely appear as an advanced JFace viewer. 2. Adapting ResourceSelectionDialog to use this viewer, and adding other features such as CamelCase, etc.
Sorry, this is being punted from my 3.2 plan in favor of more pressing issues. If this bug gets reassigned to someone else, contact me for some old experiments/code from my M4 work. I know this is a much-requested feature, it just doesn't make the cut given everything else on my plate.
moving Open Resource related bugs to Szymon. Szymon, please move between you and Krystof as needed. Let me know if you have any questions. These are all the bugs I had related to OpenResource.
An initial pass at the API has been released. Szymon and Kryzstof - please mark the new API as experimental as we still might need to make some changes in 3.3.
Created attachment 49607 [details] New AbstractSearchDialog and ResourceSearchDialog patch AbstractSearchDialog is a new abstract class which should be used as super class for resource and type search dialogs.
Created attachment 49608 [details] Fixes according to Tod comments - EXPERIMENTAL taf - doubleclick selection - shows details field by default
Created attachment 49613 [details] Fixes according to Tod comments
Patch released.
Fixed
*** Bug 91227 has been marked as a duplicate of this bug. ***
