Game Development Reference
In-Depth Information
This is the main editor interface at a glance. Its methods are quite self-explanatory, the most used methods being
the
Call(...)
method, which is used to execute commands by their name and requires a parameter “bag” (optional),
and the
IParameterValues
interface, created before the call by the user using the
CreateParameterValues()
method and then filling up the parameter values for the command to use.
Plug-ins
The plug-ins are DLLs loaded by the core editor DLL. Each plug-in will expose and register its commands in the
editor's ecosystem and provide information about these commands through a manifest file associated with
the plug-in's DLL.
A core editor plug-in consists of two files:
Example.dll
)
•
A C++ DLL file, the plug-in code (
Example.plugin.xml
4
), having the same base file name as the plug-in's DLL
(Example), containing information about it.
•
A manifest file (
Listing 11-4 shows an example of a plug-in manifest file.
Listing 11-4.
Plug-in Manifest File
<plugin
name="Example"
description="The example editor plugin"
author="Nicusor Nastase Nedelcu"
url="http://some.com"
guid="31D91906-1125-4784-81FF-119C15267FC3"
version="1.0.0"
minEditorVersion="1.0.0"
maxEditorVersion="2.0.0"
icon="example.png"
unloadable="true">
<dependencies>
<depends nameHint="OtherPlugin"
guid="DAA91906-1125-4784-81FF-319C15267FC3" />
<depends nameHint="SomeOtherPlugin"
guid="F51A2113-1361-1431-A3EA-B4EA2134A111" />
</dependencies>
<commands>
<command name="get_some_thing"
info="This command get something">
<param name="someParam1" type="int32"
info="this is parameter 1" />
<param name="someParam2" type="float"
info="this is parameter 2" />
</command>
</commands>
</plugin>
