Skip to content

Code structure

Jump to bottom Edit New page
Pawel Baran edited this page Apr 1, 2020 · 10 revisions

The code of Revit_Toolkit is different from standard BHoM pattern, which is caused by the fact that all code base referencing Revit API needs to run inside the Revit thread. It is split into two realms:

  • BHoM side - standard BHoM toolkit structure:
    • Revit_oM (BH.oM.Adapters.Revit) - Revit_Toolkit-specific classes, mainly settings/config and wrappers for Revit types
    • Revit_Engine (BH.Engine.Adapters.Revit) - methods to process the objects from Revit_oM
    • Revit_Adapter (BH.Adapter.Revit) - BHoM side of Revit-specific implementation of BHoMAdapter without CRUD, which is sitting on the Revit side of the solution (see below)
  • Revit side:
    • Adapter_Revit_UI and Revit_UI (BH.UI.Revit) - Revit side of Revit-specific implementation of BHoMAdapter, including adapter action methods, CRUD as well as Revit Listener plugin and event handlers
    • Revit_Engine (BH.Engine.Adapters.Revit) - methods to process the objects from Revit_oM

Revit_Toolkit Samples

Home

Clone this wiki locally