bumblebee-status/bumblebee/modules/cpu.py

# pylint: disable=C0111,R0903

"""Displays CPU utilization across all CPUs."""

import psutil
import bumblebee.engine

class Module(bumblebee.engine.Module):
    def __init__(self, engine):
        super(Module, self).__init__(engine,
            bumblebee.output.Widget(full_text=self.utilization)
        )
        self._utilization = psutil.cpu_percent(percpu=False)

    def utilization(self):
        return "{:05.02f}%".format(self._utilization)

    def update(self, widgets):
        self._utilization = psutil.cpu_percent(percpu=False)

# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4
[modules/cpu] Add initial version of CPU utilization module Re-enable the CPU utilization module as proof-of-concept for the new core engine. see #23 2016-12-04 17:45:42 +01:00			`# pylint: disable=C0111,R0903`

			`"""Displays CPU utilization across all CPUs."""`

			`import psutil`
			`import bumblebee.engine`

			`class Module(bumblebee.engine.Module):`
			`def __init__(self, engine):`
[core] Widget creation/update overhaul Until now, widgets were re-created during each iteration. For multiple, reasons, using static widget objects is much easier, so instead of creating new widgets continuously, modules now create the widgets during instantiation and get the list of widgets passed as parameter whenever an update occurs. During the update, they can still manipulate the widget list by removing and adding elements as needed. Advantages: * Less memory fragmentation (fewer (de)allocations) * Easier event management (widgets now have static IDs) * Easier module code (widget contents can simply be the result of a callback) see #23 2016-12-08 08:44:54 +01:00			`super(Module, self).__init__(engine,`
			`bumblebee.output.Widget(full_text=self.utilization)`
			`)`
[modules/cpu] Add initial version of CPU utilization module Re-enable the CPU utilization module as proof-of-concept for the new core engine. see #23 2016-12-04 17:45:42 +01:00			`self._utilization = psutil.cpu_percent(percpu=False)`

[core] Widget creation/update overhaul Until now, widgets were re-created during each iteration. For multiple, reasons, using static widget objects is much easier, so instead of creating new widgets continuously, modules now create the widgets during instantiation and get the list of widgets passed as parameter whenever an update occurs. During the update, they can still manipulate the widget list by removing and adding elements as needed. Advantages: * Less memory fragmentation (fewer (de)allocations) * Easier event management (widgets now have static IDs) * Easier module code (widget contents can simply be the result of a callback) see #23 2016-12-08 08:44:54 +01:00			`def utilization(self):`
			`return "{:05.02f}%".format(self._utilization)`
[modules/cpu] Add initial version of CPU utilization module Re-enable the CPU utilization module as proof-of-concept for the new core engine. see #23 2016-12-04 17:45:42 +01:00
[core] Widget creation/update overhaul Until now, widgets were re-created during each iteration. For multiple, reasons, using static widget objects is much easier, so instead of creating new widgets continuously, modules now create the widgets during instantiation and get the list of widgets passed as parameter whenever an update occurs. During the update, they can still manipulate the widget list by removing and adding elements as needed. Advantages: * Less memory fragmentation (fewer (de)allocations) * Easier event management (widgets now have static IDs) * Easier module code (widget contents can simply be the result of a callback) see #23 2016-12-08 08:44:54 +01:00			`def update(self, widgets):`
			`self._utilization = psutil.cpu_percent(percpu=False)`
[modules/cpu] Add initial version of CPU utilization module Re-enable the CPU utilization module as proof-of-concept for the new core engine. see #23 2016-12-04 17:45:42 +01:00
			`# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4`