← Back to team overview

nrtb-core team mailing list archive

[Blueprint plug-in-arch] Plug-in Architecture Guidelines

 

Blueprint changed by Rick Stovall:

Whiteboard changed:
- We need initial discussion on the email list to center around top level
- methodology. Some of the most critical open issues are:
+ Okay, I'm paring down the features for the initial alpha:
  
- 1. Use dynamic links libraries or an embedded scripting language.
- 2. What simulation objects will be pluggable in the alpha phase.
- 3. How much freedom to affect the simulation should plug-ins have?
+ 1. We'll stay with C++ for plugin implementation.
+ 2. For initial Alpha only, we will not use dynamic loading, although the "plugins" will be implemented as discrete code modules which use the target plugin API.
  
- https://launchpad.net/ricks-ga is a proof-of-concept project to evaluate
- the use of Lua as a scripted plugin approach.
- 
- Lua examples: http://www.wellho.net/mouth/2455_Lua-examples-coroutines-
- error-handling-objects-etc.html
+ We are well on the process of defining the API, and I've started the
+ abstract base class which will be used by all the plugins. See the
+ linked documentation for details.

-- 
Plug-in Architecture Guidelines
https://blueprints.launchpad.net/nrtb/+spec/plug-in-arch