Sooo, I implemented the two tickets noted as missing in my last blog entry. Since all that’s left now is waiting on other SoC students, I had to move to something else. My branch was merged into trunk (the main development tree for svn-impaired), which should help adaption and testing.

If anybody reading this is using XMPP frequently, likes living on the edge and writing bug reports, please check out the latest development version of Adium, compile it and use it for a while! If you encounter any bugs or have suggestions, take a look at ReportingBugs. Any input in valuable! If your ticket concerns XMPP, please assign it to “am” (myself), so I get a notification for it.

EDIT: We get a discount on our per-ticket-fees on trac, so please open one separate ticket per request! We can afford that. Thank you for the valuable input I’ve received so far!

I mentioned previously that we had added a defaults key to allow you to be notified of beta builds from within Adium release builds.

I lied. Due to an oversight, it doesn’t work in 1.0.5. We’ll fix it for the next release… but until then, keep your eyes peeled for Adium 1.1 beta, coming soon to an Adium blog near you.

So for since the dawn of time, man has always wondered “How do the Adium Developers create the Adium changelogs?!”

I will tell you, with pictures, and with words. First, a picture:

We typically use SubEthaEdit to do our changelogs. It’s a bunch of fun. In the end we always end up with a multicolored bit of things here and there, and a few laughs.

I hope everyone likes the image. That’s the 1.1 changelog (in mid edit).

We’re happy to announce that Adium 1.0.5 is now available for download.

This last planned release of the 1.0.x series fixes a big handful of bugs and so is a recommended download for all Adium 1.0 users. Adium 1.1, the next major release which has been in development for the past year, will drop OS X 10.3 support, targeting OS X 10.4+ so we can bring you more of the shiny.

The most notable changes of Adium 1.0.5 include that problems with the chat transcript viewer incorrectly re-indexing transcripts have been fixed, login credentials for systemwide proxy servers are now read properly, and we’ve updated to libpurple 2.0.2. Also, AdiumLibpurplePlugins, which can let Adium make use of libpurple protocol plugins previously usable only in Pidgin, will now install properly, good news for users interested in adding Tlen support to Adium. See the Version History for the full scoop.

Thanks as always for the continued support of our excellent site and code host NetworkRedux and our download host Cachefly!

Get involved in open source development! See Contributing To Adium for information on helping out in general, contributing code, and donating. 🙂

Hello,

This is Andre Cohen, one of the SoC students working on Adium. I have this summer been extending the contact list’s functionality to allow groups to be detachable. As it has been seen here a lot of progress has been made. Groups can easily be detached, moved and organized in which ever way one prefers. As of two weeks ago the project became stable enough for everyday use.

Currently I have been working on smoothing out the experience. This includes:

• Adding/perfecting options in the view and window menu
• Making sure it is clear to the user when a groups are attached to each other or if they simply are next to each other
• Fixing or perhaps revising the way contact lists hide on the edge of the screen (thus fixing a currently very interesting bug)

This project has been going very well. Having started a bit early on the project it is allowing me to take more time to make sure everything functions smoothly. More updates to come!

PS: Since this project is entirely focused on user interaction I look forward to hearing about concerns and/or suggestions about this project.

Hi,

It’s been a while since my last update, so I’d like to list what I’ve implemented so far. Since mid-eval is up pretty soon, I’ll need it anyways 🙂

• The new registration interface (I already posted screenshots for it on this blog).
• A small lock is shown next to connected accounts that use SSL/TLS encryption.
• Integrated a fully-features discovery browser for accessing all the nice remote features. This also allows listing MUC channels and joining them (screenshot).
• Implemented Ad-Hoc commands, both sending and receiving.
• Implemented these commands into the discovery browser (screenshot). The server’s ad-hoc commands are shown in the account submenu (as demonstrated in this image), too. If any contact on the contact list has some ad-hoc commands available, they’re listed in their context menu (this is untested due to some non-Adium bugs).
• Implemented displaying search results using the libpurple API. This will also benefit the other libpurple protocols.
• Implemented MSN/Yahoo!-style buzz/nudge-support, including writing up a proposal for a XEP for it
• Implemented XEP-0115: Entity Capabilities (version 1.3; I accidentally started a huge discussion on the xmpp-standards list to completely rewrite it after I implemented it)
• Implemented XEP-0203: Delayed Delivery, which was very simple.
• Automatic accept / accept+add / deny of subscription requests (called “Request for Authorization” in Adium I think)

