i2c scaner ESP32

ESP32/i2c_scaner_esp32_dev/include/Colors.h

@@ -0,0 +1,48 @@
+
+#ifndef COLORS_H
+#define COLORS_H
+
+//RESET
+String fontReset = "\e[0m";
+
+//COLORS - REGULAR 
+String Black = "\e[0;30m";
+String Red = "\e[0;31m";
+String Green = "\e[0;32m";
+String Yellow = "\e[0;33m";
+String Blue = "\e[0;34m";
+String Purple = "\e[0;35m";
+String Cyan = "\e[0;36m";
+String White = "\e[0;37m";
+
+//COLORS - BOLD
+String boldBlack = "\e[1;30m";
+String boldRed = "\e[1;31m";
+String boldGreen = "\e[1;32m";
+String boldYellow = "\e[1;33m";
+String boldBlue = "\e[1;34m";
+String boldPurple = "\e[1;35m";
+String boldCyan = "\e[1;36m";
+String boldWhite = "\e[1;37m";
+
+//COLORS - UNDERLINED
+String underlineBlack = "\e[4;30m";
+String underlineRed = "\e[4;31m";
+String underlineGreen = "\e[4;32m";
+String underlineYellow = "\e[4;33m";
+String underlineBlue = "\e[4;34m";
+String underlinePurple = "\e[4;35m";
+String underlineCyan = "\e[4;36m";
+String underlineWhite = "\e[4;37m";
+
+//BACKGROUND - 
+String backgroundBlack = "\e[40;30m";
+String backgroundRed = "\e[41;31m";
+String backgroundGreen = "\e[42;32m";
+String backgroundYellow = "\e[43;33m";
+String backgroundBlue = "\e[44;34m";
+String backgroundPurple = "\e[45;35m";
+String backgroundCyan = "\e[46;36m";
+String backgroundWhite = "\e[47;37m";
+
+#endif

ESP32/i2c_scaner_esp32_dev/include/README

@@ -0,0 +1,39 @@
+
+This directory is intended for project header files.
+
+A header file is a file containing C declarations and macro definitions
+to be shared between several project source files. You request the use of a
+header file in your project source file (C, C++, etc) located in `src` folder
+by including it, with the C preprocessing directive `#include'.
+
+```src/main.c
+
+#include "header.h"
+
+int main (void)
+{
+ ...
+}
+```
+
+Including a header file produces the same results as copying the header file
+into each source file that needs it. Such copying would be time-consuming
+and error-prone. With a header file, the related declarations appear
+in only one place. If they need to be changed, they can be changed in one
+place, and programs that include the header file will automatically use the
+new version when next recompiled. The header file eliminates the labor of
+finding and changing all the copies as well as the risk that a failure to
+find one copy will result in inconsistencies within a program.
+
+In C, the usual convention is to give header files names that end with `.h'.
+It is most portable to use only letters, digits, dashes, and underscores in
+header file names, and at most one dot.
+
+Read more about using header files in official GCC documentation:
+
+* Include Syntax
+* Include Operation
+* Once-Only Headers
+* Computed Includes
+
+https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html