vikrum
commented
9 years ago Excellent! Glad to see it forked :D
As you've already noticed, the app is all client-side. However, there are two places that might be of interest; 1) where the keyboard 's' command saves the current canvas, and 2) the drag and drop to load in an image. Apart from that, there is currently no mechanism to communicate with a backend server or filesystem.
Save to file: https://github.com/ocdtrekkie/kiddopaint/blob/master/js/init/kiddopaint.js#L569
Image upload (drag and drop): https://github.com/ocdtrekkie/kiddopaint/blob/master/js/init/kiddopaint.js#L574
I hope that helps!
@vikrum Hey, I put this over here in a 'fork' since it's not really relevant to your main project, and I don't want to pollute.
So, your app currently doesn't implement any instances of documents or user handling or anything, which (actually) makes it easier to package into a Sandstorm app. (As Sandstorm handles nearly all matters of document management, user management, etc. for you.)
If you're interested in seeing how it works, I recommend checking out http://demo.sandstorm.io and trying to create some Etherpad documents. (Or EtherDraw, for some similarity. I packaged that to Sandstorm myself!)
The only thing I need to figure out how to make your app do in order to make everything work, is somehow store (and obviously, retrieve) the art from the /var directory on the local server. It only needs to handle a single file/document, so there's no need to make random filenames or anything. I was curious if you had any ideas how best to do that.