Bug 240362 - [content assist][api] A categorized content assist processor
Summary: [content assist][api] A categorized content assist processor
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-07-10 13:03 EDT by dakshinamurthy.karra CLA
Modified: 2019-09-06 16:07 EDT (History)
1 user (show)

See Also:

Attachments
Java Source File (8.70 KB, text/plain)
2008-07-10 13:05 EDT, dakshinamurthy.karra CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description dakshinamurthy.karra CLA 2008-07-10 13:03:34 EDT 
Build ID: I20080617-2000

Steps To Reproduce:


More information:
Though the content assist has the infrastructure to provide different categories of content assists for the same content type, this could not be leveraged because there is no simple way to access it.

I am uploading an attachment that has a definition for CategorizedContentAssistantProcessor that allows to add multiple processors to it and in turn that can be added to ContentAssistant. The user will be able to cycle through the categories (a.k.a JDT).

I am not sure whether others will be interested in this.
Comment 1 dakshinamurthy.karra CLA 2008-07-10 13:05:16 EDT 
Created attachment 107107 [details]
Java Source File

While creating the bug, that attachment failed. Adding again.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:07:32 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.