Hey guys,
I was afraid this day would come. Adium 1.3 beta was just released and it seems that Xblaze no longer works with it. I’ve been doing some initial digging and from what I can see, some things have changed in the plugin architecture which breaks some things in XBlaze.
The advice I’ll give for now is to not upgrade to 1.3 just yet. I’ll see what I can do about getting a fix out soon.
I, too, accidentally updated to the beta. I stuck with it and am currently running beta 6. Xblaze does not work as of beta 6. It hangs the program forcing me to go into Activity Monitor and terminate it. I am patiently waiting for a fix since my Windows machine is offline at the moment and I would love to chat with my Xfire buddies.
iMac G5
10.5.4
Adium beta6
If you’re quick, you can still download Adium 1.2.6 from adiumx.com
I’ve checked, and Xblaze still works with 1.2.6.
You should be able to just download and overwrite the beta version you’re using.
If you’re happy with Adium 1.3 beta 6 then you’ll just have to wait for a fix for Xblaze
How is the work going?
I don’t want to rush you, but at least some informations would be nice
Yeah um you have been ‘gone’ for a while… You still with us my friend?
We’re on beta 10 now, and it looks like whatever broke XBlaze in Adium 3 isn’t on their list of things to ‘fix’, probably because it isn’t specifically ‘broken’ to begin with.
Any update on the status of a fix on XBlaze’s end?
I’m really sorry guys! I’m still alive, and I’ve not been ignoring you, honestly. The things is that I’ve just graduated from Uni and I’ve been job hunting and dealing with all the things that comes with trying to get settled in life.
Also, Adium devs won’t need to ‘fix’ anything on their side - nothing is broken in that sense - it’s just that the current plugin version is using code that is compatible with 1.2, but not with the new code in 1.3. It’z Xblaze that’s broken, not Adium.
Unfortunately, as plugins go, they have to move swiftly to keep up - which is why Xflame is in development.
Does that mean, that development on xBlaze will stop? I wouldn’t find that very fair, because I (and much other people) really like xblaze and I don’t want have to open an extra program just for one protocol when I already have multiple protocols running in an other program.
Maybe you could make it open source, so that other people could continue working on it. (I would be interested!)
Heh. It is open source — Alas, I have the source. Nice and simple… If you can understand it.
My source it old though.
Well, 1.3 official is out. So how about giving us an xblaze for it?
I hope that the fact that everyone is now waiting with the old version of adium doesn’t mean that you are not really desperate to update xblaze… well, once i get macports running I guess i am going to switch to pidgin
September 9th, Adium 1.3.1 is out. any work being done on xblaze?