QTM's development road-map
Note: this page is hideously out of date. 0.7 was delivered in October 2008 and the latest release was 0.7.1.3, in January 2009. All of the other features mentioned here are up in the air, but a rich text interface and Markdown support in the Preview are in development.
Where is QTM going from here?
A couple of weeks ago I released what I intend to be the last minor release to the 0.5 series. Work has now begun (or rather, re-started) on the next big changes to QTM, which should lead to the 0.6 release. This is the feature roadmap for the next few releases of QTM:
0.6: April or May
As of mid-March, this release is to feature persistence in its lists of blogs and categories. Each time you change the account details, the blog list will remain on file until you change the details or refresh it manually; the category lists will behave similarly. This central feature is already in place; what I am working on now is consistency, so that QTM will not, for example, wipe all your details any time you load an entry which uses a different account.
0.7: July, I hope
Once the structure which supports persistance in 0.6 is in place, the next big feature, as requested recently, is multiple accounts.
These two features are what I consider "definite"; I actually need them myself, and the constant reloading of categories and blogs, while it keeps QTM up to date, can be annoying, particularly if you lose your internet connection.
I expect that version 0.8 will feature some means of retrieving entries from the server itself, so you can edit them in QTM and resubmit them, or delete them. Note that there is only so much you can edit and manage with QTM; monitoring comments for spam, for example, is not possible in QTM and will not be for the foreseeable future, because the methods for doing this vary from system to system (SpamLookup in MT, Akismet in Wordpress, for example).
Another recent feature request: compatibility with different blogging interfaces. The most important of these is Blogger, which has its own desktop client interface (called GData) which is entirely different from that used by Wordpress and Movable Type. Another new interface is Atom, which Movable Type can use (but it can also use the standard XML-RPC). To do this, a plugin system needs to be implemented for all functions which interact with your websites, rather than with you.