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

  




 

 

RSE Base Plugin Class

You may find it of value to base your own plugin class on the RSE-supplied base plugin class. If so, there are some methods you are encouraged to create or override in your class. The benefits of using this as your base class is the inherited methods you can access.

Methods required in your plugin subclass

To use the RSE base plugin class org.eclipse.rse.ui.SystemBasePlugin , you subclass it for your own plugin class, and supply some key static methods of your own:

  • getDefault(). Return a singleton instance of your plugin.
  • getResourceBundle(). Return the resource bundle for your plugin. This is stored in a static field, initialized in your constructor by calling the loadResourceBundle(...) inherited method.
  • getString(String key). Return a translated string by calling the inherited method getString(ResourceBundle rb, String key) , passing in the static resource bundle field.
  • getPluginMessageFile(). Return your RSE message file instance, initialized in your constructor by calling loadMessageFile(...) .
  • getPluginMessage(String msgID). Return the SystemMessage for the given ID, by calling the inherited method getMessage(getPluginMessageFile(), msgId) . You will call this method often to get message objects.

You may also override some RSE-supplied instance methods:

Of course, there are the usual eclipse-supplied instance methods to override too:

  • initializeDefaultPreferences(). Good place to call the initDefaults() method of your preference pages. Be sure to call super.initializeDefaultPreferences().
  • startup(). Good place to register adapters and so forth. Be sure to call super.startup() at the beginning.
  • shutdown(). Good place to close any open communication layers. Be sure to call super.shutdown() at the end.

Methods inherited from the RSE base class

The methods you get access to by using the RSE-supplied base plugin class include:


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