4 ms·
I discovered LÖVE sometime around this february. We have a Game-making group at university, so I wanted to show them too. All went well until we looked at the l
by rg0ne 15y ago
I discovered LÖVE sometime around this february. We have a Game-making group at university, so I wanted to show them too. All went well until we looked at the libraries :/
- therockhead 15y agoWhat was wrong with them?
- 286c8cb04bda 15y agoNot the parent, but -- in my experience -- many libraries from the community were written by enthusiastic amateur developers. Finding ones I enjoyed using was very needle-in-a-haystack. One recommendation: https://github.com/kikito https://github.com/kikito
- dannytatom 15y agoAlong with that, a lot of the libraries (from what I could tell) put all the code in one massive file in a forum thread and update it from there, making it pretty time-consuming to keep up with changes. That and there's no consistency between libraries as far as how they decide to use classes.
- anonymoushn 15y agoThat and there's no consistency between libraries as far as how they decide to use classes. This problem actually became so severe that there is now a "common interface" that libraries can use on each other's objects.
- anonymoushn 15y agoMy solution to this was to not use any of them. The LÖVE APIs are pretty sane, so using your own tiny wrappers is not much work compared to dealing with the libraries.
- rg0ne 15y agofirst the names struck me(dirty mind). aside from that, the libraries that caught my attention were far from complete :/ (lure, it is)