microsoft / microsoft/pxt-microbit

Content that does not work in Windows offline use of Electron app

Open
#3,238 2 comments 0 reactions 1 assignee View on GitHub

@jwunderl is already working on this.

Since Jun 24, 2020.

offline P2
Dominant language
TypeScript
Stars
804
Forks
721
Avg merge
2d 9h
Merged PRs (30d)
2

Description

There is a lot of content that either does not work offline or points to documentation which has embedded videos that require internet connectivity.

This list is not exhaustive:
Nothing (perhaps unsurprisingly) in the Live Coding section works.
In Games section, Reaction Time brings user to local copy of webpage with video that cannot be displayed without internet connection, same with Magic Button Trick, same with Salute. The documentation for these seems thorough enough that a user would still be able to complete the project.
Nothing in the Turtle section works without internet. See screenshots below after clicking on the Scanner project.
Some content in the Science section also heavily relies on videos for instruction - see screenshot below which is from the Plant Watering project.
In the Music section, the Guitar project leads to documentation with many embedded videos for instruction, which does not seem usable at all without internet.

Expected behavior
It should be more obvious to the user what content requires internet connectivity or is optimal with internet connectivity. If a tutorial (like the Scanner project) is unavailable without internet, it should not create a project in the workspace.

Screenshots
Add screenshots to help explain your problem. You can copy paste the screenshot in the github report. The .gif screen recording is very useful as well.
image
image
image

Desktop (please complete the following information):
Windows Offline - Electron App

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.