Standard Programing

As the concept evolve on the prototypes and structural programing though on that standard programing could be achieve width standard variable names and functions.

once we know that our paginator_result will hold always the information we could also inter-act width other languages and better inside the program but this is kind a bit to advanced and we are dependent on other people. Standard programing is not a simple concept that we can implement depend on other languanges and people that also adopt something similar.

The same variable name need to be accessible also in other languages the amount of work for that is pretty large.

---

The concept of standard programing main categorys : Variables\Folders\Templates\Files\Functions\data\DB\Includes\Translation\Color\Paths

•  The Variables which we can devide in several categorys:
• Settings - Often hold a pre value to be tweaked
• Rules - Kid of setting but more specific
• Values - Math calcs
• Information - Arrays
• Function kind - Fragmentation of function parts
• Data - Mainly raw info for db or files

• Functions 
• Think in C we can prototype functions but is not that advanced at the moment.

• Templates
• Another thing that can facility our life is to have a standard way to connect between code and interface.
• Design some main categorys so that we know which is doing what.
• Files
• How to acces your files and set a better path to files to be better to use standard.
• Data Base
• Databases often have a lot of redudancy and repetition. And one of those things that does not have a standard way of doing. It can extract alot of redability and accessibility. 
• But dbs are a complex thing to do standard since the way they are build is to create modularity. While in code people create modularity because they want. Is not that needed.
• Data 
• Data is one of those things that is lacking a lot of standards. Since companys often encode their code many of this files are not open source or are coded on top of the format.
• But acces them in a standard way could create a lot of better code.
• Folders
• Folders already debated often they are not organized...
• Includes or Librarys
• Includes inherit alot from the standard way. But depend on how you are going to stucture your project. 
• Still a bad planning of the includes will also end up causing problems in mainting code and modularity.
• For example many C librarys have a poorly implementation and could gain a lot if the moved to a standard form of implementation.
• Translate
• One timne shaw a guy asking where is the translate? Actually width so many years of programming there isn't still a simple and automated or maiby standard way of accessing it. 
• And translationg is something that most probjects as they evolve will eventualy need.
• Color
• Add colors in a standardized. Which application have a diferent way to add them hold be nice to have some kind of standard. Can you imagine the amount of work that could be saved? (
• At this time in 23 i need to change the color of the of the page. I know the code and i know the hex where do i applay? I do not have a standard way to know where it is still i have the knwoledge to do it. What that means? a couple of hours searching and testing. (waste of time).
• Paths
• Well there is a lot of stuff that we can make standard. But for now think this is more or less ok. Need to update more things. Paths is kind of a minimal thing. Not all small details are that relevant. Like if something makes you waste a couple of hours which time is relevant but if is just a few minutes... 

* This is still a work in progress