Re: [WebERP-developers] FormDesigner.php

[Tim S. <tim...@gm...>]

Hi Jo, we seem to be saying the same thing here. By using the form
designer you don't have to change any PHP files, and updating to new
scripts is easy. It is only the xml files that change. So instead of
maintaining separate PHP scripts for each client as Phil is suggesting
above, you just create a new xml file for each client. As I said in my
email earlier if someone can find a way of simply getting the data
into the database without creating lots of complex tables that would
be great, and then you wouldn't even need to maintain the xml files.

Thanks
Tim

On 14 November 2013 12:15, icedlava <ice...@gm...> wrote:
> 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
>
> ------------------------------------------------------------------------------
> DreamFactory - Open Source REST & JSON Services for HTML5 & Native Apps
> OAuth, Users, Roles, SQL, NoSQL, BLOB Storage and External API Access
> Free app hosting. Or install the open source package on any LAMP server.
> Sign up and see examples for AngularJS, jQuery, Sencha Touch and Native!
> http://pubads.g.doubleclick.net/gampad/clk?id=63469471&iu=/4140/ostg.clktrk
> _______________________________________________
> Web-erp-developers mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/web-erp-developers



-- 
Course View Towers,
Plot 21 Yusuf Lule Road,
Kampala
T   +256 (0) 312 314 418
M +256 (0) 752 963 325
www.weberpafrica.com
Twitter: @TimSchofield2
Blog: http://weberpafrica.blogspot.co.uk/