Renamed src to web cause it looks better!
src -> web in import paths.
Bare bones login handler.

The status code I want returned (405) isn't happening yet though. In the logs,
status 200 still appears.
GET login is now returning 405 status code.

Problem is cherrypy.response.headers.status should be cherrypy.response.status .
Added web directory to the path mapping.

Since, we are to run main from just outside web, for the sake of Python packaging
rules.
Trying to integrate the login model with main.py.

Changed the login model function to login_check to avoid function namespace
collisions.

Can't test since the MySQL version at home is outdated and PLDT myDSL is too
drop dead slow to even update.
More like the defuze tutorial.
The DB tool is working at last.

Problem is, I should've enabled it in the config as well but I didn't.

Still not working as there seems to be some errors in my models.
Errors resolved but DB queries are not yet issued as I expect.
Login hit now completely working.

The problem was that queries return tuples no matter what. The nested query
cherrypy.request.db.query(q.exists()) also contains nested tuples. I had to
append [0][0] (multidimensional indexing) to get the actual boolean return value.
Added web/ directory in template path.
Attempting basic log-in in CherryPy.
session should be sessions
Adding view element to indicate invalid log-in.
Set-up for AJAX log-in.

- Better styling of log-in fail indicator.
- Set-up of Javascript functions for log-in (index.js).
- Included Javascript in index.jinja.

Only problem now is that my local SQL isn't properly configured so I can't test
happy path log-in.
Tested AJAX call intergration.

However, there seems to be a problem with the @authentication_req decorator.
Hits to /dashboard are not being routed properly.
Some more debugging...
Getting to know decorators.
Added z-index 1 to login box.

For some weird reason, the text boxes suddenly became inaccessible both in
Chromium and in Firefox. Specifying z-index resolves the issue.
Reorganized functions in main. Dashboard is now authenticated properly.

BUT the authenticating function is not yet fully working. Need to check on
sending request with cookies.