Shareaza

I suggest to add a line to our update notification popup informing the user about the ability of his CPU to run the SSE2 optimized version of Shareaza. Like this, more users might run the more optimal version of Shareaza.

Also, there should be a second magnet link on our download page pointing to the SSE2 build.

As most of the CPUs out there do support SSE2, I'd like to also suggest to make the SSE2 optimized build our default download on the download page.

Please post performance comparisons or why it matters.

It matters because we do currently offer both versions, and so users should use the better one if possible, even if the performance gain were really small.

Well, now that v2.5.4.0 is out, could you at least place the link for the SSE2 optimized build above the one to the normal one and make both build types available via magnet instead of only one of them?

Well, for some reason, Ryo didn't even commit the SSE2 version...

Because of I have no change log, news post, web article etc. for new version.

You could have simply asked us for that stuff... We didn't even know you planned on releasing the new version...

I really want to help you Ryo, but if you always act without noticing anyone about what you intend to do, it's not likely when a new version comes out, such stuff is ready right away...


Anyway, I'll set up a change log on the Wiki.


mfg,
Old

Here you go: https://sourceforge.net/apps/mediawiki/ ... geLog2.5.4

If it's out of the oven but not yet served, so to speak, and in particular given that the front page of the site has not changed, then how precisely did old_death know about it?

I have the sneaking suspicion now of an inner circle that is privy to things before even us beta testers...

Nope. Have a look at this page: http://cia.vc/stats/project/shareaza
If you subscribe to this RSS feed, you are informed almost instantly over all code changes, which includes changes that announce a new version.


mfg,
Old

Does the auto-update use a P2P download? If it does we really should look into getting a smart installer that contains both versions and installs the correct one automatically. Or has a simple launcher that detects the system and executes the correct executable. If you store the alternate versions as patches it should not change the filesize that much and would keep the number of sources from fragmenting.

Also, we should not include the plugins in the installer any more. They can be downloaded automatically by Shareaza itself on first run.

Hey, I got 2 crashes since upgrading to the debug build of the new version. I take back any requests for updating our home page and do suggest we fix those first and release a version without them to the public. Both of these crashes have happened in during operation in Hub mode and uploading a torrent, so that's a place where testing could start.

Well, if you sent the bug report ryo should already know about it... But I've been thinking that a slight delay between the new version and pushing it to users is not really that bad a thing. It might even be good to do it on purpose the next time.

That's strange. Since I switched over from the x64 version to the x86 version of the debug build again, the crashes are gone. I suppose this has to do with the library updates done a week ago. Maybe there is something still not 64 bit compatible in there...

Or there might be a problem with your x64 system... Something like not having the correct version of the Visual C runtimes. The dependencies for x86 and x64 have to be updated and maintained separately which is why the "lazy person" (me... *sigh*) prefers using 32 bit applications.