Topic: Plugins Feature

Kommute now supports Plugins feature.

To see how is written  different then a normal Qt project
look on SVN plugins examples:
http://kommute.svn.sourceforge.net/view … c/plugins/

Each Plugins project file has this same structure:

#=== this part is common (similar) for all plugin projects =====================
TEMPLATE      = lib
CONFIG       += plugin debug

# this is directory, where PluginInterface.h is located
INCLUDEPATH  += ../

# and, the result (*.so or *.dll) should appear in this directory
DESTDIR       = ../bin
OBJECTS_DIR = temp/obj
RCC_DIR = temp/qrc
UI_DIR  = temp/ui
MOC_DIR = temp/moc


# the name of the result file;
TARGET        = $$qtLibraryTarget(puzzle_plugin)

HEADERS     += ../PluginInterface.h  \
               src/PuzzlePlugin.h
SOURCES     += src/PuzzlePlugin.cpp
               
#===============================================================================

for each new Project must write a Class for this Plugin like MyPlugin.cpp/MyPlugin.h
and each Class Plugin need the PluginInteface.h as header.

look on the Example PuzzlePlugin.cpp/PuzzlePlugin.h to write this.
and its easy to port a Qt4 application as Plugin for Kommute.

http://kommute.svn.sourceforge.net/view … iew=markup
http://kommute.svn.sourceforge.net/view … iew=markup