Allow exporting of the current state to a URL. The files would be hosted on aws s3, and be given a hash.
Then, going to studio.dumbcode.net/view/<hash> would allow anyone to view the model/texture/animation.
Going to studio.dumbcode.net/view/<userid> would allow anyone to view the exported projects for the user . If authenticated and viewing own projects, it would also allow deleting the projects, and changing the description/title/url of the exported project.
Going to studio.dumbcode.net/view/<userid>/<hash> would allow anyone to view the exported project, and have it render.
When exporting to the URL, the user can select (via a dropdown box), the Model, the Textures, and the animations.
The easiest way to do this honestly, is to generate a new .dcproj from the selected items, save it to a buffer, and upload the buffer to aws.
The saved location would be /dcexports/<userid>/<hash>.dcproj in s3.
For every user, there is a /dcexports/<userid>/posts.json that stores the title/description for every post (this would come eventually)
Allow exporting of the current state to a URL. The files would be hosted on aws s3, and be given a hash.
Then, going tostudio.dumbcode.net/view/<hash>would allow anyone to view the model/texture/animation.studio.dumbcode.net/view/<userid>would allow anyone to view the exported projects for the userstudio.dumbcode.net/view/<userid>/<hash>would allow anyone to view the exported project, and have it render.When exporting to the URL, the user can select (via a dropdown box), the Model, the Textures, and the animations.
The easiest way to do this honestly, is to generate a new .dcproj from the selected items, save it to a buffer, and upload the buffer to aws.
The saved location would be
/dcexports/<userid>/<hash>.dcprojin s3. For every user, there is a/dcexports/<userid>/posts.jsonthat stores the title/description for every post (this would come eventually)