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
The CloudCompare software currently has a visual GUI and a command line interface for editing mesh and point cloud data. The CloudCompare CLI is very powerful at allowing users to batch process models and supports complex editing operations.
If CloudCompare added LuaJIT and Python scripting support to the CloudCompare GUI and CLI tools it would be possible to take mesh processing workflows further and fully pipeline automate complex multi-step tasks.
A scripting system would dramatically boost the tool's capabilities. A script could probe the current scene graph's state to determine the correct setting to use when performing computationally intense operations. A script that was running inside of CloudCompare would be able to edit the DB Tree, the model properties, do automated tasks like model opening, run "Edit" and "Tool" menu item features, perform file saving and closing operations, and support advanced workflow automation with branching and flow control logic.
CloudCompare currently has a Console tab in the GUI session. With the addition of a Script Editor window batch workflows would be supported and the results could be echoed to the Console view.
If there was a scripting layer in CloudCompare, the existing Toolbar system could be expanded to allow for user-created Toolbars that would let the user create their own custom tool buttons. Each custom Tool button would run user defined scripts/code chunks, support the entry of a tooltip caption, and the linking of an icon image for each button. This would be identical to Houdini Toolbars and Maya's Shelf system.
Additionally, inter-application communication would be possible in CloudCompare via the scripting layer if an RPC protocol was enabled in the integrated scripting system. Having an RPC capability would enable multiple systems running CloudCompare to work collaboratively on batch processing media in a queue and make it possible to have a CloudCompare "cluster" of batch render nodes all work together in an automated fashion to each grab a model and batch process it locally.
Also, when the CloudCompare CLI is started from a terminal session, you could define a remote system and that CLI task could be passed automatically to another node to compute the result.
The text was updated successfully, but these errors were encountered:
The CloudCompare software currently has a visual GUI and a command line interface for editing mesh and point cloud data. The CloudCompare CLI is very powerful at allowing users to batch process models and supports complex editing operations.
If CloudCompare added LuaJIT and Python scripting support to the CloudCompare GUI and CLI tools it would be possible to take mesh processing workflows further and fully pipeline automate complex multi-step tasks.
A scripting system would dramatically boost the tool's capabilities. A script could probe the current scene graph's state to determine the correct setting to use when performing computationally intense operations. A script that was running inside of CloudCompare would be able to edit the DB Tree, the model properties, do automated tasks like model opening, run "Edit" and "Tool" menu item features, perform file saving and closing operations, and support advanced workflow automation with branching and flow control logic.
CloudCompare currently has a
Console
tab in the GUI session. With the addition of aScript Editor
window batch workflows would be supported and the results could be echoed to the Console view.If there was a scripting layer in CloudCompare, the existing Toolbar system could be expanded to allow for user-created Toolbars that would let the user create their own custom tool buttons. Each custom Tool button would run user defined scripts/code chunks, support the entry of a tooltip caption, and the linking of an icon image for each button. This would be identical to Houdini Toolbars and Maya's Shelf system.
Additionally, inter-application communication would be possible in CloudCompare via the scripting layer if an RPC protocol was enabled in the integrated scripting system. Having an RPC capability would enable multiple systems running CloudCompare to work collaboratively on batch processing media in a queue and make it possible to have a CloudCompare "cluster" of batch render nodes all work together in an automated fashion to each grab a model and batch process it locally.
Also, when the CloudCompare CLI is started from a terminal session, you could define a remote system and that CLI task could be passed automatically to another node to compute the result.
The text was updated successfully, but these errors were encountered: