Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Project roadmap
See original GitHub issueHello folks,
I know this is a project made after the 2 hours Daniel spent to make the QuadTree videos, but I think it could either benefit from either:
- Being renamed to
QuadTreeExample(because it’s definitely just a bunch of examples, at least for now 😄 ) - Split into smaller packages.
Just saying this because we have very common classes here (Point, Rectangle…) that could be used as simple geometry for any kind of project based on a canvas, and the QuadTree one that depends on the Geometry one.
Or then rename this project to Geometry and put everything in it in separate files 🤣 .
What do you think?
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m totally 👍 for adding an
object(orsubjectmaybe?) property toPoint! I was mostly arguing about the particle part, because IMO this “subject” should be an abstraction that can mix types, not a fixed one. Sounds totally legit to me, and it could be a recursive relationship: for example, a Particle is associated with a Point, and the Point “carries” the Particle as a “subject”. This allows using the Point class in any library 😄Maybe it is better to call the Point class different. Something like QuadTreeData or so. Then you know that it is not a “normal” point like @Pierstoval mentioned.