For further development of the fritzing software, an open source application, it is better to add the arduino code checking feature of this application. In that way it is easier to know if the codes created was correct or it has some errors. Then it is easier to troubleshoot if ever there is an error in the codes by displaying the number of rows or columns in which the error occurs. As an example, let us consider the simple digital thermometer below.
So here is the arduino codes needed for the digital thermometer
As you can see in the figure, there is no way to check if these codes were correctly programmed. No feature for automatic checking of the programmed codes.
If ever there is a long programmed codes we cannot troubleshoot it directly because we don’t know which part of the codes has an errors. I consider it as a disadvantage to the user especially for the beginners in arduino programming. To have a better and user friendly fritzing application, a feature that could help the users must be added in this software.
So here is my suggestion
(Name of this icon: "Build Project" )
This icon must be included in the application which function is to build the program and after that it will automatically display at the bottom if it is successful which means no errors occur or else display the line in which errors occur.
So the fritzing software will now look like this.
Where if there is an error in the program, it will display like this below.
If no errors occur, it will display success.
Conclusion
In troubleshooting an electronic project, it is hard to find the problem if it is on the system or it is embedded in the program itself. So to avoid this scenario, it is better if the programmed codes were already checked automatically so that the troubleshooting would be easier to do. To create an electronic project, we can rely on the software that we will be using.
I hope this suggestion will help in developing a better and user friendly fritzing software.
Yours Truly,
@rfece143
Posted on Utopian.io - Rewarding Open Source Contributors