search

scratchfoundation / scratch-www

Standalone web client for Scratch
https://scratch.mit.edu
BSD 3-Clause "New" or "Revised" License
1.58k stars 835 forks source link

ability to "load" new 3.0 project #2019

Closed benjiwheeler closed 6 years ago

benjiwheeler commented 6 years ago

user should be able to do File -> New to load a new default 3.0 project in the editor, which replaces the current project data.

towerofnix commented 6 years ago

Oh, btw.. what's the LLK/scratch-projects repository? Are there any plans to open source that, or to document the API used to interact with it?

colbygk commented 6 years ago

The scratch-projects repository and software is our interface for storing project files to our backend storage system. We have no current plans for open sourcing this and I think it's unlikely we will make any documentation updates before or immediately after the Scratch 3.0 release in January 2019.

wwj718 commented 6 years ago

hi @colbygk, I noticed that the existing project homepage is based on Django

image

I want to know if the new backend of scratch3.0 is also based on django.

Thanks!

colbygk commented 6 years ago

Hello there, the simple answer is that no, Scratch 3.0 is not based on django. The more complex answer is that we're currently in the process of shifting a lot of backend infrastructure away from being handled by django, and some of this infrastructure ends up handing data back into requests made by the Scratch 3.0 frontend. This includes parts like the individual project pages, which we are currently updating.

wwj718 commented 6 years ago

@colbygk thanks for your reply!

wwj718 commented 6 years ago

@colbygk I guess the new backend only provides REST api, Business logic is at the front end. I would like to know if you will use django-rest-framework or Rails to provides the REST api，Or you will use Serverless Framework

Thanks!

benjiwheeler commented 6 years ago

We are currently building the REST API in node, with a server (not sure what the opposite of "serverless" is :)

As @colbygk said, the plan is to launch 3.0 using both the node and django servers providing API endpoints, andover time to shift backend business logic over from the django server to the node server.

wwj718 commented 6 years ago

@benjiwheeler Thanks!

benjiwheeler commented 6 years ago

Should we create a new project on the server for every user, including ones who are not logged in? Or should we wait until a user is logged in to create it? My understanding is that we do the latter for 2.0.

colbygk commented 6 years ago

I believe that we should wait until login and keep the same behavior as 2.0. This seems like something reasonable to raise at the next project page huddle.

benjiwheeler commented 6 years ago

Moved to LLK/scratch-gui#2954