{"action":"created","issue":{"url":"https://api.github.com/repos/jeffeb3/sandify/issues/15","repository_url":"https://api.github.com/repos/jeffeb3/sandify","labels_url":"https://api.github.com/repos/jeffeb3/sandify/issues/15/labels{/name}","comments_url":"https://api.github.com/repos/jeffeb3/sandify/issues/15/comments","events_url":"https://api.github.com/repos/jeffeb3/sandify/issues/15/events","html_url":"https://github.com/jeffeb3/sandify/issues/15","id":240660118,"number":15,"title":"Integrate Turtle","user":{"login":"jeffeb3","id":1812882,"avatar_url":"https://avatars7.githubusercontent.com/u/1812882?v=4","gravatar_id":"","url":"https://api.github.com/users/jeffeb3","html_url":"https://github.com/jeffeb3","followers_url":"https://api.github.com/users/jeffeb3/followers","following_url":"https://api.github.com/users/jeffeb3/following{/other_user}","gists_url":"https://api.github.com/users/jeffeb3/gists{/gist_id}","starred_url":"https://api.github.com/users/jeffeb3/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jeffeb3/subscriptions","organizations_url":"https://api.github.com/users/jeffeb3/orgs","repos_url":"https://api.github.com/users/jeffeb3/repos","events_url":"https://api.github.com/users/jeffeb3/events{/privacy}","received_events_url":"https://api.github.com/users/jeffeb3/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2017-07-05T13:59:15Z","updated_at":"2017-07-15T10:29:05Z","closed_at":null,"body":"We need to merge turtle into sandify. How do we do that?\r\n\r\n1) Make turtle another input mode, similar to the Transforms.js. We could bring back the ace.js editor, and the command line and remove all references to the canvas from turtle, but make the output an array of vertices. \r\n -The design you have won't look the same because there's no way to lift the pen with an array of vertices. We could add a member to the Vertices to indicate a move vertex.\r\n\r\n2) Make turtle handle the canvas, and have it use an array of vertices as input.\r\n - This promotes turtle too much. The benefit of turtle is it's interface with the user, making it our backend seems like it's going to be crippling.\r\n - Other input modes, by other people would fit in parallel to Transform.js and Turtle.js. So making turtle different doesn't make sense to me. "},"comment":{"url":"https://api.github.com/repos/jeffeb3/sandify/issues/comments/315525322","html_url":"https://github.com/jeffeb3/sandify/issues/15#issuecomment-315525322","issue_url":"https://api.github.com/repos/jeffeb3/sandify/issues/15","id":315525322,"user":{"login":"jamesd256","id":17936291,"avatar_url":"https://avatars5.githubusercontent.com/u/17936291?v=4","gravatar_id":"","url":"https://api.github.com/users/jamesd256","html_url":"https://github.com/jamesd256","followers_url":"https://api.github.com/users/jamesd256/followers","following_url":"https://api.github.com/users/jamesd256/following{/other_user}","gists_url":"https://api.github.com/users/jamesd256/gists{/gist_id}","starred_url":"https://api.github.com/users/jamesd256/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jamesd256/subscriptions","organizations_url":"https://api.github.com/users/jamesd256/orgs","repos_url":"https://api.github.com/users/jamesd256/repos","events_url":"https://api.github.com/users/jamesd256/events{/privacy}","received_events_url":"https://api.github.com/users/jamesd256/received_events","type":"User","site_admin":false},"created_at":"2017-07-15T10:29:05Z","updated_at":"2017-07-15T10:29:05Z","body":"Thanks - good effort again.\r\n\r\nI will not put any authentication in unless it's 100% industry standard.  I am moving away from RdbHost, which looks fine, but it's just not something I'm used to.  I've found that Heroku do full node.js hosting with a free database, within limits.  I think I'd like to pursue this approach as things stand.  \r\n\r\nThe ideal would be federated logins available (google+, fb, twitter, etc.)  with a fallback to storing and encrypted password in a standard way, with the best of breed NPM modules.\r\n\r\nThere is a question about how the interface would work, but I would think the tabs will stay at least.  I would like to work on loggin in and storing / retrieving / sharing patterns first, with some presets available for each input.  Following that I guess me or you could look again at the input sequencing.  If you get there first, that would be awesome too.\r\n\r\nJust for fun I deployed to GH pages with a TLD:  www.sandify.tk.\r\n\r\nIt's a free domain.  Once I\"m back to the workstation I'll pull the latest gh-pages from jeffe3b to that page.\r\n\r\nThat will move to Heroku soon."}}
{"actor":{"display_login":"jamesd256"}}