Plug-In Architecture for Customization
Developers can use Traction® TeamPage's plug-in architecture to add new functions to TeamPage or override and extend the appearance and behavior of standard TeamPage features and interfaces. The architecture preserves plug-ins in their own directories so the installation of new plug-ins or software updates is non-destructive.
Plug-in extensions are packaged as self-contained files that are easy to create, share, and install in an extensions directory. Plug-in extensions are preserved across software updates to simplify software maintenance as well as initial deployment.
The TeamPage plug-in architecture includes Server Setup web page that makes it easy for server administrators to install and configure options plug-in extensions. A personal setup page is also provided to make it simple for individual users to configure their own plug-in settings. For example, each user can specify a Jabber Username and edit notification options for when using Traction's Jabber notifier plug-in.
Here is a an image of the page where you upload, delete and manage plug-ins, the Jabber notifier is selected:
When you click Configure, a form pops up allowing the administrator to setup server level properties and default user level properties of the plug-in.
Plug-in's can extend or override Traction's Skin Definition Language for simple UI extensions (SDL), or use Traction's Java Software Developer Kit (SDK) to create new SDL tags, derive from Traction's Java SDK components, or create new authentication, notification and other components using the SDK's run-time extensible interfaces. Traction Customers have full access to the Java source code and JavaDoc of the SDK layer - including the full SDL implementation - at no additional cost.