See the Changelog for list of features and fixes.
On trying to port the client to Mac
I've done almost nothing in the last few days except see how far I can get trying to port SoulseekQT to a Mac environment. I don't have a Mac, but a long while ago I managed to get Snow Leopard running in Virtual Box, and seeing as Qt had been ported to the Mac along with its accompanying development environment, Qt creator, it seemed as if my chances were pretty good. It took me a while to find my way back to a virtualized Mac desktop, requiring that I fool around with various VM settings and legacy loaders, and when I finally got there, Qt Creator emerged as all but unusable for my purposes. Anything as slight as trying to open a source file in the environment's editor would bring it to its knees. Debugging was completely out of the question. My prospects might have been better with the newly released Qt SDK 1.1 beta, but my box would not run a 64-bit program, and trying to force Snow Leopard into 64-bit mode was not getting me anywhere. Finally I had noticed that the Qt Creator portion of the 1.1 beta was being offered in standalone form, and in 32-bit to add. Until then I had no idea whether the gross instabilities I was experiencing were to blame on virtualization or on the current release version of Qt Creator. It seemed unlikely that the latter would be offered as current if that were the case. My doubts were laid to rest, there was nothing wrong with my virtual machine. Everything was now working properly.
Code incompatibilities were not plentiful, but I did have to pay special attention to anything that had to do with file paths, as the FreeBSD based Snow Leopard uses slashes to separate folder names as opposed to backslashes on Windows. I did enough to see that I could download files and folders off of search results, but I wouldn't expect anything else that's file-related to work. File sharing and uploading seems completely out of the question at this point, although I haven't even tried. It seems a bit wasteful to try to provide a perfect port of something that's as imperfect as it is in its current form. Also, Mac debugging is still a bit finicky and very, very slow in my virtual box, so I'm not sure how well I'd be able to perfect any future ports if any platform specific issues arise. While it seems impractical to try and provide a Mac port with every build I produce for Windows, I'm going to try and offer them for major developments. I tried running the compiled application in a clean, second virtual machine just to see if it would work properly off the bat. It doesn't exactly. I don't know how to bundle the required libraries, so you'll have to install the Qt SDK to get it to work, link provided below. It also has a really ugly default icon right now. Sorry!