31,026
edits
Language and development rules: Difference between revisions
Jump to navigation
Jump to search
→Patterns of code organization
m (→Normes HTML) |
|||
| Line 189: | Line 189: | ||
=== Patterns of code organization === | === Patterns of code organization === | ||
[[wikipedia:Martin Fowler|Martin Fowler]] has identified 3 way to organize: | [[wikipedia:Martin Fowler|Martin Fowler]] has identified 3 way to organize: | ||
* The '''Transaction Script''' (The source code is linear for each user action). | * The '''Transaction Script''' (The source code is linear for each user action). | ||
| Line 200: | Line 199: | ||
This is a mix between 2 previous where we have only one unique class for each table of database. | This is a mix between 2 previous where we have only one unique class for each table of database. | ||
-> As shown in code skeletons (see previous chapter), Dolibarr use concept of '''Table Module'''. | |||
=== Communication between business logic - data (ORM) === | === Communication between business logic - data (ORM) === | ||