Hey thanks for your interest,
sorry about the differing license in source code, I just forgot to remove it, that will happen in the next update. The choosing of the Artistic/GPL license is intentional, you can find out more about it on http://en.wikipedia.org/wiki/Artistic_License
as a starting point. I have to add a little correction to tmikaelds comment. Even if you provide GPL driven software as a service, you will have to provide a link where the the source code is accessable. If you use GPL software as essential part of your software, the software must be licensed as GPL to. Depending on your business model, this may or may not work for you
The Artistic license nevertheless allows us to offer you a custom licensing as well. For example something like you are allowed to use the software for free and without the need to put it under open source, as long as we are still mentioned as the creators of this specific part of the software at some appropriate place and as long as you send back improvements to the original project.
For me it is perfectly well If you are going to use my wrapper and even earn money with it, because it is confirmation of doing something useful and some advertisement as long as it is give and take. This is what the license enforces.
To answer your question about documentation I have to disappoint you by now. We have several current projects and at the moment and we are not yet connecting them to e-conomic, but that will certainly happen this year. So by now I will push recent changes to the repository whenever there is something new and I have the time for it but I am definitely not able to provide documentation right now. Nevertheless I will write some more unit tests. These should give you a good hint how to use the wrapper. At least I hope that it will be quite simple to use because most of the classes behave in a VERY similar way and only the attributes differ.
Best regards and have a nice weekend,