LivelyKernel / LivelyKernel/lively4-chrome-loader
Replay changes made by lively tools (idea)
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
This will require a different approach to persisting an applying changes,
but and interesting question would be how to make the changes to imgur in the demo would be made persistent.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no file, test, or entry point, so first inspect how lively4 is loaded into websites and how changes to the imgur demo are currently applied. Define the persistence and replay approach before implementation; done means changes made by lively tools to the demo can be persisted and replayed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100