Mostly pjdatechy. "what was DJ thoughts process like when he was developing the micro-controller for the EZ-B along with the EZ-Board. How in the world did he create such a complex yet simple platform for all to use."

Personally speaking (and I hear a lot of devs say it too), the coding is the easy part. Once you figure out what you want to achieve, how you will achieve it then you just need to change parts of it so that it's flexible. Not to take anything away from the awesomeness of ARC but making it configurable for multiple users was probably the easiest part for DJ.

Each control is pretty much going to be the same from user to user, the only changes are the EZ-B board/port number. It's all very much like in my Ping Roam script where I have the variables set at the start for the ports and settings. The script itself could be complex or it could be simple, it's irrelevant.

Each of the ARC native controls is like a script (I'm using this as an example as you can look at one of my scripts and you can see the complex parts but also see how easily it is to adapt to your own circumstances). Options for those parts which could change, like port number or minimum distance, phrase, timings, min and max positions or whatever are added in. That can be done for any complex algorithm with ease.