Follow Techotopia on Twitter

On-line Guides
All Guides
eBook Store
iOS / Android
Linux for Beginners
Office Productivity
Linux Installation
Linux Security
Linux Utilities
Linux Virtualization
Linux Kernel
System/Network Admin
Programming
Scripting Languages
Development Tools
Web Development
GUI Toolkits/Desktop
Databases
Mail Systems
openSolaris
Eclipse Documentation
Techotopia.com
Virtuatopia.com

How To Guides
Virtualization
General System Admin
Linux Security
Linux Filesystems
Web Servers
Graphics & Desktop
PC Hardware
Windows
Problem Solutions
Privacy Policy

  




 

 

Eclipse Plug-in Developer Guide
Previous Page Home Next Page

Adopting 3.5 mechanisms and APIs

This section describes changes that are required if you are trying to change your 3.4 plug-in to adopt the 3.5 mechanisms and APIs.

  1. Delete creation of ContentAssistAction action
  2. Switch to new look of FilteredTree

1. Delete creation of ContentAssistAction action

As of 3.5, the AbstractTextEditor creates and registers the content assist action. This means that subclasses no longer need to create and register their own content assist action. It is recommended to remove that code and to use org.eclipse.ui.texteditor.ITextEditorActionConstants.CONTENT_ASSIST when adding that action to the main menu or toolbar.

Same applies to the action that shows content assist context information (org.eclipse.ui.texteditor.ITextEditorActionConstants.CONTENT_ASSIST_CONTEXT_INFORMATION).

2. Switch to new look of FilteredTree

As of 3.5, the FilteredTree comes with a new look. It is recommended to switch to that new look by using one of the two new constructors. Subclasses that switch to the new look must carefully review their UI because depending on what the subclass does, it might result in a broken look. In that case, the code in the subclass needs to be adjusted.


 
 
  Published under the terms of the Eclipse Public License Version 1.0 ("EPL") Design by Interspire