Interestingly, postings which include screenshots seem to gather several times more comments than those without. So here's another screenshot for you screenshot-hungry people :)

As discussed before, the top-right corner will become statistics graph (hopefully should have implementation of that by designer within few days). The bottom part will display module info/overview, but the backend is currently missing, since the time went to implement the network-statistics related core/gui comm protocol parts.
Statistics-fans shouldn't be alarmed about the small space the statistics got in the interface. Thanks to the tab-based approach, we can introduce a separate tab on the Home page which opens on-demand by double-clicking on the graph, or some button, and can display pagefuls of statistics data. This approach avoids cluttering the interface with data the average user isn't interested in, but provides the data for the
"mythical power user".
Due to the VS2005 iostreams library memory leak issue, previously mentioned
here, the r2805 win32 builds are built with mingw compiler. We'll have to see what to do with the VS2005 problems; one option would be to use STLPort library instead of the VS2005 STL implementation; other would be to patch the issue and rebuild the dlls; frankly, I don't like either approach, but it seems there are no other options.
I've been experimenting somewhat with a layout change, which will affect transfer and library pages. Namely, I'm trying to get rid of the 'action toolbar' (clear/pause/resume/stop buttons), and move those buttons to top-right corner, on same row as the tabs. This has several reasons - gain of ~20px in height (less scrolling and cleaner look), move less-used functionality away from primary location (most p2p users are more accustomed to using right-click menu for those operations), and balance the interface visually (left/right). Initially, it seemed this would require a lot of manual layouting, including taking apart the QTabWidgets and recomposing them manually from QTabBar and whatever they use additionally. However, it turned out QTabWidget has a function,
setCornerWidget(QWidget *w), which allows doing exactly what we need. The trouble began when I attempted to put there a larger widget (actually, composite widget) - namely, the space seemed to be limited to ~50px width. So far my attempts of tweaking it have been only partially successful, as can be seen from screenshots below.



New builds from r2805 are up for Windows and Linux, as well as source snapshot in three formats.
Madcat, ZzZz