Firstly, thanks to all of you who have filed feature requests or flagged up bugs on our bug tracker, your feedback has been really useful.

After thinking about how to best accommodate your needs we’ve deciding to do a rewrite of some of the internal Mendeley code in order to get it running snappier and work better with larger libraries.

As a result of some work Fred has done on his music player we’ve decided that using Qt’s MVC framework maps extremely well to our needs and should bring us far greater performance when dealing with large libraries as well as keeping the code cleaner, better separated and making it much easier to write unit tests with decent coverage levels.

So where are we with this at the moment? Currently we have implemented most of the new non-GUI code with just our local/remote database code to finish. For those interested in this sort of thing, we are 100% documented with Doxygen (both private and public members) and have every class’s method unit-tested with around 85% test coverage.

Without revealing too much you should be excited about this and some of the new features that will see the light of day around the same time as the new, better-performing internal code. This will hopefully mean we can feasible support much larger collections than currently with a slimmer/faster application and quicker bug turnaround with less regressions than our previous releases.

Get excited, I am! 😀