- 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.
- For each application, add ./tests directory and __init__.py file
within it.
- Modify test controllers (coverage.py, runtests.py) to find the new
test directories for testing and coverage analysis.
- Move existing application-specific test modules (test_pagekite.py) to
the newly created directories.
- It is conventional to store application data in /var/lib/APPDIR
instead of /var/APPDIR. Change ikiwiki data folder to
/var/lib/ikiwiki.
- After installing and before enabling and setting up basic
configuration, performing any operation such as 'create' wiki/blog
lead to silent errors. Do avoid this situation, perform a separate
setup() operation soon after the package is installed.
- In manage page, show a message to create new blog/wiki when there are
none.
- Elaborate on what gets deleted in delete page.
- Add Ikiwiki in menu item label. This is in order to allow for other
Wiki/Blog modules.
- Indentation changes.
