From: rfthomas <rf...@as...> - 2016-10-06 13:04:19
|
We do modify a few of the PDF forms (as well as several other scripts - we should get some incorporated into the main trunk as they are of general use) and for each release we need to back in our changes. For the past several releases (only with respect to PDF) there have been no changes in the information passed and the major libraries (includes), so we are able to just copy the modified scripts. PDF generation is generally very fast using the existing software. We find that the database code is where the major overhead resides. Adding XML is forcing another "dialect" to be learned and mastered in order to make changes. As we understand it, xml is just a framework that code must interpret, in the case of weberp such would be done utilizing php code. We would prefer an execution search hierarchy for scripts, where users would place customized code into customer directories. We recognize that there is a performance penalty for such. It would also require that changes that involve database, session, get, or post data incompatibility be documented. We do agree that the report writer and forms are difficult to use and that the results are not always as expected. The form designer is missing several forms, e.g. Quotation, Packing Slip, and Credit Notes. We have not researched the form code. Is the Sales Invoice form data, i.e. Customer Invoice, actually used in the code? We have modified the scripts to enable printing customer invoices, credit notes and packing slips from PrintCustTransPortrait.php. Bob Thomas -- View this message in context: http://weberp-accounting.1478800.n4.nabble.com/Replace-addJpegFromFile-from-R-OS-pdf-php-with-Image-from-tcpdf-php-tp4658687p4658698.html Sent from the web-ERP-developers mailing list archive at Nabble.com. |