bumblebee-status/bumblebee/module.py


class Module(object):
    def __init__(self, theme, args):
        self._theme = theme

    def theme(self):
        return self._theme

    def data(self):
        pass

    def state(self):
        return "default"

# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4
[themes] Add themeing framework Add - again a very simplistic - method for themeing the output. Essentially, the plan is to have JSON-formatted configuration files in bumblebee/themes/ and have a separate class for querying the config whenever the output needs to know about semantic formatting/coloring. Note that the theme object is stored on a per-module basis. Right now, that doesn't have any effect (except looking particularly wasteful), but the idea is to be able to have different themes for different modules in the future. 2016-10-30 17:56:04 +01:00
			`class Module(object):`
[modules] Add battery indicator plugin Add a plugin that displays the remaining battery power in %. This also introduces the concept of arguments that can be passed to a module during startup by delimiting the module name with ":", for example: -m battery:BAT1 to query the BAT1 device. Note that this works to an arbitray length, i.e. if a module accepts 3 parameters: -m <modulename>:<A>:<B>:<C> The module gets the arguments as list. 2016-10-30 18:10:25 +01:00			`def __init__(self, theme, args):`
[themes] Add themeing framework Add - again a very simplistic - method for themeing the output. Essentially, the plan is to have JSON-formatted configuration files in bumblebee/themes/ and have a separate class for querying the config whenever the output needs to know about semantic formatting/coloring. Note that the theme object is stored on a per-module basis. Right now, that doesn't have any effect (except looking particularly wasteful), but the idea is to be able to have different themes for different modules in the future. 2016-10-30 17:56:04 +01:00			`self._theme = theme`

			`def theme(self):`
			`return self._theme`

[themes] Make individual items theme-able (a bit) Individual items in the bar can now be configured with a prefix and a suffix. It works like this: * If there is a specific module configuration in the theme configuration, use that (i.e. { "<modulename>": { "prefix: " a " } }) * Otherwise, if there is a configuration in the "default" section of the theme, use that * Otherwise, if the module object itself has a method called like the required attribute (prefix, suffix), use that * Otherwise, leave prefix/suffix empty ("") 2016-10-31 07:18:57 +01:00			`def data(self):`
			`pass`

			`def state(self):`
			`return "default"`

[themes] Add themeing framework Add - again a very simplistic - method for themeing the output. Essentially, the plan is to have JSON-formatted configuration files in bumblebee/themes/ and have a separate class for querying the config whenever the output needs to know about semantic formatting/coloring. Note that the theme object is stored on a per-module basis. Right now, that doesn't have any effect (except looking particularly wasteful), but the idea is to be able to have different themes for different modules in the future. 2016-10-30 17:56:04 +01:00			`# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4`