Wiki source for ProjectGoals
|=|{{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]]||
----
=====Contributing to webERP=====
====GOALS of webERP====
~1. To provide **fast, web-based, integrated "best practise" business administration software**.
~2. To be **"low footprint"** efficient and fast, with absolutely minimal network traffic.
~This is to enable dial up/low band-width connections to work with reasonable response times. This will require some compromises with the use of graphics.
~3. **Platform independence**.
~Originally the use of Javascript was avoided due to the inconsistencies between implimentations. However, subject to certain rules javascript can be used.
~~1. Any use of javascript must have another server based option as a fallback - so client machines without javascript enabled will still function.
~~2. No significant blocks of javascript to choke dialup connections (see goal 2).
~~3. The javascript used should be used consistently throughout the code.
~4. Scripts **easily readable and modifiable by a business**.
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.
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.
|=|[[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]]||
----
=====Contributing to webERP=====
====GOALS of webERP====
~1. To provide **fast, web-based, integrated "best practise" business administration software**.
~2. To be **"low footprint"** efficient and fast, with absolutely minimal network traffic.
~This is to enable dial up/low band-width connections to work with reasonable response times. This will require some compromises with the use of graphics.
~3. **Platform independence**.
~Originally the use of Javascript was avoided due to the inconsistencies between implimentations. However, subject to certain rules javascript can be used.
~~1. Any use of javascript must have another server based option as a fallback - so client machines without javascript enabled will still function.
~~2. No significant blocks of javascript to choke dialup connections (see goal 2).
~~3. The javascript used should be used consistently throughout the code.
~4. Scripts **easily readable and modifiable by a business**.
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.
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.