DtEditorPlugin Class Reference

The plugin manager will load external loadable objects in order to provide additional functionality to the front-end. More...

Inheritance diagram for DtEditorPlugin:

Public Member Functions
	DtEditorPlugin (const DtString &libName, bool addPlatExt=true, bool useLazyEval=true)
virtual	~DtEditorPlugin ()
virtual bool	init ()
virtual bool	init (DtEditorExtensionInterface *, DtTMApplication *)
virtual bool	postAppInitialize (DtEditorExtensionInterface *iface, DtTMApplication *app)
Public Member Functions inherited from DtTMPlugin
	DtTMPlugin (const DtString &libName, bool addPlatExt=true, bool useLazyEval=true)
virtual	~DtTMPlugin ()
virtual bool	init (DtTMApplication *)
virtual bool	postAppInitialize (DtTMApplication *)
virtual void	unloadPlugin ()
DtTMApplication *	createApplication (int argc, char **argv)
const DtPluginInformation &	pluginInformation () const
virtual void	pluginInformation (std::string &str) const
virtual bool	checkVersion (const QString &curVersion)
	Returns false if there is a version mismatch.
virtual bool	isValid () const
virtual DtString	libraryName () const
virtual const char *	error () const

Protected Attributes
DtEditorInitializePluginFcn	myEditorPluginInit
DtEditorPostInitializePluginFcn	myEditorPostPluginInit
Protected Attributes inherited from DtTMPlugin
DtPluginInformation	myPluginInformation
DtInitializePluginFcn	myPluginInit
DtPostAppInitializeFcn	myPostAppInitialize
DtUnloadPluginFcn	myUnloadPlugin
DtDynamicLibrary *	myDynamicLibrary

Detailed Description

The plugin manager will load external loadable objects in order to provide additional functionality to the front-end.

The file pluginExtension.h defines the template for what you can and/or need to define in order to be considered a plugin to the front-end.

The plugin manager will, upon calling the init() method, read plugins from the supplied .mtl file. It will also scan the argv command line for the –loadPlugin command to schedule to load a plugin. Once the list of loadable plugins has been created, the plugins will be found and loaded into the system, calling initializePlugin for each plugin supplied.

Once all the plugins have been loaded and initialized, the application object will be created and returned to the user. This application will be in an uninitialized state, and it will be up to the developer to init the application from the factory. Also, it is up to the developer to delete the application object Note that this class is only used for the opd and entity editors

Constructor & Destructor Documentation

DtEditorPlugin::DtEditorPlugin	(	const DtString &	libName,
		bool	addPlatExt = true,
		bool	useLazyEval = true
	)

virtual DtEditorPlugin::~DtEditorPlugin ( )

virtual

Member Function Documentation

virtual bool DtEditorPlugin::init ( )

virtual

Reimplemented from DtTMPlugin.

virtual bool DtEditorPlugin::init ( DtEditorExtensionInterface *  , DtTMApplication *    )

virtual

virtual bool DtEditorPlugin::postAppInitialize ( DtEditorExtensionInterface *  iface, DtTMApplication *  app  )

virtual

Member Data Documentation

DtEditorInitializePluginFcn DtEditorPlugin::myEditorPluginInit

protected

DtEditorPostInitializePluginFcn DtEditorPlugin::myEditorPostPluginInit

protected

---

The documentation for this class was generated from the following file:

• include/vrfGuiCommon/editorPluginManager.h