Creating it is very simple. First, we need to setup a file structure.  Create a folder called whatshesaid.AdiumScripts.  Then right click(CTLR+click), and click ’show package contents.’  Create a folder called Contents.  Inside Contents, create a folder called Resources.  The result:

->whatshesaid.AdiumScripts
–>Contents
—->Resources

The next step is to create the actual script.  Enter the Resources folder.  Open up the Script Editor from the Applications folder.  If this is not installed, then just be prepared to save a file using the .scpt extension.  Create a function like this:

The on substitute() function will be called every time the script is used.  Inside is an array of strings seperated by commas.   Now the question is, how do we use the script?

Go up one level back to the Contents folder.  Click HERE and drag the info.plist file into the directory.  If you changed any of the defaults, make the appropriate changes.

And that’s it.  Just click on the random.AdiumScripts icon and it should install. Type /she or %_she in a chatbox to test the script. That’s the simplest way to do it. There are some other XML properties that can be added but aren’t necessary for personal use. If you plan on publishing on Adium’s website, be sure to add any and all public standards.

You can add more substitutions by creating more script files and more entries into the XML tree. You can also edit the triggers by changing /she to any character sequence.

Your files will be installed in Library/Application Support/Adium 2.0/Scripts

The best way to learn these concepts is to open up one.  That is just what I did.  I found a script that formatted iTunes data.  I was not satisfied with all of its features so I modified it.  I left credit to the original authors in the modified script.

First, we need to create a file structure.  Create a folder called name.AdiumScripts.  name can be anything you like, just make sure you don’t forget it.  Then right click(CTLR+click), and click ’show package contents.’  Create a folder called Contents.  Inside Contents, create a folder called Resources.  The result:

->name.AdiumScripts
–>Contents
—->Resources

Enter the contents folder. Click HERE for the info.plist file that will direct Adium where to get your script.  Place it in the contents folder.

The following is how the file looks:

name corresponds to the name of your project from earlier.  Under <key>File</key>, we specify the name of the script file that will be called each time %_name {default_message} is called.  Of course, you can change any of these.  It is also possible to create more callable scripts by copying and pasting. {default_message} will be displayed with the track information or if iTunes is not playing. This is required to run the script.

Now enter the Resources folder.  Create a file called name, or whatever you may have changed name to, with the file extension .scpt. You can either use your favorite text editor or the Script Editor.  This is where we will create our actual script that displays the data.

The following script has the following sample output:

Reading and listening to You Are The Pan
By John Williams
From Hook (Original Motion Picture Soundtrack).

The first line is shows my default action combined with the current song name.  The next lines are the artist, and the album.  If iTunes is not active, whether it is paused or not open, the default action will appear. This output is produced by typing: %_name {Reading}The modified script can be found by clicking HERE.

The code is pretty simple to follow so I won’t go into details here.  It is very simple to add more formatting.  It is just a matter of copying and pasting.  The column names found in iTunes are pretty much the same as they are in AppleScript e.g. to access the genre of a track, just use the variable genre.  Adding more substitutions, that is adding more features like %_name, is as simple as expanding the XML tree and placing the new script files in the same directory.

Like always, if you plan on creating a published add-on, be sure to adhere to any current standards. And that’s it. Just click on name.AdiumScripts to install.

Your files will be installed in Library/Application Support/Adium 2.0/Scripts

In this example, we are only going to create one new emoticon.  The process can be duplicated easily by copying and pasting.  To start, create a folder called Name.adiumemoticonset.  The name doesn’t really matter as long as you remember it later.  Right click(CTLR+click) on your new folder, it should be a smiley face, and click ‘Show Package Contents.’ Open up the Property List Editor to create a .plist file. Name this file Emoticons.plist.

Click HERE for a shell of the .plist file.

That is all there is too customizing your own Adium “smiley set”.  Yourpic.png is the element that controls which picture is called when the proper emoticon appears.  In this case, the emoticon :) , most know it as , will cause Yourpic.png to show up.  You can assign any number of emoticons to a particular picture by adding more nodes under Equivalents.  Just copy and paste for more elements.

Yourpic.png, and any other .pngs, are stored in the same directory as Emoticons.plist.  All of them are stored in the main directory of the package.  Most .png files are around (19-21)x(19-21).  You don’t have to conform to the size limits but you might not want large files crowding your chat window. Also note, the emoticons only appear on your end, so whomever you are talking with will only see their representation of :) and not Yourpic.png.

Your files will be installed in Library/Application Support/Adium 2.0/Emoticons

One of the easiest ways to learn how to create an Adium script is to open up an exisiting script and look at how it works.  Easy enough.  First, we need to setup a file structure.  Create a folder called random.AdiumScripts.  Then right click(CTLR+click), and click ’show package contents.’  Create a folder called Contents.  Inside Contents, create a folder called Resources.  The result:

->random.AdiumScripts
–>Contents
—->Resources

The next step is to create the actual script.  Enter the Resources folder.  Open up the Script Editor from the Applications folder.  If this is not installed, then just be prepared to save a file using the .scpt extension.  Create a function like this:

The on substitute() function will be called every time the script is used.  Inside is an array of strings seperated by commas.  usethis is assigned to some random string inside the array and returned to Adium.  Now the question is, how do we use the script?

Go up one level back to the Contents folder.  Click HERE and drag the info.plist file into the directory.  If you changed any of the defaults, make the appropriate changes.

And that’s it.  Just click on the random.AdiumScripts icon and it should install. Type /random in a chatbox to test the script. That’s the simplest way to do it. There are some other XML properties that can be added but aren’t necessary for personal use. If you plan on publishing on Adium’s website, be sure to add any and all public standards.

You can add more substitutions by creating more script files and more entries into the XML tree. You can also edit the triggers by changing /random to any character sequence.

Your files will be installed in Library/Application Support/Adium 2.0/Scripts