Thanks everyone for voting on the protocols thread. I should have some results later on this week. Please keep in mind that the poll did not mean much, I just wanted to get a general idea of what everyone uses.

10.3.2 is out and updates a number of system frameworks. If you’re building Adium from source, it’s a good idea to open console and run:

sudo fixprecomps -force -all

This will stop any pre-compiled symbol warnings and should keep your compile times fast.

We had a bad binary go up this morning.

Anyone who downloaded before 9:00 AM EST (And is not seeing aliases on their contact list) should download again.

A new binary is up now and should be all good 🙂

I’ve revamped the object specific preference system. This means that plugins can now easily add preferences specific to an individual contact (or all the contacts within a specific group). The contact alerts already had a system for this, but the support is now in Adium’s core and easier to access 🙂

I’ve added some temporary code to upgrade your preferences to the new system as they’re read. Don’t be alarmed if some contact-specific preferences are lost, however (aka. Aliases, Contact alerts, and custom voice settings). Sorry for the inconvenience.

There are three types of bugs a user can run up against in Adium:

– Logic flaws (Mistakes in our logic, where we’ve told Adium to behave incorrectly)

– Exceptions (Small mistakes that Adium catches while running)

– Unexpected quits (Mistakes or errors that Adium is unable to recover from)

Currently, when the user encounters an exception, Adium aborts the particular task it was on and attempts to keep going. While this may sound like a good thing, skipping code that was intended to run can cause some very strange behavior later. What’s worse is that the user often doesn’t realize they’ve encountered an error. (This is what we’re looking for when we tell you to ‘check console.app’).

Unexpected quits let the user know something went wrong, and even generate a log to let us know more information about the crash. Unfortunately, fetching these logs and emailing them to us is a pain. Making things more complicated is Apple’s ‘crash submit’ dialog which prompts the user to send Apple a crash report. We don’t get reports sent to Apple, and this may trick users into thinking they’ve reported a crash to us.

We are working on code to simplify the process of sending us Adium’s crash logs. We are also working on code to generate and send helpful logs when there is an exception.

This is really exciting for us, because it will result in much more crash/exception reports and ultimately lead to a much stabler Adium. More details will emerge as we have them. 🙂

I’ve removed the avatars from the binary – We weren’t using them and they’re kinda big 🙂

Tomorrow’s binary should be a smaller download.

AdamIser:”This change touches a lot of files.”

Hm. ~Well they say the sky’s the limit, and to me that’s really true, but my friend you have seen nothing, just wait ’til I get through, because I’m bad, I’m bad, come on…~

Everybody, keep an eye out for new crashes and bugs in today’s binary. I touched a lot of files yesterday, and odds are that I made a mistake or two somewhere 🙂

[Known Bug(s) : Already fixed]

– Issues with contact alerts (Empty action menus, assertions)

The LaTeX plugin is working again, thanks to max_cohen (Stephen Poprocki). To use it, you need a working pdflatex binary and Equation Service. You can get both from http://www.rna.nl/tex.html.

If you don’t know what it does, it typesets mathematics beautifully, creating integral signs and such.

Adium is aqua again.

Give it a week or so and then let us know what you think 🙂