Sounds interesting! Are you referring to github’s versioning with commits, etc? The benefits really depend on the use case. And you can setup a git repository on S3.
Or are you referring to version control of the plugin source? Definitely a good idea, I’m doing that with git myself.
I’m building an image cropping element, which takes an image and allows the end user to crop it before uploading.
One feature I’d like it to be able to do is to load an image from one stored Bubble’s database. I can retrieve the image url from an image field, but I get a CORS error when the plugin tries to read the image data.
XMLHttpRequest cannot load https://s3.amazonaws.com/appforest_uf/f1487851009545x439826681511476600/image.png. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'https://my-test-app.bubbleapps.io' is therefore not allowed access.
Is there some access to the app that you can grant on the server side?
I’m curious… would this new capability allow for the adding of js or css libraries? For instance could we add/load like material design, bootstrap, or even some animation library to control the design of elements?
You can think of the element plugin as a HTML element with added functions for reading properties, exposing values and raising events. Bubble elements remain outside the container.
So for adding js / css, yes easily for any HTML added inside the element. But for altering Bubble elements, you’d have to do similar tricks of walking the DOM to find them, adding classes, and competing with Bubble’s responsive engine.
The answer: if you can do it in a HTML element, then you can do it in the plugin element.