- Remove apps and system modules and merge their views into main views.
- Move main_menu from cfg into menu.py.
- Remove dependencies of other modules on apps and system modules.
- Update tests.
Signed-off-by: Sunil Mohan Adapa <sunil@medhas.org>
Currently menu items are shown in alphabetical order in applications and
no clear order in system configuration. This is done using static
weights for menu items based on English names that does not work for
other locales.
Sorting can't be done at the time of adding menu items as users of
multiple locales may use the interface at the same time.
Implement a sorting mechanism based on existing order as well as labels
of menu item. This allows the flexiblity of grouping menu items in
future as it may be need for system configuration. In case of help menu
Remove sort order for all modules except for help menu as here we want
that specific order.
- The last part of the module import path is the module name. This also
becomes the Django app name. Apps names have to be unique. Hence,
there is no scope for two different modules with same name but
different load path to exist in the project.
- Most uses of list of loaded modules are dealing with app names instead
of full module load path. This is due to the fact that Django deals
with app names and not module paths.
- It is also somewhat clumsy to access a loaded module as we are
re-importing every time to get access module.
- Simplify all of the above by using app names are module identifiers
and maintaing an ordered dictionary of app names to loadded modules.
- Remove unused imports.
- Minor styling fixes.
- Change term 'reboot' to 'restart' as it is less techinical and more
consistent with popular interaces on desktop/mobiles.
- Updated description for power module.
- Simplify the module title to just 'Power'.
- Update the use of elipses and angular quotes as angular quotes and
elipses are both used to indicate that further user interface will be
available after pressing the button.
- Remove suprious '\' in power_reboot.html.
- Notify to the user that web interface will not be available after
reboot/shutdown.
- Redirect the user to application page after restart/shutdown. If the
page serve succeeds, they will have simply refresh/access it after
restart/shutdown after waiting or powering on.
