bumblebee-status/bumblebee/modules/time.py

import datetime
import bumblebee.module

class Module(bumblebee.module.Module):
    def __init__(self, args):
        module = self.__module__.split(".")[-1]

        default = "%x" if module == "date" else "%X"
        self._fmt = args[0] if args else default

        super(Module, self).__init__(args)

    def data(self):
        return datetime.datetime.now().strftime(self._fmt)

# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4
[modules] Initial module loading framework Add a very simplistic framework for loading modules that query system data. The user can provide a list of modules via an argument switch, and the name of the module is used to look up a Python module that has to have a class called "Module". The outer framework (the outputs, in particular) then uses various query methods of that class to construct a meaningful output. 2016-10-30 16:30:09 +00:00			`import datetime`
[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 16:56:04 +00:00			`import bumblebee.module`

			`class Module(bumblebee.module.Module):`
[themes] Add "cycle" theme capability It is now possible to add a list of theme configurations in the "default" section called "cycle". These configuration items will be cycled through module by module. to create "alternate style" effects. This is only possible in the "default" configuration part, but any module-specific configurations still take precedence. Also, removed the capability of per-widget themes. That simply complicates things and probably doesn't really bring any benefits. 2016-10-31 09:45:15 +00:00			`def __init__(self, args):`
[modules] Add module "date" as alias of "time" The "time" module now has an alias (symlink) called "date". This is used to differentiate a widget showing the time from a widget showing the date. 2016-10-31 10:11:53 +00:00			`module = self.__module__.split(".")[-1]`

			`default = "%x" if module == "date" else "%X"`
			`self._fmt = args[0] if args else default`

[themes] Add "cycle" theme capability It is now possible to add a list of theme configurations in the "default" section called "cycle". These configuration items will be cycled through module by module. to create "alternate style" effects. This is only possible in the "default" configuration part, but any module-specific configurations still take precedence. Also, removed the capability of per-widget themes. That simply complicates things and probably doesn't really bring any benefits. 2016-10-31 09:45:15 +00:00			`super(Module, self).__init__(args)`
[modules] Initial module loading framework Add a very simplistic framework for loading modules that query system data. The user can provide a list of modules via an argument switch, and the name of the module is used to look up a Python module that has to have a class called "Module". The outer framework (the outputs, in particular) then uses various query methods of that class to construct a meaningful output. 2016-10-30 16:30:09 +00:00
			`def data(self):`
[modules/time] Add parameter for format string Format string for strftime is now configurable. Also, changed the separator for module name vs. arguments to "::" to make it possible to have ":" as part of the strftime format string (which is useful in most cases). Eventually, I'll probably have to come up with a better way, i.e. a fully-fledged parser, and move away from "special characters", but right now, the effort seems too much for the gain. 2016-10-31 09:53:31 +00:00			`return datetime.datetime.now().strftime(self._fmt)`
[modules] Initial module loading framework Add a very simplistic framework for loading modules that query system data. The user can provide a list of modules via an argument switch, and the name of the module is used to look up a Python module that has to have a class called "Module". The outer framework (the outputs, in particular) then uses various query methods of that class to construct a meaningful output. 2016-10-30 16:30:09 +00:00
			`# vim: tabstop=8 expandtab shiftwidth=4 softtabstop=4`