Procedural true performance

Procedural true performance

 
One of the benefits of this engine is the procedural speed people where asking or saying is not faster. But you can check your self How 2 loops not nested are faster the 1 nested loop.  

https://stackoverflow.com/questions/8547778/why-are-elementwise-additions-much-faster-in-separate-loops-than-in-a-combined-l?rq=1

Added to git hub don't like that much, all things done by hand, like move files by command, and only 1 which time. All tasks kind of manual. Only upload 100 file which time. No empty files. The program is suppose to fill those files they are not there just to take space. If they take any at all.

https://github.com/saintsoftware/the-box

Added the documentation folder.

This will help for people to learn in the project. For example, instead of reading a wikipédia article on JPG, we can get those articles and mount something more elaborated. Like width code examples. OR things connected width the project. In next update already have many stuff on BMP. If you need to learn BMP for raw applications or engines, you will have there a well planned documentations.

Folders for this:

->Documentation

   ->BMP
      -article1
      -article2
     ->JPG
    ->3D theory
...