Creating Additions to Existing Speckle Connectors

Help
, ,
1

Hello again.

I wanted to ask regarding what the process is for modifying the source code of a connector to add a feature to it, precisely the Revit connector and adding the ability to receive selections in Revit instead of receiving the entire stream. I wanted to ask if we could do that and if so what would the procedure be?

2

All Speckle connectors that we author are fully open-sourced.

If it is within your team’s capability, you can do so by forking the appropriate repo and making code amendments. If you want these changes considered to be added to the core, the PR and review process standards are the same as for other open-source projects.

Full warning: as we are engineering Speckle connectors from the ground up, the likelihood of a PR against the v2 connectors is unlikely to receive much attention/assistance, and any PR against v3 will be premature.

While we have discussed your described workflow as part of any future Mapper initiative, there is no timeline.

My recommendation is that if your selection for receiving data into Revit is not entirely arbitrary each time, then you work toward either:

  1. Instead of publishing whole models, publish discrete data to specific submodels - well-named means recipients will be completely clear about what is about to update their home models
    or
  2. Publish to a model and run a Speckle Automate function to split that data exchange in predetermined ways into submodels

Option 1) is more straightforward and requires discipline on the publisher’s part, 2) is more elaborate but is the least intrusive into the Author and Recipient’s workflow. Both options assume consistent selectivity.

3

Thank you for the response. I will discuss it with my team and we will see where to go from there.

1 Like