subiquity/subiquitycore/ui
Michael Hudson-Doyle dad0e10912 completely separate menu -> signal and signal -> method mappings
and put the signal -> method mapping into the controller

this breaks the subiquity part even more than before, but it's pretty broken
already.
2016-09-27 20:53:17 +13:00
..
views completely separate menu -> signal and signal -> method mappings 2016-09-27 20:53:17 +13:00
__init__.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
anchors.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
buttons.py Make it a little more obvious where labels are in fact buttons or menus 2016-08-16 15:01:51 -04:00
dummy.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
error.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
frame.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
interactive.py Start at a login view. 2016-07-28 10:30:27 +12:00
lists.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
utils.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00
widgets.py Rename subiquity to subiquitycore -- will serve as base classes for everything 2016-06-30 14:17:01 -04:00