fireclawthefox / fireclawthefox/SceneEditor
Enhance editor performance
- Dominant language
- Python
- Stars
- 22
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Larger scenes suffer from the many text elements in the tree graphs and property editor. The scenes itself are good as soon as all the labels have been loaded.
Some ideas:
Load only visible labels and some that may be visible soon (lazy loading)
Pack labels in the scene graph into one node and flatten them, make sure buttons and other clickable elements won't be affected or labels misplaced.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files or tests are named. Start by profiling large scenes in the tree graphs and property editor, focusing on the many text labels and their loading cost. Done means large scenes load or remain responsive while labels stay correctly positioned and buttons and other clickable elements continue to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100