LivelyKernel / LivelyKernel/lively.next
stepping in the Component/ViewModel architecture
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 90
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
What would you like to achieve?
Lively Morphic had a very nice overlay on the native JavaScript timing functions -- stepping. In order to run a script on a Morph every n milliseconds, the call was simple: morph.startStepping(<scriptName>, <time in milliseconds) (the order may be wrong, I'm doing this from memory.). morph.stopStepping() stopped the stepping (of all stepping scripts).
It could have been improved (basically, UI/methods to view and control individual stepping scripts) but it was a huge improvement over the native JS calls.
The problem is that it was tied to Morph, and, in a Component/ViewModel architecture it's not clear if this is available or how to use it. So guidance is appreciated.
How are you trying to achieve that
I assume the simplest way to do this is just to attach the stepping methods to ViewModel
Alternative solutions
If applicable, what other solutions have you tried?
Additional Resources
Please provide links to any custom code that might be necessary to grasp your problem. Screenshots of custom component, etc. are also appreciated.
Version: Please paste the lively.next commit on which the problem occurred here (use the copy button of the Version Checker in the bottom left corner).
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.
Research direction
Start by locating the existing Morph stepping entry points, morph.startStepping and morph.stopStepping, and compare them with the Component/ViewModel architecture. Determine whether stepping should be exposed through ViewModel or another API, then document the chosen behavior and how individual stepping scripts are controlled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100