Differences

This shows you the differences between two versions of the page.

--- coding_rules [2022/07/20 06:44] – atari
+++ coding_rules [2022/07/21 02:43] (current) – add some bullet point coding rules atari
@@ Line 7: / Line 7: @@
 In other words, don't try to handle all cases if it makes the software complicated and unmaintainable.
+  * Don't add new systems that are simply variations of other systems, aim to have one folder per system. An exception to this rule would be if a system required different configuration to launch, as asking the user to create two sets of custom emulator settings should be avoided.
+  * Don't put in [[:devices|device]]-specific ''if'' conditions into Batocera's ''/etc/init.d'' scripts. These should be applied via [[:udev_rules|udev rules]] for proper identification. Ultimately, it would be preferable to fix the global script in the first place to be suitable for all situations.
+  * Build emulators from their source where possible.
+  * Don't add emulators that duplicate the function of other emulators. We must avoid redundancy as there is an upper limit as to how much data can be packed into the ''batocera'' update file.
+  * Avoid making patches if possible, encourage the source developer of the software to fix issues upstream.
+  * Avoid adding files to the ''fsoverlay''. Fix the core root of the issue instead.
 <WRAP center round info>