ThinkPad thermal monitor, display ThinkPad thermal and fan status using /proc/acpi/ibm/thermal and /proc/acpi/ibm/fan.
Note: Binary files aren't shown on the web site. To see all files, please download the extension zipfile.
| Version | Status |
|---|---|
| 35 | Active |
| 34 | Inactive |
| 33 | Inactive |
| 32 | Rejected |
| 31 | Active |
| 30 | Active |
| 29 | Inactive |
| 28 | Inactive |
| 27 | Inactive |
| 26 | Active |
| 25 | Inactive |
| 24 | Inactive |
| 23 | Inactive |
| 22 | Inactive |
| 21 | Rejected |
| 20 | Inactive |
| 19 | Rejected |
| 18 | Rejected |
| 17 | Active |
| 16 | Inactive |
| 15 | Inactive |
| 14 | Inactive |
| 13 | Inactive |
| 12 | Inactive |
| 11 | Inactive |
| 10 | Inactive |
| 9 | Inactive |
| 8 | Inactive |
| 7 | Rejected |
| 6 | Inactive |
| 5 | Inactive |
| 4 | Inactive |
| 3 | Inactive |
| 2 | Inactive |
| 1 | Active |
1. Don't call functions in global scope (line 86-87, 204-211 `extension.js`). 2. `lookupByURL()` is a bad practice (line 658 `extension.js`). You can send `this` from the entry point to the class needing it when it's possible (dependency injection).
1. What would be the preferred way of handling constants? 2. Is there any other way to resolve the path? I'd gladly remove that call if possible otherwise
1. If you are using `new` keyword you can move it to the function using it and create it there. If you don't like that approach, create a static class with init and uninit. Call `uninit` in disable to clean up everything you've do in `init`. Just remember to don't create any instance before init (like static property with initial value using `new`). 2. The other way would be using a global. For example: ```js enable() { ME = this; } disable() { ME = null; } ```
ThinkPad Thermal