Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing - Create iOS wrapper for playground #32

Closed
thisandagain opened this issue Feb 2, 2016 · 3 comments
Closed

Testing - Create iOS wrapper for playground #32

thisandagain opened this issue Feb 2, 2016 · 3 comments

Comments

@thisandagain
Copy link
Contributor

For local development and prototyping (as well as design reviews around the lab) we should implement and lightweight iOS wrapper application around playground.html.

@thisandagain
Copy link
Contributor Author

@tmickel Could you take this? I figure the basic WKWebView structure from the Shakespeare prototype could be a good fit.

@tmickel
Copy link
Contributor

tmickel commented Feb 8, 2016

@thisandagain Sure, I can do this.
With Shakespeare/ScratchJr it was helpful to have a version that could be configured to point to a dev server, in the app settings - or to build a version with everything bundled. I'm assuming we'd like the same?

I was assuming we're going to rebase scratch-blockly to blocklypp at some point. Let me know if you have thoughts about where this wrapper should live, otherwise I'll just throw it in here in /wrapper or something.

@RoboErikG
Copy link
Contributor

Just an FYI, we're splitting out the iOS and Android pieces into their own
projects. Any changes to the web are going directly into the public Blockly
repo, though, so you won't need to switch for anything using the web
version.

On Mon, Feb 8, 2016 at 12:47 PM, Tim Mickel notifications@github.com
wrote:

@thisandagain https://github.com/thisandagain Sure, I can do this.
With Shakespeare/ScratchJr it was helpful to have a version that could be
configured to point to a dev server, in the app settings - or to build a
version with everything bundled. I'm assuming we'd like the same?

I was assuming we're going to rebase scratch-blockly to blocklypp at some
point. Let me know if you have thoughts about where this wrapper should
live, otherwise I'll just throw it in here in /wrapper or something.


Reply to this email directly or view it on GitHub
#32 (comment).

Erik Pasternak | Master of the House | epastern@google.com

rschamp added a commit that referenced this issue Feb 18, 2016
@tmickel tmickel closed this as completed Feb 19, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants