Confirmed users
764
edits
(Status update) |
(→Background: s/[FlightDeck] will be available as a Web service or maybe an extension/[FlightDeck] will be available as a Web app/) |
||
Line 15: | Line 15: | ||
* The SDK has a security model, the Prototype didn't. | * The SDK has a security model, the Prototype didn't. | ||
* Roughly speaking, there are two layers of APIs under the SDK. There's a low-level, chrome-privileged layer that wraps the platform. And there's a high-level, secure, low surface area, and friendly layer that builds on the lower. It's the higher layer that might be thought of as "the Jetpack API," but it's entirely possible to use the lower to build an extension. | * Roughly speaking, there are two layers of APIs under the SDK. There's a low-level, chrome-privileged layer that wraps the platform. And there's a high-level, secure, low surface area, and friendly layer that builds on the lower. It's the higher layer that might be thought of as "the Jetpack API," but it's entirely possible to use the lower to build an extension. | ||
* The Bespin IDE of the Prototype will be replaced with a contracted-out in-browser IDE called "[[Labs/Jetpack/FlightDeck|FlightDeck]]." (Maybe you've heard of it?) FlightDeck provides a nice UI to the SDK's toolchain. It will be available as a Web | * The Bespin IDE of the Prototype will be replaced with a contracted-out in-browser IDE called "[[Labs/Jetpack/FlightDeck|FlightDeck]]." (Maybe you've heard of it?) FlightDeck provides a nice UI to the SDK's toolchain. It will be available as a Web app. | ||
== Current Status == | == Current Status == |