Friday, 4 December 2009

Class Test Class

A Teacher should be able to create a test with a group of problems or exercises. I have thought some about that, and it looks like we can solve it in a nice way with our current inheritance-approach. If we let our test implement the ExerciseClass, we can use and acces it just like any other exercise from the sidebara-menu.
A standard exercise takes a string as a setting argument, so if we let our test take a comma-separated string as input with class-names and setting-strings, we can create exercise instances within our test. A nice way to do this would be with dynamic class loading, Reflection, but that is not fully compatible with GWT.. and there is some drawbacks too. Dynamic classloading would probably decrease the code modifications to zero when new exercise-classes is to be added. We will have to solve the problem in a more static way, but with a nice code-layout it should be very clear where to manually add code for new exercises.

A test displays its exercises one at a time, stores the results from the individual exercises and uploads a testresult once the test is completed. A simple 'exercise' can be used to generate parameters for tests.

An idea that I want to think more of, is that all settings and statistic functionalities should be accessed like exercises, and the type of the user should determine which options that show up in the sidebar. Admins should see statistics and settings, teachers should see test generators and users should only see the exercises.
This way of constructing the site is similar to how facebook is built up, just a shell with applications for everything but the basic functionallities. The users decides what applications to see and use.

No comments:

Post a Comment