LivelyKernel / LivelyKernel/lively.next
Snapshots must load!
@rickmcgeer is already working on this.
Since Apr 27, 2021.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
This is related to the issue I just filed. Since lively is an integrated system, when a world fails to load due to a bug there is no way for the ordinary user to recover it. The world-not-loading error is always due to a user error, typically a fatal bug in properties or initialization code. But at a minimum, the user needs a world with an editor so they can fix whatever the problem is. I don't know if a "Safe Mode" is the answer, or trapping errors so only the offending morphs won't load, but I do know this is one of those problems that makes people walk away for good when they hit it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.