Feature request : Support for Scratch-style Actor-centric multithreading
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 611
- Forks
- 211
- PR merge metrics
- No merged PRs in 30d
Description
Originally reported by: **brice.copy@cern.ch (Bitbucket: [bcopy](https://bitbucket.org/bcopy), GitHub: [bcopy](https://github.com/bcopy))**
----------------------------------------
It would be very useful to agree on a naming convention that would allow Actor-centric execution threads, similar to what is being done in scratch.
Young users focus primarily on what happens to an actor, but can't handle the concept of multi-threading in the UPDATE() method - Adopting a naming convention would help a lot.
Other features that would help the transition from Scratch :
* Actor messaging (to exchange simple signals) and associated event handling
* Actor rotation, zooming, flipping (c.f. currently open issues #3 and #36 )
----------------------------------------
- Bitbucket: https://bitbucket.org/lordmauve/pgzero/issue/50
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
Start by reading how UPDATE() currently drives execution, then review the related open issues #3 and #36. The request combines actor-centric threads, messaging and event handling, plus actor transformations, so the scope and completion criteria need agreement before implementation can begin.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100