Recent changes to Checklist

Checklist modified by Alec Leamas

Alec Leamas — Tue, 31 Jan 2017 14:40:51 -0000

--- v15
+++ v16
@@ -61,7 +61,7 @@
 ## NOTES:

 ### Filenames:
-configuration files are named *.lircd.conf, photos like *.jpg (or *.gif, *.png). 
+configuration files are named *.lircd.conf, photos like \*.jpg (or \*.gif, \*.png). 
 They live in a directory named after the vendor. If the file only contains one remote, 
 use the same name as the name attribute. Example:

Checklist modified by Alec Leamas

Alec Leamas — Tue, 31 Jan 2017 14:38:59 -0000

--- v14
+++ v15
@@ -74,6 +74,7 @@
    symbol prefixed with KEY_ is supposed to be a standard symbol.
  + For mouse clicks use BTN_LEFT, BTN_RIGHT
  + For mouse movements use MOUSE_N, MOUSE_S, MOUSE_NW, MOUSE_SE, etc.
+ + Use KEY_0..KEY_9, not KEY_NUMERIC_0 etc.
  + KEY_RED..KEY_BLUE is preferred to KEY_A..KEY_D.

 lirc-config-tool -sc scans file for "bad" symbols. lirc-config-tool -uc can

Checklist modified by Alec Leamas

Alec Leamas — Mon, 07 Sep 2015 15:59:53 -0000

--- v13
+++ v14
@@ -25,6 +25,7 @@

   - Config file should use proper name symbols from namespace where applicable (use 
     ```lirc-config-tool -sc <file>``` to check status).
+  - If not writing a remote layout (below),  document  all non-obvious button bindings.

   - There should be no parsing errors. Use ```lirc-lsremotes  -s <file>```, verify that 
     there is no output

Checklist modified by Alec Leamas

Alec Leamas — Fri, 13 Mar 2015 12:12:20 -0000

--- v12
+++ v13
@@ -23,8 +23,6 @@

     + Device(s) controlled.

-    + Remote layout (ascii art showing symbol for each button).
-
   - Config file should use proper name symbols from namespace where applicable (use 
     ```lirc-config-tool -sc <file>``` to check status).

@@ -47,7 +45,7 @@

  - Photo of remote (scale to ~100 kb).

- - ASCII sketch showing symbols used for each button (below).
+ - Remote layout (ascii art showing symbol for each button).

  - Is there any known kernel configuration e. g., blacklisted kernel modules or 
    specific kernel drivers?

Checklist modified by Alec Leamas

Alec Leamas — Fri, 13 Mar 2015 12:10:27 -0000

--- v11
+++ v12
@@ -46,6 +46,8 @@
 ## SHOULD:

  - Photo of remote (scale to ~100 kb).
+ 
+ - ASCII sketch showing symbols used for each button (below).

  - Is there any known kernel configuration e. g., blacklisted kernel modules or 
    specific kernel drivers?

Checklist modified by Alec Leamas

Alec Leamas — Wed, 22 Oct 2014 14:32:46 -0000

--- v10
+++ v11
@@ -31,7 +31,7 @@
   - There should be no parsing errors. Use ```lirc-lsremotes  -s <file>```, verify that 
     there is no output

-  - Are all buttons handled? If not, write a short not on why.
+  - Are all buttons handled? If not, write a short note on why.

   - Check that repeat codes works properly as described in [manual]

Checklist modified by Alec Leamas

Alec Leamas — Wed, 22 Oct 2014 14:31:20 -0000

--- v9
+++ v10
@@ -11,10 +11,6 @@
   - Each config file should correspond to one physical device.

   - All data supplied?
-
-    + Kernel revision (uname -r).
-
-    + irrecord --driver and --device option used.

     + Name of remote device, the thing you hold in your hand.

@@ -31,8 +27,13 @@

   - Config file should use proper name symbols from namespace where applicable (use 
     ```lirc-config-tool -sc <file>``` to check status).
+
   - There should be no parsing errors. Use ```lirc-lsremotes  -s <file>```, verify that 
     there is no output
+
+  - Are all buttons handled? If not, write a short not on why.
+
+  - Check that repeat codes works properly as described in [manual]

   - Files with raw data should if possible be converted using irrecord -a

@@ -54,7 +55,6 @@
  - If the remote can be decoded in different ways e. g., like intelligent, 
    multi-purpose devices,  several remote definitions should be put in the config 
    file.
-

 ## NOTES:

Checklist modified by Alec Leamas

Alec Leamas — Thu, 16 Oct 2014 07:57:29 -0000

--- v8
+++ v9
@@ -1,6 +1,8 @@
 # Remote configuration file checklist.

-To make a configuration file truly useful to others we need to complete it according to the following. Most of the existing remotes does not live up to these standards, but we really wish they did....
+To make a configuration file truly useful to others we need to complete
+it according to the following. Most of the existing remotes does not live 
+up to these standards, but we really wish they did....

 ## MUST:

@@ -18,7 +20,8 @@

     + Does remote device has a bundled capture device e. g., a usb dongle?

-    + For bundled USB capture  devices: usb vendor id, product id and device string (using dmesg or lsusb).
+    + For bundled USB capture  devices: usb vendor id, product id and device string 
+     (using dmesg or lsusb).

     + Type of device controlled (TV, VCR, Audio, DVD, Satellite, Cable, PVR, HTPC, ...)

@@ -26,8 +29,10 @@

     + Remote layout (ascii art showing symbol for each button).

-  - Config file should use proper name symbols from namespace where applicable (use ```lirc-config-tool -sc <file>``` to check status).
-  - There should be no parsing errors. Use ```lirc-lsremotes  -s <file>```, verify that there is no output
+  - Config file should use proper name symbols from namespace where applicable (use 
+    ```lirc-config-tool -sc <file>``` to check status).
+  - There should be no parsing errors. Use ```lirc-lsremotes  -s <file>```, verify that 
+    there is no output

   - Files with raw data should if possible be converted using irrecord -a

@@ -41,18 +46,23 @@

  - Photo of remote (scale to ~100 kb).

- - Is there any known kernel configuration e. g., blacklisted kernel modules or specific kernel drivers?
+ - Is there any known kernel configuration e. g., blacklisted kernel modules or 
+   specific kernel drivers?

  - URL with remote device information.

- - If the remote can be decoded in different ways e. g., like intelligent, multi-purpose devices,  several remote definitions should be put in the config file.
+ - If the remote can be decoded in different ways e. g., like intelligent, 
+   multi-purpose devices,  several remote definitions should be put in the config 
+   file.

 ## NOTES:

 ### Filenames:
-configuration files are named *.lircd.conf, photos like *.jpg (or *.gif, *.png). They live in a directory named after the vendor. If the file only contains one remote, use the same name as the name attribute. Example:
+configuration files are named *.lircd.conf, photos like *.jpg (or *.gif, *.png). 
+They live in a directory named after the vendor. If the file only contains one remote, 
+use the same name as the name attribute. Example:

     Photo:        samsung/AA59-00600A.jpg
     Config file:  samsung/AA59-00600A.lircd.conf

Checklist modified by Alec Leamas

Alec Leamas — Wed, 15 Oct 2014 20:54:00 -0000

--- v7
+++ v8
@@ -26,7 +26,8 @@

     + Remote layout (ascii art showing symbol for each button).

-  - Config file should use proper name symbols from namespace where applicable (use lirc-config-tool -sc to check status).
+  - Config file should use proper name symbols from namespace where applicable (use ```lirc-config-tool -sc <file>``` to check status).
+  - There should be no parsing errors. Use ```lirc-lsremotes  -s <file>```, verify that there is no output

   - Files with raw data should if possible be converted using irrecord -a

Checklist modified by Alec Leamas

Alec Leamas — Wed, 15 Oct 2014 20:45:59 -0000

--- v6
+++ v7
@@ -117,7 +117,7 @@

 ###    Examples made according to new standards:

-  - [samsung/AA59-00600A.conf](https://sourceforge.net/p/lirc-remotes/code/ci/master/tree/remotes/samsung/AA59-00600A.lircd.conf)
+  - [samsung/AA59-00600A.lircd.conf](https://sourceforge.net/p/lirc-remotes/code/ci/master/tree/remotes/samsung/AA59-00600A.lircd.conf)