Nikos M. - 2022-08-20 08:21:19 - In reply to message 1 from Cleriic
Hello, I am the author of this package.
Most of it is structured like this on purpose (eg simplicity, minimum file loads/requests, backwards-compatibility, so on..) because I use these on some legacy systems.
So "bad OOP" is really about personal preferences of code layout (there are no fundamental OOP principles violated in this code), one can always refactor the code if it is useful to satisfy one's own preferences.
But I would be glad to correct any mistakes there can be or bad documentation.