Rules

Rules, Steps & methods

This is the current way to implement and be implemented but there could be more things to add :

1. Root or loader  (which load things in to the interface, all frameworks\engines have or should have a loader, so it automates many things).
2. Prototypes or Pseudo objects (can also be called schemes, whis is what they are schematics for problems solved or rules)
3. Global inheritance ( like Variables in scheames, may also be defined as inherarquy)
4. Stack Librarys (format code in files that can inherit global variables )
5. Fuctions (also should work on a global scale)
6. DTR  (Database text fromat reader, a kind of tool to improve performance, but a thing that all project uses they way to deal width information can also be called data structures)
7. Stand alone programs (for easy to develop, this is optional you don't need to do like this)
8. Standard Coding (which we could divide in to several parts like standard names, a fixed set of names so that we can access at any time)
9. Unit tests (tests should be available in any project that have a large size.)
10. Librarys (part of standard coding, a basic set of high quality raw assets that allow to create and set up a project, their names should be standard so that they are ready to include).
11. Structure (this is kind of a more theory, once we decompose our framework or engine in to all this steps we have a structure framework. Every thing is decomposed on a ready to use hierarquy... )
12. Hierarquy (part of the structure a simple way to see what we need to have at the higher levels)

Also whant to add more steps but this are more a on develop  :

• Templates (applay the standard structure that we can easy use templates in to projects)
• Modules (a bit the same as templates)
• Interfaces (can be a part of templates

We are going throw this topics to explain them this topis also are like a index in a book. Is not 100% ordered only aprox