Rework Widget javascript code to not use a global variable for entry point
Nobody has claimed this yet.
- Dominant language
- CoffeeScript
- Stars
- 65
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
Currently having two nlogo models compiled to the same page would break as things would get added improperly.
This will involve reworking how the widgets get compiled into javascript themselves, perhaps by some user defined connection between the compiled js and the code widget.coffee. Another option is having the entire session booted up from the compiled netlogo file (perhaps via workspace?) The goForever code that constantly monitors the widgets would either need to take care of all models loaded on page, or a separate goForever timeout would need to be created for each one.
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 tracing the widget.coffee compilation flow and the goForever code that monitors widgets, then inspect how the compiled NetLogo file or workspace boots a session. Compare the possible entry-point and per-model timeout approaches. Done means two nlogo models can load on the same page without their widgets interfering.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- coffeescript, javascript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100