Bug 228274

Summary: [FieldAssist] Provide support for long running / deferred proposal calculations
Product: [Eclipse Project] Platform Reporter: Mario Winterer <mario.winterer>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: NEW --- QA Contact:
Severity: enhancement    
Priority: P3 CC: contact, dsciamma, emoffatt, eostroukhov, francois.rigault, juergen, remy.suen, tomasz.zarna
Version: 3.4   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Mario Winterer CLA 2008-04-22 16:21:36 EDT 
The current fieldassist-API does not support content proposal providers with long running proposal calculations (e.g. look up the proposals in a database etc.) or deferred proposal delivery.

The main problem is that the IContentProposalProvider's getProposals() method is just called once. It would be nice if class ContentProposalAdapter had an additonal public method "refreshProposals" that force the popup to refresh its proposal list and call getProposals() again on the IContentProposalProvider.

This would enable the possibility to run a background job that does proposal calculation to fill the IContentProposalProvider's (internal) proposal list. By periodically refreshing the proposal popup, the calculated proposals would appear by and by in the popup-list.
Comment 1 Susan McCourt CLA 2008-04-23 17:16:55 EDT 
This is a reasonable enhancement, however we are past API freeze for 3.4.  Should be considered during the early 3.5 bug triage/planning
Comment 2 Susan McCourt CLA 2008-09-17 18:25:26 EDT 
*** Bug 211778 has been marked as a duplicate of this bug. ***
Comment 3 Susan McCourt CLA 2009-07-09 17:37:57 EDT 
as per 2009 triage guidelines
Comment 4 Juergen Weber CLA 2010-12-10 09:45:34 EST 
This would be usefull for large content, e.g. results of database or LDAP queries. So the user would type A, you'd select count(A*) , user types B, and so on.
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:29:39 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.