s o u l s e e X
I put up a new build in the builds directory that fixes the crashes on Intel Macs. Also completely redid the way tooltips were done which surprisingly I figured out was the cause of most of the performance problems. This version should run like a gajillion times faster (yes, exactly that much). The one catch is tool tips are now Tiger only, sorry Panther users but no little yellow boxes for you (blame Apple for not having a tool tip api for table views until Tiger, not me).
Download here: ssX-04292006-2118.dmg
Note: Saved searches do NOT work yet, so no need to ask about them.An update as this is getting out of hand. This project is not dead it's just moving slowly at the moment. For those who don't know I was hired by Soulseek to be their sys-admin and also to do some work on a windows client. That's been a lot of work to say the least, so this has been lowered in priority as basically it works pretty well for most people and there aren't any major pressing issues with it. Anyway I am currently working on getting a wishlist feature done and hope to have something in the nightly builds in the next few weeks to a month (there I said it now I have to do it). Once wishlist is in I will most likely call this version 1.0. Then I have this strong urge to start completely over from scratch and make ssX2. Patience is a virtue.
ssX is being searched by other users again. It's the only 3rd party client on the trusted list so if you are coming from Nicotine or others don't be surprised when your upload queues are much bigger on ssX, it's not a bug it's a feature. Now let the moaning about cpu usage begin!
Note: If you are using a version of ssX older than 1.0b6 you will not be searched. Upgrade if you haven't.
I just put up a version thats been recompiled as a universal Power PC and Intel binary. I have no way to know if it works on Intel though as I don't have access to an osx-x86 box. If anybody who does wants to comment on if it works natively or at all I'd love to hear it. I don't know what the NDA is like for the x86 developer program but if it is too restrictive to say even that in public maybe you could email me privately (address is in the readme) and just say minimally if it works at all. I am really curious mainly because the slsk protocol stuff relies heavily on endian translations and I want to make sure I got it right. The new build is here: ssX-08212005-2128.dmg.
Also any panther users that comment would be appreciated, as I haven't reinstalled it as my secondary OS to check if anything broke there yet.