Import Image UI (allows for importing via URLs and by local image file

[ChronoAndross]

The code changes that are made here are as follows:

1. I added a new file named ImportModal.js.
2. I added a new main method called loadImageFile, which essentially parses the entirety of the current shader and adds the appropriate path next to the new texture name. I call setUniforms for local files since the image comes in as a data64 string.
3. Added an instance of ImportModal class to the Menu class using a similar pattern used for the ExportModal class.

NOTE: This does not capture CORS requests if they occur in these instances. I was going to attempt to try this, but the response for CORS happens to far in the call stack to catch it. Perhaps I'll work on this at some other point.

For more information about the behavior of this new feature, please look at my latest comment in this issue: #29

Thanks!

[patriciogonzalezvivo]

thanks for the patience @ChronoAndross. Although loadImageFile using base64 it's a great idea to keep shaders compact and independent, it relays on the space on my server which I pay only with donations. That's a pattern that I don't wish to promote. Do you mind taking out that feature?

[ChronoAndross]

@patriciogonzalezvivo I can take out that feature and just accept paste the local file path and submit that today.

Thanks for getting back to me!

[ChronoAndross]

Actually, now I'm looking back at my code, I know why I did it this way to begin with. I did it this way since the input tag won't give me a full local file path by default because of security reasons, and I don't think I can get around this. Should I just disable the feature, or should I just change the UI so that the user gets the same dialog when importing a URL image?

Thanks!

[ChronoAndross]

Okay so I've changed my code to just paste the local path, but local imports don't presently work since the Texture.js code keeps rejecting local URIs. I can't directly change this code. @patriciogonzalezvivo is this something you can do? I'm betting it has something to do with loading the local image data. This is why I loaded the data using base64 since a base64 stream can be read locally fairly easily.

Thanks!

[patriciogonzalezvivo]

Yes using URL to the cloud (checking previously that don't raise CORS issues) should be the only way to import an image. Why?

• local files wont work for other users
• base64 encoded images, promote "sharing" the image in the shader and that drastically increment the size of the shader... and that potentially will collapse the server and/or make me pay extra $$$... which I'm not willing to do.

For then, remotes URL with no CORS issues should be the only available option. People need to host their own images using dropbox or another services