| commit | f3460297a962e2a3d07869a56241866576ffc7a3 | |
| author | Tim Hunt <T.J.Hunt@open.ac.uk> | |
| Thu, 9 Aug 2012 18:42:57 +0000 (9 19:42 +0100) | ||
| committer | Tim Hunt <T.J.Hunt@open.ac.uk> | |
| Fri, 4 Oct 2013 11:15:01 +0000 (4 12:15 +0100) | ||
| tree | bccfbc1651d9f0a569334bcb07af6a897ecbdd4e | treesnapshot (tar.gz zip) |
| parent | 56cc9b387ed095a18a6ee4df724dabf490f93df6 | commitdiff |
MDL-32188 question engine: behaviour static methods -> new classes
It was always a bit of a hack to use static methods on the
qbehaviour_whatever classes to return metadata about the behaviour. It
is better design to have real qbehaviour_whatever_type classes to report
that metadata, particularly now that we are planning to add more such.
For example, inheritance works better with real classes. See, for
example, the improvements in
question_engine::get_behaviour_unused_display_options().
This change has been implemented in a backwards-compatbile way. Old
behaviours will continue to work. There will just be some developer debug
output to prompt people to upgrade their code properly.
It was always a bit of a hack to use static methods on the
qbehaviour_whatever classes to return metadata about the behaviour. It
is better design to have real qbehaviour_whatever_type classes to report
that metadata, particularly now that we are planning to add more such.
For example, inheritance works better with real classes. See, for
example, the improvements in
question_engine::get_behaviour_unused_display_options().
This change has been implemented in a backwards-compatbile way. Old
behaviours will continue to work. There will just be some developer debug
output to prompt people to upgrade their code properly.
29 files changed: