Rename mixevals_question* tbl to mixeval_question*

Remove the s from mixevals to more conform with CakePHP 1.3 conventions.
Remove more dead css.

Delete more css that isn't used anymore. Or merge css that doesn't have
to be by itself.
Add mixeval_question_types table.

This should make it easier to add question types to mixeval_questions.
There are a few feature requests on trac about new question types, this
is preliminary work meant to help implement these new question types.

Note that the question_type column in mixeval_questions is now
mixeval_question_type_id, it's a foreign key mapped to the the new
mixeval_question_types table.

Also added some instructions to the sample mixeval questions for testing
that instruction display is working in mixeval.
Rename question_type to mixeval_question_type_id.

Due to the new mixeval_question_types table, have to fix all the
hardcoded references to the old question_type column in
mixeval_questions to the new mixeval_question_type_id column.
Fix test cases broken by mixeval_question_type.

Just need to add the mixeval_question_type fixture in most of the cases.
Though, for some reason, have to add a giant host of other dependencies
too.
Remove response_type from mixeval_questions.

Turns out that the comment responses are further split up into single
line or multiline responses. And this is determined by the response_type
column in mixeval_questions. Since this doesn't fit into the new scheme
where question types are determined by the mixeval_question_types table,
I've removed the response_type column from mixeval_questions.

I've renamed the "Comment" response in mixeval_question_types to
"Paragraph" and added a "Sentence" entry. So the "Paragraph" question
type indicates a multiline response and the "Sentence" question type
indicates a single line response. Multiline/single line responses
differ in that multiline responses are entered using a <textarea> while
a regular single line response uses an <input>.
Mixevals/view/$id works with mixeval_question_type

Mixeval view now understands how to display questions using the new data
available from mixeval_question_type.

Note that this removed the almost unmaintainable javascript viewer for a
pure server side php version.

Instead of a combined view/edit/add page for mixeval, I've now created a
separate view.ctp file specifically for mixeval view.
Fix install5 printing config dirs as %s.

Printf expected a string for formatting but got a return value from the
__() function instead.
Mixeval view, add response required marker.

Certain questions require the user to input a response, this is now
indicated by an * on the right hand side of the question prompt.
Fix misaligned send email notification label.

The send email notification checkbox's label was floating to the left of
the checkbox like it's supposed to. This was due to it having a custom
div class of "email" so it didn't get the general rules for all labels.
Fixed by removing the custom div class and some extraneous css.
User controller, remove dead code
Fix favicon display on subdirectory pages.

The missing / in front of the favicon location means that the browser
tries to resolve it as a relative image, which means that the favicon
can't be found when we're in a subdirectory.
Half operational new mixeval add page.

With new question editor that looks much better but is still just as
responsive.

Question type templates are generated by using CakePHP's helpers and
then passed to javascript or the dynamic interactions. This is done so
we can restore previously submitted questions using php if a save fails.
Remove unnecessary fields from mixeval table.

The information stored in these fields can be obtained from
MixevalQuestions and shouldn't be stored in the db.
Fixes for db bugs in mixeval related views.

Changing the mixeval table resulted in some of the not directly mixeval
views breaking, such as Evaltools which lists all evaluations.
New mixeval add now fully functional.

Supports likert questions now and can actually save the mixeval properly
to database.

Saving to the database is a bit complicated due to the need to use
transactions. Since CakePHP does not support nested transactions and
since saveAll creates a transaction by default, saveAll cannot be used
in my transactional save. Each Mixeval, MixevalQuestion, and
MixevalQuestionDesc has to be saved individually with a regular model
save call.

It would've been nice to have the likert marks distributed properly but
since that doesn't impact functionality, it was pushed back later.

Note that likert questions right now is more of a generic template for
other questions that might need to save descriptors too, e.g.: multiple
choice. Haven't figured out how to nicely abstract the shared qualities
of these questions while having the ability to customize.

It would be nice to be able to decare questions as "Master" like in
surveys, allowing you to load them into an evaluation. But that is for
later too.
Fix test cases broken by previous mixeval commits

Most of it just changes to how data is accessed.

One of it is a missing method in the mixeval model that used to be to
provided by it's parent class (evaluation_base).