Based on Local Development Environment, About Dynamo Connector

Help
, , ,
1

Hello, Community!

I am currently exploring Speckle in a local development environment to evaluate its functionalities. Among them, I am focusing on the Dynamo Connector, and I would greatly appreciate it if you could provide some clarification on the following points.

  1. In the current local development setup, the Dynamo Connector appears to use port 3000 and works with stream URLs in the format:
    http://<server_address>:3000/streams/<projectId>/branches/<modelName>.
    I would like to confirm if this is the correct format. Additionally, I am curious about the potential impact if the legacy pages are removed in the future.

  2. Regarding objects that cannot be represented as Geometry, I have reviewed the documentation (https://speckle.guide/user/dynamo.html#creating-custom-objects) and observed the expected behavior when custom objects are sent.

    example-data
    example-data833×695 50.8 KB

However, I am wondering if there is a way to transmit the actual Dynamo script itself (e.g., the programmed code in Dynamo) to Speckle.

  1. When data is sent, Speckle seems to automatically convert it as per the documentation (https://speckle.guide/user/dynamo.html#send-data). If the automatic conversion fails, does the data appear as null? Could you please confirm this behavior?

  2. Lastly, I would like to confirm whether the Dynamo Connector can be used with Dynamo Sandbox in addition to Dynamo for Revit.

Thank you in advance for your response. Have a great day! :slightly_smiling_face:

2

Hi @Yonggu ,

  1. the dynamo connector does not enforce any specific port, the URL used is they one you have set up during your account authorisation (via Manager or other means)
  2. sending the dynamo script is not possible by default, but you might hack a way to send it as text
  3. yes, I believe failed objects are sent as null
  4. yes it can, but you will need to build it from source as the installer does not support sandbox
3

Hello, thank you very much for your response to my previous question.
I have a follow-up question regarding question #1 that I previously asked, and I would appreciate your clarification.

deprecate-query.txt (265 Bytes)
active-query.txt (303 Bytes)
response_deprecate_api.json (3.2 KB)
response_active_api.json (2.2 KB)

If the legacy page were to be removed, I’m curious if this would impact the URL format in any way. Based on the queries and response data I’ve attached, I observed that using the following URL format seems to work. I’d like to know if there is any additional information or official guidance related to this.

URL: http://<server_address>:{port}/streams/<projectId>/branches/<modelName>

Thank you.

4

Hey @Yonggu

as a general rule, when you are using the graphql api, you should use the new nomenclature (projects, models, versions). For url-s of projects, we had to implement translations on both the connector and the webapp layer to keep supporting old style links in ie. existing dynamo / gh definitions or 3d viewer embed links.

So using both /streams/... and /projects/... is fine. Ofcourse if you are doing new stuff, you should be using the /project routes.

Hope this clarifies things for you.

2 Likes