The major parts still missing are:

• The ad-hoc receiving part is planned to be used by AppleScript, so you can add custom AppleScripts to the list to be executed by clients connected to the same account (different resource), even with forms for interaction. This depends on Matthew Handley implementing the AS-part, though.
• Multiuser-Chat enhancements. For this feature I’ll probably don’t have to do anything, since Erik Beerepoot agreed to add the connection between his work and libpurple itself, which should automagically make it work with XMPP (libpurple already implements all features I’d like to have added to Adium).
• #1323
• #4695

I’m well within my time plan, so the project is looking good so far.

Hi,

My name is Erik Beerepoot, i’m another SoC student here at Adium.

Although a bit on the late side perhaps, here’s an update on group chat improvements. As you can read on Google’s SoC page, I proposed to do several improvements on the current implementation of group chat. As coding has been going on for a little over a month now, some of this features have been implemented, and are waiting on dev feedback.

So far, I’ve updated the group chat interface, I’ve changed to old userlist and added a so-called widget bar. A planned feature for this bar is room commands; but for now, it just looks pretty.

I’ve also added drag & drop support to group chats. It is now possible to drag a contact from the contact list to a group chat, and the contact will join the group chat. I’m planning on adding sorting capabilities to the userlist (just like in the contact list), and also making this drag possible for turning a single user chat into a group chat.

Right now, I’m working on adding room/server bookmarking to adium. It is currently being discussed what exactly the proper graphical representation will be.

This is all for now, but i’ll have updates to follow soon!

Hey folks,

Just a little heads up about the recent downtime. I didn’t post earlier because, well, this blog was down.

We’ve just finished the move of a couple of the services utilized for Adium to a heftier box at a much nicer datacenter at Network Redux. For those who have noticed, we’ve had outages on and off for months. The server was up, the problem was entirely the fault of the datacenter at the time. This move should correct that problem.

Some things are needing to be done still, but most of everything is back up.

Hello. This is Matt, a SoCoder working on improving Adium’s AppleScript support.

I’ve created a page on the wiki here: FixAndExpandAppleScriptSupport

It contains an incomplete list of features that I’m planning on, or already have implemented. If any scripters out there would like to add their input to the design, now would be a good time. I’m interested in any high-level critique of the design as it is now, as well as any suggestions for features I need to include.

Thanks so much!

– Matt

Hi again,

Since there has been some confusion among libpurple developers on how the new registration I added to Adium works, I’ve created some screenshots that might be of interest to others, too:

1. Creating a new account is unchanged, of course.
2. This is the slightly modified account pane. Note the “Register New Account” button there.
3. After clicking that button, a new view comes up, which allows you to either enter your own server to register to, or choose one from the list (the list is automatically fetched from xmpp.net). The numbers on the right display the geographical distance to that server in km, I’m not sure yet if I should display that. The list is ordered by that number.
4. I’m entering my own testserver of my local LAN, though. You won’t be able to reach that one 🙂
5. After clicking “Request New Account”, the view switches back to the regular account pane and Adium (via libpurple of course) connects to that server and requests the registration form and displays it. This form view isn’t final, I have to work on that some more to get it to look more Mac OS X-like.
6. I’m entering the data for a new test account.
7. Registration successful! Note that the values have been filled in automatically in the account editor. The account itself hasn’t been created yet, though. This will only be the case when the user presses “OK” in that window.

I hope that this will solve the confusion, and why I need those code changes 🙂