Tickets :: Comment on [#3700] Proforma

* Your Email Address
* Spam protection	Enter the letters below: .__.. .. ..___.. \| \|\| \|\ / \| \| \|__\|\|__\| \/ \| \|___
Comment	> Great work!!! > > > > Some comments (Please don't take them too serious if I'm totally wrong on > > some points. I installed proforma yesterday evening and just played around a > > little bit - but I didn't dig deep enough to be sure about what I'm writing): > > > > - using AJAX for tax calculation while updating fields seems a useless over- > > head - it should be worth the effort to write some client-side > JavaScript to do > > this job. While finally saving an invoice I wouldn't trust these > values and do > > the same calculation once again on server side. > > > > This may be seen as a duplication of code (same thing in PHP and JS) - > > but it saves us a lot of HTTP traffic. Especially if you're going > to use HTTPS > > this shouldn't be underestimated. > > > > - show tax sums only for taxes used in the current invoice (there are > countries > > with 5 and more tax variants - and only one of them is used in probably 99% > > of all invoices) > > > > - what will the SQL layout look like? I would suggest something like: > > > > * invoices: containing customer details (address... - it's important to > > duplicate them and not to save just an ID), billing date, ctime, mtime, > > document type (offer, invoice, proforma invoice...), state (sent, payed) > > > > * invoice details: invoice id, amount, price, tax, currency > > > > I'm in a hurry right now - but maybe this weekend I can find some time to > > go on playing with "proforma" ;-) > > > > Kind regards, > > Thomas Gelf > > > > NB: Please keep this ticket up to date!
Attachment
Watch this ticket

Saved Queries