Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Here we describe and discuss how to extend the blender-osm addon via a separate Blender addon (i.e. an addon for the blender-osm addon).
There are a number of scenarios how blender-osm and an extension can interact.
blender-osm is the master, extension is the slave
blender-osm serves as the master addon, the extesion serves as the slave addon.
blender-osm is the slave, extension is the master.
Example: OpenStreetMap 3D editor for Blender. Currently only the export from Blender to an OpenStreetMap has been done. Additional work is needed based on the NP Station to provide creating a simple 3D building for OSM in Blender.
Here the OSM editor simply imports the blender-osm modules responsible for creating specific roof shapes.
Extension provides a well known functionality
The extension provides a well known functionality which isn't specific for the blender-osm addon.
Here the blender-osm (or another addon) checks if the addon for the custom map projections is installed and activated (?). If yes, the master addon imports the required stuff from the extension. The master addon must be aware of the module, class and function names in the extension.