António Sarmento

@koistya Generally, it's used to add library headers to conveniently give less build hassles. [Here's an example](https://github.com/cinder/Cinder/tree/master/include). I'm solely suggesting, since this has its own drawbacks.

It's relevant to any kind of project. Of course, it mostly works with C/C++.

Note to add for macOS support: The code contains plenty of Carbon function calls. Since there are no direct translations for these to Cocoa (or Metal if we're going even...

That didn't show up when I searched. I'm sorry, I should've tried different keywords.

Do you mean using the `draw_*` functions from `CanvasItem`? If so, if borders are to optionally have collision in them (as per #42), this is not a good idea.

Ah yes, my mistake. The polygon data is not lost in the process, so it can be applied to a CollisionPolygon2D.

Is it possible to add a simple, untextured border of a given color? If not, then that would be a great feature!

I've been trying to do it by myself for the past 2 days before I found your plugin. I think I'm close to a solution, but we'll see!

Will do! Another suggestion: overloading functions like `update()` is terrible practice. You should use `_draw()` instead (`update()` makes the necessary function calls, including `_draw()`). I'll push any changes where I...

I am, and I will! Give me some time while I work with your code and get to know it better :)