Hi @wojtek, @tomek and @jan.
I want to talk to you from my point of view as a shapespark user without programming knowledge.
I consider myself a curious person and I know that many things can be done interacting with Shapespark through the html and the API, however due to my ignorance I don’t understand the limitations and the scope of these tools. I see some wonderful results and I would like to offer them to my clients but I just don’t know how to implement them.
Even this topic is so foreign to me that I don’t even know how to ask my questions because it is simply not clear to me what I can and cannot do using html and the API.
So I propose you something
Please make a list of the interactions and tricks that can be achieved programmatically and indicate which ones can be done with the scrip extension, with the API and with HTML files.
Then, try to make the implementation of those tools friendly for people like me who have no idea about programming. Even the script extension is a mystery to me. You need a very ease front-end, a fool-proof interface!
I leave you these concerns and I hope to collaborate with the development of this platform.
If you would like to try something I am always willing to collaborate.
There isn’t really much difference between body-end.html based customizations and the Script extension. Script extension allows to add code directly from the editor, so it can be more convenient for small customizations, but body-end.html allows to use your preferred HTML editor, so for any larger customization body-end.html will be more manageable.
From Shapespark API point of view, the interactions look to be simple. The page uses API calls to detect when the scene is loaded, when a node is clicked and to switch camera to a particular view. But HTML UI is really sophisticated (this isn’t really Shapespark related, as Shapespark doesn’t expose any functions for building such a UI)
others that I do not know how to achieve are for example 3D scene
specifically how to generate these buttons