Re: [WebERP-developers] FormDesigner.php

[icedlava <ice...@gm...>]

Hi Tim

On 14 Nov 2013, at 21:52, Tim Schofield wrote:

> Surely this is a strength not a weakness? It means that each company
> can have its own design and there is no need to be constantly changing
> the code depending on which company is being used?

I disagree on this point. For me it's truly time consuming especially if 
each client has different custom files for multiple forms (or other 
display pages). Now there is perhaps a minimum of 30 to 40 files i have 
to keep updated separately for a customer - minimum.  If any of those 
PHP files is updated in webERP, each has to be individually diffed 
against system file (to at least check and ensure correct changes with 
SVN) and changes applied. It also means i have to keep each client's 
weberp in separate custom branches to monitor the tracking and update of 
the main upstream repository of webERP.

Having separate branches in scm makes it easier, but the individual 
files is a time killer.

If this time can be reduced and we can provide easy, clean html/css 
files for display output that are override able in say a separate 
override folder outside of core webERP files, maintenance and upgrades 
becomes much easier. Even just having an override directory would be a 
huge saving.

@sotandeka - I agree with him that we could contribute templates for 
reports - once the method/format (or database form) is decided. That 
might be a nice touch for webERP - a user contributed template 
repository. It would be good if they could be drop in, in an override 
directory as mentioned above.

Anyway, just some ideas tossing around ...

Happy to go with what is decided .

Cheers,
Jo