This is the innotop roadmap.  Don't hold me to it, it's just my plan :-)
There are no dates because I work on this in my spare time.

IF YOU WANT A FEATURE SOONER, please ask me about it!  These are my
priorities, but I'm flexible.

A note on version numbers: odd-numbered versions are development,
even-numbered are stable.

Features for version 1.6:

* Quick-filters: easy-to-create filters applied to columns.  They are not
  persisted to the configuration file.  They can only be added, cannot be
  edited, and can only be cleared all at once, not singly.  The '/' key
  triggers adding a new filter, and the - key clears them all.
* Accept command-line parameters to control unattended operation.
   * Run a specified number of times and exit.
   * Run once and exit.  This would actually need to "do the right thing"
     depending on whether innotop is in incremental operation -- if so, it has
     to actually run for two clock ticks before it can output any data.
* Read InnoDB Status Monitor data from a file instead of fetching from a DB.
* Add a mode to display current locks from innodb_lock_monitor.
* Add a command summary mode like mytop's c mode.
* Support aggregation across servers.
* Plugins to add columns and/or key mappings.

Features for version 1.8:

* A test suite.
* Rename the variables the InnoDB parser outputs to match what MySQL has named them.
  http://dev.mysql.com/doc/refman/5.0/en/server-status-variables.html#option_mysqld_Innodb_buffer_pool_pages_data
* Support Google's patches:
  http://code.google.com/p/google-mysql-tools/wiki/InnodbStatus
  http://dammit.lt/2007/06/23/mysql-40-google-edition/
* Make InnoDBParser.pm smartly fill in the data it needs by looking in SHOW
  STATUS and SHOW VARIABLES and realizing if these already provide necessary
  data.
* Efficiency and speed optimizations.  Only fetch needed data from servers.
* Use SQL instead of all the extract_values stuff.
* New configuration screen with less duplicate code that plugins can add to.
* Add support for Falcon and solidDB.
* Support multiple server connections in all modes.
* Support incremental display in all modes.  Make incremental display a per-mode
  configuration setting.
* Tentative: Add a new mode for monitoring NDB clusters.
* Tentative: usability testing and if necessary, make usability enhancements.
* Tentative: Add support for pager if you want to see more than fits on screen.
* Tentative: Documentation and built-in help (get help on a key from help screen).

Features for version 2.0:

* Introduce multi-threading for getting data from many servers.
* Code cleanup.
* Documentation.

Future features:
* Merge InnoDB transactions and PROCESSLIST so one can see, for example, how
  long a transaction has been open but idle.
* Support more storage engines as needed: PBXT, Falcon, solidDB etc.
* Check online for a newer version of innotop and alert for possible upgrades.
* Add a mode to 'watch' a particular connection.  This would try to collect
  query history on this connection and display each query with as much
  statistics as available on it, such as start and finish time.
* Work on usability and learnability, especially as regards managing one or
  many servers.  For example, if you only have one server, the cxn should not
  show up in any displays.