jMonkeyEngine / jMonkeyEngine/sdk
Replace usage of LegacyApplication
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 348
- Forks
- 104
- Avg merge
- 4d 13h
- Merged PRs (30d)
- 3
Description
So the SDK makes heavy use of the assetManager field where it could use Application.getAssetManager().
It might also extend Application instead of SimpleApplication (now LegacyApplication).
The question is if we should implement Application or extend LegacyApplication? I'd say we can go for the latter and worry about those things later.
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 locating the SDK code that extends or uses LegacyApplication and accesses the assetManager field. Review the Application and LegacyApplication APIs to compare implementing Application with extending LegacyApplication. Done means choosing and applying one approach consistently, with the existing SDK behavior preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- devtools
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100