{"id":628,"date":"2014-10-07T10:35:17","date_gmt":"2014-10-07T10:35:17","guid":{"rendered":"http:\/\/www.numbas.org.uk\/?p=628"},"modified":"2014-10-07T10:35:17","modified_gmt":"2014-10-07T10:35:17","slug":"development-log-september-2014","status":"publish","type":"post","link":"https:\/\/www.numbas.org.uk\/theme-testing\/blog\/2014\/10\/development-log-september-2014\/","title":{"rendered":"Development log – September 2014"},"content":{"rendered":"

Here’s another round-up of the development work on Numbas in the past month-and-a-bit.<\/p>\n

A little attribution<\/h3>\n

I’ve added a small attribution footer to the bottom of the default theme. It looks like this:<\/p>\n

\"created<\/p>\n

Now that people can upload their own themes, we wanted an unobtrusive way of noting that tests are built using Numbas. If you don’t want it there, you can use a modified theme to remove it, but we’d prefer you kept it.<\/p>\n

Better error messages<\/h3>\n

I’ve spent some time looking at the ways Numbas tests can fail, with the aim of giving better information about what’s gone wrong. The biggest change is that errors encountered while the exam is loading now show a more helpful screen than the old pop-up message:<\/p>\n

\"numbas<\/p>\n

And if you click on the error message, you get a JavaScript stack trace:<\/p>\n

\"numbas<\/p>\n

I’ve worked on making the messages themselves more helpful, as well. Errors caused by a particular question will tell you which question they came from, so it’s easier to work out where to look. Numbas now catches a lot more errors encountered while resuming SCORM sessions – missing or mismatched data will cause an immediate error, instead of being ignored until it causes something else to fail. A common error is caused by variables not being defined – instead of cryptic messages like “no definition of ‘+’ of right type found” when one of the operands is an undefined variable, the error now says “Variable <name> not defined”.<\/p>\n

Faster question search<\/h3>\n

The search page in the question editor is now a lot faster. Now that we have over 4,000 questions in the public database, it was taking a long time to filter the whole question set. I’ve rewritten the database queries so it takes just a few milliseconds to do the same thing.<\/p>\n

Other changes<\/h3>\n

Here are the rest of the changes made to Numbas in the last month or so:<\/p>\n