luci/modules/luci-mod-system/htdocs/luci-static/resources/view/system/led-trigger/heartbeat.js

'use strict';
'require baseclass';

return baseclass.extend({
	trigger: _('Heartbeat interval (kernel: heartbeat)'),
	description: _('The LED flashes to simulate actual heart beat.') +
		_('The frequency is in direct proportion to 1-minute average CPU load.'),
	kernel: true,
	addFormOptions: function(s) {}
});
luci-mod-system: add led plugin infrastructure This commit creates the possibility that not only kernel-led-triggers can be selected but also application-led-triggers from user space. This is done via a plugin mechanism. The application-led-triggers are scripts that set kernel-led-triggers on system events or services. Until now this has not been possible. The package rssileds is a kind of application-led-trigger. The following new packages are added: * luci-app-ledtrig-rssi (application-led-trigger) * luci-app-ledtrig-switch (kernel-led-trigger) not needed on every most devices * luci-app-ledtrig-usport (kernel-led-trigger) optional trigger Since we have now a plugin mechanism I have added the following triggers as a dependency. So this triggers are now installed per default on LuCI installation. * kmod-ledtrig-default-on * kmod-ledtrig-heartbeat * kmod-ledtrig-netdev * kmod-ledtrig-timer The kernel trigger kmod-ledtrig-usbdev was removed with the commit https://github.com/openwrt/openwrt/commit/d0b50c2770a0e2d54b37153f2801e2e7dc865fa6 So I have not ported the relevant code anymore. Signed-off-by: Florian Eckert <fe@dev.tdt.de> 2020-02-20 11:04:12 +00:00			`'use strict';`
treewide: import utility classes explicitly Signed-off-by: Jo-Philipp Wich <jo@mein.io> 2020-04-03 08:00:06 +00:00			`'require baseclass';`
luci-mod-system: add led plugin infrastructure This commit creates the possibility that not only kernel-led-triggers can be selected but also application-led-triggers from user space. This is done via a plugin mechanism. The application-led-triggers are scripts that set kernel-led-triggers on system events or services. Until now this has not been possible. The package rssileds is a kind of application-led-trigger. The following new packages are added: * luci-app-ledtrig-rssi (application-led-trigger) * luci-app-ledtrig-switch (kernel-led-trigger) not needed on every most devices * luci-app-ledtrig-usport (kernel-led-trigger) optional trigger Since we have now a plugin mechanism I have added the following triggers as a dependency. So this triggers are now installed per default on LuCI installation. * kmod-ledtrig-default-on * kmod-ledtrig-heartbeat * kmod-ledtrig-netdev * kmod-ledtrig-timer The kernel trigger kmod-ledtrig-usbdev was removed with the commit https://github.com/openwrt/openwrt/commit/d0b50c2770a0e2d54b37153f2801e2e7dc865fa6 So I have not ported the relevant code anymore. Signed-off-by: Florian Eckert <fe@dev.tdt.de> 2020-02-20 11:04:12 +00:00
treewide: import utility classes explicitly Signed-off-by: Jo-Philipp Wich <jo@mein.io> 2020-04-03 08:00:06 +00:00			`return baseclass.extend({`
luci-mod-system: update LED trigger translations Signed-off-by: Florian Eckert <fe@dev.tdt.de> 2020-04-28 13:59:49 +00:00			`trigger: _('Heartbeat interval (kernel: heartbeat)'),`
luci-mod-system: add led-trigger description Signed-off-by: Florian Eckert <fe@dev.tdt.de> 2021-09-02 12:52:23 +00:00			`description: _('The LED flashes to simulate actual heart beat.') +`
			`_('The frequency is in direct proportion to 1-minute average CPU load.'),`
luci-mod-system: add led plugin infrastructure This commit creates the possibility that not only kernel-led-triggers can be selected but also application-led-triggers from user space. This is done via a plugin mechanism. The application-led-triggers are scripts that set kernel-led-triggers on system events or services. Until now this has not been possible. The package rssileds is a kind of application-led-trigger. The following new packages are added: * luci-app-ledtrig-rssi (application-led-trigger) * luci-app-ledtrig-switch (kernel-led-trigger) not needed on every most devices * luci-app-ledtrig-usport (kernel-led-trigger) optional trigger Since we have now a plugin mechanism I have added the following triggers as a dependency. So this triggers are now installed per default on LuCI installation. * kmod-ledtrig-default-on * kmod-ledtrig-heartbeat * kmod-ledtrig-netdev * kmod-ledtrig-timer The kernel trigger kmod-ledtrig-usbdev was removed with the commit https://github.com/openwrt/openwrt/commit/d0b50c2770a0e2d54b37153f2801e2e7dc865fa6 So I have not ported the relevant code anymore. Signed-off-by: Florian Eckert <fe@dev.tdt.de> 2020-02-20 11:04:12 +00:00			`kernel: true,`
luci-mod-system: add missing require to `none` led trigger class Also convert ES6 to ES5 syntax while we're at it. Fixes: #5476 Fixes: 5b42cd5b46 ("luci-mod-system: move default option from defaul-on trigger to none trigger") Signed-off-by: Jo-Philipp Wich <jo@mein.io> 2021-10-31 21:26:42 +00:00			`addFormOptions: function(s) {}`
luci-mod-system: add led plugin infrastructure This commit creates the possibility that not only kernel-led-triggers can be selected but also application-led-triggers from user space. This is done via a plugin mechanism. The application-led-triggers are scripts that set kernel-led-triggers on system events or services. Until now this has not been possible. The package rssileds is a kind of application-led-trigger. The following new packages are added: * luci-app-ledtrig-rssi (application-led-trigger) * luci-app-ledtrig-switch (kernel-led-trigger) not needed on every most devices * luci-app-ledtrig-usport (kernel-led-trigger) optional trigger Since we have now a plugin mechanism I have added the following triggers as a dependency. So this triggers are now installed per default on LuCI installation. * kmod-ledtrig-default-on * kmod-ledtrig-heartbeat * kmod-ledtrig-netdev * kmod-ledtrig-timer The kernel trigger kmod-ledtrig-usbdev was removed with the commit https://github.com/openwrt/openwrt/commit/d0b50c2770a0e2d54b37153f2801e2e7dc865fa6 So I have not ported the relevant code anymore. Signed-off-by: Florian Eckert <fe@dev.tdt.de> 2020-02-20 11:04:12 +00:00			`});`