Flavien OpenCat code reviews

The new architecture is better structured to separate modules into different header files. The main workflow is in OpenCat.ino or OpenCatEsp32.ino.

The new architecture is indeed better structured but it is also much more complex and more difficult to understand. That is why I think it needs a code review (which I called a code walk-through above) by someone who knows the source code in these repos very well, preferably by someone who has written that code.

The Arduino source code uses many pointers and classes to improve efficiency and fit in the chip's limited storage. Some algorithms were written when I was preparing for the interview with Google. The tricks to combine complex cases into one-line conditions can take hours to explain. in Variables that may also correlate with many files and the circuit.  Even I will make mistakes when modifying the source code. So it takes a lot of work to explain the code. It can be a thick book. 

To make it easier for people interested in Arduino programming, there's also a simpler interface that only requires an understanding of the application layer. It's the taskQueue method. It uses the same serial command rules in an altered format and can run directly within the Arduino source code. You can refer to the extensible modules, and check how the robot can read sensor data and react within the scope of a single file. For example, you can activate the macro of DOUBLE_TOUCH, and the code defining all its behaviors is in src/doubleTouch.h. 

@Rongzhong Li ahhhh, that makes sense. I didnt modify it a lot, just 1 or 2 parametres on the speed, instead of 4/10/10, i did 4/4/4 so bittle wave hi slowly.......but I wasnt aware the balance was such an important position called after every move. makes sense and your help is appreciated once again. I'm starting to love it!

A last but important question: once I define all the skills and want to change their frames, do I also need to upload opencat.ino everytime? I thought if all I changed were parameters within the frames, but not adding or removing or renaming any skills, can I not just upload "instinct.h" alone? do I need to open serial monitor and say "y" to writinstincts again/everytime?----edit: my tests indicate 3 actions after every change in order for everything to work nicelly: after simple changes in InstinctBittle.h, I follow these steps: 1) open and upload WriteInstinct.ino; 2) open serial monitor and say "y" to write instincts; 3) upload opencat.ino.

I know if I do them everytime things work, but is there a simpler way to do it or the aboves steps is the way to go? thanks, I promisee I wont be bombarding you with newby questions soon. Cheers

If you define the skill as a Newbility by adding an 'N' suffix in its skill name, you only need to upload the first round of code for once to register its address. Later you won't need to do the two round uploading, just upload OpenCat.ino will update it, because the new skill will be saved in the flash.

Hi, I don't remember whether I have replied to you elsewhere. There's a shorter instinct.h file you can use. We also restructured the doc center and included a step-by-step tutorial to understand and create new skills. There's also a graphical tool to create new skills.

The link to the "step-by-step tutorial" is broken. Has it moved or has it been deleted because it is obsolete?

It was merged with the new graphical user interface. I just updated the link.