Revision history for ProjectGoals
Additions:
The proof/success in having business people directly involved in webERP development now - who previously had little programming experience - adds credibility to the enormous value of this goal.
Additions:
|=|{{image alt="webERP logo" title="webERP Logo" url="images/webERPlogo.gif"}}|=|[[HomePage What Is webERP]] |=| [[WeberpFeatures webERP Features]] |=|[[WeberpFaq Documentation]]||
|=|[[WeberpSupport Support]] |=|[[http://www.weberp.org/forum Forum]] |=|{{image class="center" alt="Sourceforge Logo" title="Sourceforge Logo" url="http://sflogo.sourceforge.net/sflogo.php?group_id=70949&type=9" link="http://sourceforge.net/projects/web-erp"}} |=| [[http://sourceforge.net/project/platformdownload.php?group_id=70949&sel_platform=3757 Download]] |=| [[http://www.weberp.org/weberp/index.php Demo]] |=|[[WeberpDevelopment Development]]||
|=|[[WeberpSupport Support]] |=|[[http://www.weberp.org/forum Forum]] |=|{{image class="center" alt="Sourceforge Logo" title="Sourceforge Logo" url="http://sflogo.sourceforge.net/sflogo.php?group_id=70949&type=9" link="http://sourceforge.net/projects/web-erp"}} |=| [[http://sourceforge.net/project/platformdownload.php?group_id=70949&sel_platform=3757 Download]] |=| [[http://www.weberp.org/weberp/index.php Demo]] |=|[[WeberpDevelopment Development]]||
Deletions:
|=|[[WeberpSupport Support]] |=| [[http://sourceforge.net/projects/web-erp Sourceforge Project Page]] |=| [[http://sourceforge.net/project/platformdownload.php?group_id=70949&sel_platform=3757 Download]] |=| [[http://www.weberp.org/weberp/index.php Demo]] |=|[[WeberpDevelopment Development]]||
Additions:
This last goal/objective is contentious and not all agree with the CodingConventions that have been adopted and the rigour applied in ensuring code conforms to them. The ultimate aim is to make the code as simple as possible for a reader of the code and to minimise the learning curve of new developers in getting to grips with the scripts that make up webERP. New scripts created must adhere to the coding conventions and style. It is hoped that business people can look at webERP code and pick up the essentials of PHP necessary to give their business a real competitive advantage.
Deletions:
Additions:
This last goal/objective is contentious and not all agree with the coding conventions that have been adopted and the rigour applied in ensuring code conforms to them. The ultimate aim is to make the code as simple as possible for a reader of the code and to minimise the learning curve of new developers in getting to grips with the scripts that make up webERP. New scripts created must adhere to the coding conventions and style. It is hoped that business people can look at webERP code and pick up the essentials of PHP necessary to give their business a real competitive advantage.
Deletions:
Additions:
This last goal/objective is contentious and not all agree with the coding conventions that have been adopted and the rigour applied in ensuring code conforms to them. The ultimate aim is to make the code as simple as possible for a reader of the code and to minimise the learning curve of new developers in getting to grips with the scripts that make up webERP. New scripts created must adhere to the coding conventions and style.
Deletions:
No Differences
Additions:
This goal is contentious and not all agree with the coding conventions and the rigour applied in ensuring code conforms to them. The aim is to make the code as simple as possible for a reader of the code and to minimise the learning curve of new developers in getting to grips with the scripts that make up webERP.
Deletions:
~Well spaced and rigorously indented.
~Extensive commenting.
~Long descriptive variable names.
~There is also an interesting compromise between good programming practice in maximising code reuse through the use of includes, classes and common functions and in the number of separate scripts required to be understood before a developer has enough confidence to consider modifying the script. I believe that too many levels of abstraction can detract from ease of understanding the script. For this reason includes are used in preference to function calls where possible. Abstracting PHP functions to separate user-defined PHP functions is avoided. Use of OOP is restricted to those areas where large amounts of re-use are possible.