AIM Now (Mostly) Open To Developers
gregsblog writes "Today is a historic day at AOL as we announced a software development kit for AOL Instant Messenger. Open AIM will empower you, as the developer, to write custom clients and plugins.
For now, lets concentrate on the Open AIM SDK and get into what it can do for you. First, the development kit is written using COM, so plugins and custom clients can be written for Windows in languages like C++, VB, C#, and eventually J-Script. In the near future we will have solutions for LINUX, MAC and Windows Mobile devices. Why is this important? We now have a solution to provide all AIM users and consumers to build their own IM clients and to extend the features of Triton via plugins. Of course all of this is free of charge. How do I get started? Well my team has provided a quick start guide, and tutorials, in addition to numerous coding examples, from the simple to the complex. Our examples are in C++ and C#.
What are the limitations? Basically anything goes, with the exception of writing multi-headed clients."
Without advertising, how do they reach step 3?
... I mean, we've only been using Gaim for about five years now...
Real Daleks don't climb stairs - they level the building.
The overall effectiveness of this will of course be determined by the users who are writing their own clients/plugins. Your mileage may vary. However, I do see this as a positive step forward, if only in an academic sense. With a major company making such an effort to have their software available for community modification, with tutorials and examples, I'd have to say that this is a nice step away from the monoculture software development. Even if you can't get anything truly useful out of it, it is interesting to take a look at what is offered and see what you might be able to learn from it. Never hurts to experiment.
Randimal: AT-CG-CG-AT-CG-AT-AT-CG-CG-AT-AT-CG-AT-CG-CG-AT-CG-AT-AT-CG-AT-CG-CG-AT-AT-CG-CG-AT-CG-AT-AT-CG
"Developers are not permitted to build Custom Clients that are multi-headed or interoperable with any other IM network."
The definition of "almost, but not quite totally useless" seems more appropriate.
-Charles
Learning HOW to think is more important than learning WHAT to think.
From the Gaim Wikipedia article:
Recently, the Gaim developers have started to separate the core code--which handles things such as network connections and messaging--from the GUI code, which controls how these actions are presented to the user. After the code split is complete, it will be possible to write client programs using a developer's GUI library of choice. The core library produced by the split will be called libgaim; an in-development but stable version of this library is already in use in the Adium, Fire, and Proteus clients as well as the Meebo web-based application.
So, in other words, AOL are going to have something much more limited than libgaim (AIM protocol only) available in the "near future"? Uhhh... congratulations AOL! Now bugger off, you jerk-burgers!
We don't need no stinkin' SDKs.. why not officially document and open up the API instead? That way we can call it and do what we want on any platform without having to worry about SDKs.
Here come the AIM bots.
For the masses at large, this means you cannot use ANY GPLed code, or any code that causes you to redistribute your code freely.
This makes sense in the context of custom clients as you would be required to redistribute the client and the associated source code (which you cannot do because of closed source nature of the AOL libraries.) But as a consequence, it's worth paying attention to and will have some nasty effects on code reuse.