What is the storm editor?
The storm editor combines several editors into one. Most of these can be used independently of each other.
What's “WIP” to do with storm?
WIP stands for work in progress. That's the state the editor is currently in as you've probably guessed already. Some parts are ready for regular use, others are still experimental and the API is still in flux. You've been warned.
Scene Editing
Storm let's you edit scenes as defined via the dotScene format. It let's you edit scene nodes and their attached objects (lights, particle systems, mesh instances etc) as well as environmental settings.
What is dotScene? The dotScene format has originally been developed as a scene description format for OGRE3D. It's general enough to be of use for other engines either for direct import or data transfer. The author of storm is one of the creators and maintainers of the dotScene format. The format is supported by growing number of editors and im- and exporters.
Interoperability with OGRE3D
Storm can be used to define and modify scenes designed to be used with OGRE (http://www.ogre3d.org) and other engines utilizing the dotScene format.
Lighting
Storm provides a front end for radiosity based lightmap generation using OgreFSRad.
Graphical and physical models
Storm can be used to create graphical and physical models. Graphical models are similar to fragments of scene graphs while physical models define static and dynamic actors including collision proxies and shapes and more.
High-level entities
Editing of Yapp's high-level entities is supported natively, including their graphical and physical submodels and reflected properties.
Custom entities and pluggable properties
The easiest way to integrate new information on existing objects into the editor is to attach new properties to them via the generic pluggable property backend. It allows to persist data using various possible backends (e.g. XML or RDBMS). Furthermore regular property plugins can be used for complex properties which cannot be handled otherwise.