You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Bldrs supports two data sources for IFC models:
Local file
GitHub
The first data source supports reading data. The second data source supports reading data and (?) may support writing data in the future.
In addition there should be support for HTTPS as a data source to support use cases where IFC models are stored as a resource in the cloud and are available through an HTTPS URL. For example, a user in vyzn may sign-up with an account type other than GitHub (google workspace account, e-mail, ..) and may choose not to authorize any GitHub OAuth integrations. In this case the system needs to provide means to show 3D content even if GitHub is unavailable.
The existing Bldrs URL structure as documented here should be extended to support the "src" parameter:
Currently Bldrs supports two data sources for IFC models:
The first data source supports reading data. The second data source supports reading data and (?) may support writing data in the future.
In addition there should be support for HTTPS as a data source to support use cases where IFC models are stored as a resource in the cloud and are available through an HTTPS URL. For example, a user in vyzn may sign-up with an account type other than GitHub (google workspace account, e-mail, ..) and may choose not to authorize any GitHub OAuth integrations. In this case the system needs to provide means to show 3D content even if GitHub is unavailable.
The existing Bldrs URL structure as documented here should be extended to support the "src" parameter:
This would load the file from https://example.org/blobs/myfile.ifc?x=1&y=2
The text was updated successfully, but these errors were encountered: