You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Readme.md
+22-2Lines changed: 22 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,18 +16,38 @@ MikroClick board supported:
16
16
- Thermo3
17
17
- Proximity
18
18
- Motion
19
-
- Relay
19
+
- Relay (partial support)
20
20
- Relay2
21
21
- Joystick
22
22
- Air quality
23
-
- Accel (SPI only)
23
+
- Accel
24
24
- 8x8R (Led Matrix)
25
25
- Alcohol
26
26
- IR eclipse
27
+
- IR distance
28
+
- Color
29
+
- Color2
30
+
- Bargraph
31
+
- 7Seg
32
+
- ADC
27
33
28
34
Examples are installed in /usr/bin/letmecreate_examples.
29
35
Tests are installed in /usr/bin/letmecreate_tests.
30
36
37
+
## Contributing to LetMeCreate
38
+
39
+
The master branch is the stable branch and the dev branch is merged to master just before doing a release. All pull requests must be done on dev branch.
40
+
Before creating a wrapper for a click board, make sure that it is not already supported in the dev branch. To avoid any overlap, contact me my email ([email protected]).
41
+
42
+
43
+
About code style, I follow roughly the [linux kernel coding style](https://www.kernel.org/doc/Documentation/CodingStyle) (two notable exceptions: indentation is set to 4 spaces and no 80 characters limit per line). Keep the style of your wrapper consistent with the rest of the code. For instance, most functions return 0 if they succeed and a negative number if not.
44
+
45
+
46
+
Each wrapper must implement features provided by only one click board. Do not mix code related to different click boards in a wrapper. Add doxygen documentation to all of your functions and do not forget to add a doxygen header on top of your header file otherwise the documentation will not be generated by doxygen.
47
+
48
+
49
+
Keep examples very simple and avoid parsing arguments. Examples are there to show one or two features of a **single** click board. Do not use multiple click boards in an example. The idea behind writing examples is to show how easy the library makes it using click boards. Hence, the shorter the example is, the better it is.
50
+
31
51
## Integration in Openwrt
32
52
33
53
To add new packages, Openwrt relies on feeds: a collection of packages.
0 commit comments