Re: [WebERP-developers] Replace addJpegFromFile() [from R&OS pdf.php] with Image() [from tcpdf.php].

[Rafael C. <raf...@gm...>]

Hi Bob,

Thank you for your comments.

About PDF forms modifications: I am trying to merge customisation inside
the main code as options. My goal is to reduce the re-customisation of the
upgrades. I'd be glad to know that kind of customisation you did to see how
to incorporate it to the master code.

About XML as another "dialect": I think it's best to have the report
customisation in the database. But as simple data, not XML, not json,
not... Pros: less "framework to be learned and mastered". Cons: We have to
re-write and migrate all reports.

About hierarchy for scripts: Nice idea! It remains me
GNU/Linux/Debian/Ubuntu/Mint/Gnome... each customisation in in the next
layer.

About the form designer: I was tempted to improve it, but that would
perpetuate the inherited problems that make very difficult to customise the
reports (no standard coordinates; unsuited for LTR/RTL languages changes,
etc.). It is better to make a new one.

About PrintCustTransPortrait.php and others: We also modified that script
(all customers ask for it). It is a nightmare when we have updates of that
scripts.

Best regards, Rafael.

2016-10-06 6:57 GMT-06:00 rfthomas <rf...@as...>:

> 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.
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers
>