I can’t blame you for expecting that every existing Rhino and Grasshopper feature will work out of the box on ShapeDiver. Not that it’s not unrealistic - it bloody well is - but it is in fact a beautiful vision, for a somewhat distant future. However, we are in the field of cloud technologies, and don’t yet dabble in sorcery, except for some unsatisfactory experiments.
That being said, I truly apologize for invoking the API so much when I answer your questions. We are doing our best to make ShapeDiver a designer-first tool. It’s the vision, after all: we want to give Grasshopper designers the ability to create complex web applications, without the help of a skilled developer. Therefore, we iterate along those lines:
- Identify a feature needed by our users
- Upgrade the online viewer and its API so that the feature can be tested and become available to developers
- Connect the viewer feature with additional Grasshopper components or rules so that designers can access it as well
In the present case, I agree it makes complete sense to have a “Point Grip” tool in the ShapeDiver plugin, which would create a draggable element in the online viewer acting as an input to the definition. As a matter of fact, this is a need we already identified and built in the online viewer (steps 1 and 2). We only miss step 3). I will make sure to let you know when it happens.
Please scroll down the tutorial page to the section called “Full code of the tutorial”, and click on the third tab in the embedded fiddle, called “Result”. There you can play with the example.