Standard programming now includes a lot of stuff. It start just by affecting variables but now have extended to other parts of the project.
Often the projects have a big mess in the folder & files structure.
One of the things in standard programming is to represent the files in the folders. A folder that contain include files should be named "includes" we can't read it other way :
The Box folder structure->
Abstract -> a folder to have sub includes files, they often have some kind of data or functionality.
Includes -> Normal includes people mix them width macros, but many things does not need to be in a header file.
Headers -> It could be renamed to macros, but for now is just headers. Trudly header files that contain macros mainly. Macros and header files are pre processor you can only gain performance width them.
Progs -> Standalone option for the main this will easy development. Cause less bugs, to develop things separitly and if need to load less stuff.
Data -> To store our dinamic data
Projects -> Other stuff we do
The structure is becoming very redable...
This way we do not need study the project structure which is time consuming. Lets imagine you have to read 1000 projects on git hub what kind of projects will you prefer to study? A time saving option, width folders representing what it's inside.
Think in putting some files,
No comments:
Post a Comment