unfortunately I do not have the programming skills to do it alone.
thanks to the work that I do, in the field of management software precisely, I have experience with respect to how it works, the necessary items, headings and db tables that could be used, but are not able to implement them in invoiceplane.
being the base of this project very valid implement the various types of documents used in various fields would make it one of the best.
I could still help by creating, knowing tables and items to be used in advance of the report that I would use it myself and then share them with the community
As was said it’s very nice piece of code.
Thanks a lot for this work.
My project where I’ll plan to use InvoicePlane for invoices probably will be release
similar to IP in fall 2015 in Alpha state.
I’ll add some not trivial features to code like separate admin-user logins (to see
their own invoices only), translations to polish, better PDF generation, etc …
And will be developing & maintaining in the future.
My situation is maybe similar to @simxware but I’m freelancer - know CI and Laravel.
So @kovah do you suggest use a V1 code (CodeIgniter) or better V2 (Laravel) now?
So this is it 1.4 has been released so that means V2 is just around the corner. Quite exciting to see this kind of speedy development. Well done and I’m looking forward to future versions. Have a great day!
Wait, didn’t i read wrong? When someone else develops some changes there can be several later iterations of v1? I mean looking at the developer road it states that 1.4.1 is planned in 2 weeks, 1.5.0 should come with a completed tasks function e.t.c.?
Just wanted to let you know: I got 1.4 running on IIS w/ SqlServer. Had to jump through some hoops, but it can be done and I’m actually using it right now.
I understand that this is not a high priority prerequisite, but you might bear in mind that some constructs will obstruct this possibility, like literal dbqueries. I saw you moved from CodeIgniter to Laravel, which also facilitates sqlsrv.