bumblebee-status/bumblebee/modules/test.py

# pylint: disable=C0111,R0903

"""Test module"""

import bumblebee.engine

class Module(bumblebee.engine.Module):
    def __init__(self, engine, config):
        super(Module, self).__init__(engine, config,
            bumblebee.output.Widget(full_text="test")
        )

    def update(self, widgets):
        pass

# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4
[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +01:00			`# pylint: disable=C0111,R0903`

			`"""Test module"""`

			`import bumblebee.engine`

			`class Module(bumblebee.engine.Module):`
[modules/datetime] Use parameter functionality to get format Make the format string of the datetime module configurable using the new parameter() method in the module. Also, restructured the setting of the config information a bit so that the parameter() method can be used in the constructor of a module. see #23 2016-12-09 08:23:53 +01:00			`def __init__(self, engine, config):`
			`super(Module, self).__init__(engine, config,`
[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			`bumblebee.output.Widget(full_text="test")`
			`)`
[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +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):`
			`pass`
[output/i3bar] Add flush method flush() terminates a single iteration of widget drawing. see #23 2016-12-04 16:14:43 +01:00
[core/engine] Add module loading logic Allow the engine to load modules from the bumblebee/modules/ directory. see #23 2016-12-04 11:09:10 +01:00			`# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4`