Goals of the project: FidoCadJ is meant to be an easy to use 2D drawing program with a large library of symbols for electronic circuits. FidoCadJ is meant to be great when you want to draw a small circuit for a publication or a slide for a presentation. It is a great tool when you want to discuss about a circuit in a forum or with your colleagues. It does not mean to become a full-fledged CAD program for electronic circuits. For this, we fully support projects like KiCad.

Digital minimalism FidoCad/J tries to be as affective as possible, so that the user interaction is minimized. The least time the user shall spend using FidoCadJ to solve a problem, the better. This requires a clean and efficient interface and an efficient use of computing resources.

Self consistency FidoCadJ is meant to be a self-contained and self-consistent project. It is not meant to became dependent of an external server or online service.

Avoidance of software bloat FidoCadJ avoids as much as possible hard dependencies from external libraries or projects (with the notable exception of the JRE). "Soft" dependencies can be tolerated in certain situations, such as for fine-tweaking of the user interface appearance on modern operating systems. In any case, the future of FidoCadJ should not be linked to a particular library or tool that may become unsupported or introduce a cause of bloat of software rot.

Openness and documentation FidoCadJ is meant to be documented, accessible and open. It promotes  ...
Goals of the project: FidoCadJ is meant to be an easy to use 2D drawing program with a large library of symbols for electronic circuits. FidoCadJ is meant to be great when you want to draw a small circuit for a publication or a slide for a presentation. It is a great tool when you want to discuss about a circuit in a forum or with your colleagues. It does not mean to become a full-fledged CAD program for electronic circuits. For this, we fully support projects like KiCad. Digital minimalism FidoCad/J tries to be as affective as possible, so that the user interaction is minimized. The least time the user shall spend using FidoCadJ to solve a problem, the better. This requires a clean and efficient interface and an efficient use of computing resources. Self consistency FidoCadJ is meant to be a self-contained and self-consistent project. It is not meant to became dependent of an external server or online service. Avoidance of software bloat FidoCadJ avoids as much as possible hard dependencies from external libraries or projects (with the notable exception of the JRE). "Soft" dependencies can be tolerated in certain situations, such as for fine-tweaking of the user interface appearance on modern operating systems. In any case, the future of FidoCadJ should not be linked to a particular library or tool that may become unsupported or introduce a cause of bloat of software rot. Openness and documentation FidoCadJ is meant to be documented, accessible and open. It promotes ...