Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320159

Summary: Preference for favorite namespaces
Product: [Tools] CDT Reporter: Tomasz Wesolowski <kosashi>
Component: cdt-editorAssignee: Project Inbox <cdt-editor-inbox>
Status: ASSIGNED --- QA Contact: Jonah Graham <jonah>
Severity: enhancement    
Priority: P3 CC: yevshif, zeratul976
Version: 7.0   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Bug Depends on:    
Bug Blocks: 319175    
Attachments:
Description Flags
Favorites tab in Preferences
none
Favorites tab in Preferences none

Description Tomasz Wesolowski CLA 2010-07-17 06:23:51 EDT
For bug 319175, it shall be possible to specify a list of namespaces, the members of which would be always suggested in Context Assist.
Comment 1 Tomasz Wesolowski CLA 2010-07-17 06:29:01 EDT
Created attachment 174556 [details]
Favorites tab in Preferences

I've ported the "Favorite static members" from JDT for handling Favorite namespaces in C++.

Cosmetic issues:
- the description doesn't wrap properly
- help needs to be written?
Comment 2 Tomasz Wesolowski CLA 2010-07-17 07:57:02 EDT
Created attachment 174557 [details]
Favorites tab in Preferences

updated with licence text
Comment 3 Anton Leherbauer CLA 2010-08-09 09:09:36 EDT
Thanks for the patch.  Looks good basically, a few issues remain:

1. The Eclipse guideline for the Copyright header is to specify only the first and last year, i.e. instead of
 * Copyright (c) 2007, 2009, 2010 IBM Corporation and others.
it should be
 * Copyright (c) 2007, 2010 IBM Corporation and others.
2. Please adjust the @since tags copied from JDT
3. Add a @since tag and javadoc to the new preference constant.
4. To enable wrapping of the label, you need to add the SWT.WRAP flag in DialogField (see JDT's counterpart).
Comment 4 Nathan Ridge CLA 2017-01-03 19:14:14 EST
Tomasz, do you plan to finish this patch?
Comment 5 Jonah Graham CLA 2019-12-30 17:05:11 EST
This bug was assigned and targeted at a now released milestone. As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and marked the bug as resolved.