LimeWire 3.6.6 Beta

[afisk]

We've just released what we hope is the final beta in the 3.6.x series. This version adds a change to how we return search results -- hosts will now only return results if they have open upload slots. We used to return results if you had upload slots *or* open queue slots, but the new system should ensure that more search results work as expected due to fewer hosts being busy. This change also allows us to improve performance significantly, especially for big sharers.

This version also adds a file on OS X where users had problems with too many files being open at one time. The default limit for open files on OS X is 256, which is significantly lower than for other operating systems. So, with 3.6.6, we will now override this setting. Thanks to Jens-Uwe Mager (once again) for his contributions to this code, and special thanks to Greg Guerin from the Apple Java developer mailing list.

Finally, 3.6.6 adds a new pro-only theme with a special LimeWire Pro splash screen and LimeWire icon within the application.

That's about it for the new changes. Thanks for everyone's help!

-LimeWire Team

[jum]

The pro only theme appears only in the themes subdirectory, not in the themes.jar that is found in gui/lib. Was that file forgotten to update?

By the way, why is that info duplicated in the cvs tree? As one can see, it can go out of sync. If it were only once in cvs, it could not go out of sync.

[afisk]

Hi Jens-

We build the installers dynamically using the themes directory in CVS, so I was really only worrying about the released version yesterday, not the CVS version. The files are duplicated simply because I didn't want to force everyone to unjar the themes.jar file each time if they wanted to look at a specific file. On the other side, I didn't want to have to customize the code too much to handle CVS themes -- I preferred to just have it open the themes.jar file just like it does for installed versions.

I don't feel strongly about it in any case, but that was the thinking behind the current structure.

[jum]

I was just wondering about the difference. I personally prefer to not store any build results in CVS at all, just the sources to generate them with the apropriate build instructions in the form of build.xml files.

[afisk]

We could definitely do it this way -- check to see if the themes.jar file already exists each time build it dynamically if it's not there. I agree that technique is a little cleaner. I don't feel strongly about it at all, but I'd of course be more than happy to integrate a build.xml patch if you really would like it to change =). I guess to me it's an issue that comes up so rarely that I'm not that concerned with it.

[spearson]

Adam,

I just downloaded the new version of LimeWire Pro v3.6.6 from my download page. I think the new version is great. I have two questions. I noticed that the icon for Mac OS 9x is the same? Does this mean that the Mac OS X version of LimeWire gets the new icon? Also when I went to the download page for the basic version of LimeWire it took me to a different page and there was no place to download it. Are you just offering the Pro version now? I think this is about it. Thanks to Adam and the rest of the LimeWire Team for all you do you make LimeWire so great.

[afisk]

Hi LimeDude-

The way the pro theme works is a little quirky. By default, LimeWire will always open to whatever theme you had previously set. Since the LimeWire Pro theme is a new theme, it will not automatically open to this theme if you had another theme previously selected. To use the pro theme, you have to select it in the View>>Themes menu.

The download page should be all set -- we still offer both the Pro and the Basic versions.

Thanks.

[spearson]

Hi Adam,

I had already changed the theme I had before to the new LimeWire Pro theme. But the LimeWire icon is still the same. Any ideas? Thanks.