While using Speckle on some of our engineering/software dev projects, I observe an increased need for users to be able to edit stream object properties outside of the source application.
Abstractly, I see this need occur when:
- A user wants to send a model from application A (alien software) and receive in application B (his/her software), but to be able to receive a valid model, some of the object properties are missing due to lacking API or knowledge of application A.
- User A creates a stream in his software (modeller/junior), user B (project manager or senior designer) wants to quickly review/edit/fix object properties to enable further downstream processes.
Right now, you can edit object properties using the Excel connector, but it doesn’t support merging this new data with a specific branch/commit again to create a new merged commit.
Ideally, this type editing can be done inside the web app, as a feature inside the stream page (ppt extravaganza):
User only needs to select branch, commit & Speckle type, for the table editor to appear.
When finished editing one or multiple speckle types, a new commit can be generated with the changes. Geometry based properties should probably be filtered out.
If having a stream type editor in the web app is undesired, the described feature could also be added in the Excel connector. In addition to the
filter and receive command, a new selection command can be added that allows users to select by speckle type (e.g.
Select by Speckle type):
For every selection, a new excel worksheet is generated with the name of the speckle type.
Selecting by Speckle type from a list like this has the advantage that you can edit all instances of a type at the same time, even if they are nested.
In addition to this new receive method, the sender should have an option to merge the sheets with an existing branch/commit again.
Curious to hear what you foaks think? Has something like this been discussed before? We’re happy to contribute here!