Developer

Understanding

• Architecture
• For SnipSnap version numbers see SnipSnap Version Numbers
• Snip render lifecycle explains rendering flow
• Snip storage lifecycle explains storage flow

Naming conventions

• <Name>Support is a support class that cannot be used on it's own, most of the time an abstract class. Example FilterSupport
• Base<Name> is a class with basic functionality which can be instantiated. Probably implements the interface <Name>. Example BaseRenderEngine
• <Name>Impl is a class that implements the interface <Name>. Usually this is the only implementation, otherwise it would be named Base<Name>. Example SnipSpaceImpl.
• Mock<Name> is a Mock object that implements <Name> or subclasses <Name>

CVS

• SnipSnap Subversion Access
• SnipSnap CVS Access (deprecated)

Subversion SVN Access

• SnipForge

Mailing List

• SnipSnap Mailing Lists

Developer resources

• Localization
• Macro Tutorial
• Advanced Macro Tutorial
• SnipSnap Macro Tutorial on how to write macros that use SnipSnap features
• Filter Tutorial
• List Formatter Tutorial 1
• List Formatter Tutorial 2
• Source Code Formatter Tutorial
• SnipSnap RenderEngine Tutorial

Others

• FAQ There are some developer questions answered

Radeox resources

• see http://radeox.org

Contributions

Third party extensions to SnipSnap can be found on the contributed page.