In case you haven’t noticed, we now have access to CoreSuite.scriptSuite and TextSuite.scriptSuite. All I had to do was add:

<key>NSAppleScriptEnabled</key>

<value>true</value>

to Info.plist. You can now do basic stuff like opening up Adium, and… uh, well, I haven’t played around with it. But you can do stuff, that much I assure you. 😀

So text drag&drop onto the tabs works great now, but as I mentioned in my commit, I can’t get the AISendingTextView to resize properly when text is dropped on the tab (processed in the routine appendToTextEntryView in AIMessageViewController.m). It’s not a line ending issue, as cutting and pasting back in the same text works as expected. I post the same notification that, say, clearTextView does, and that doesn’t do it. I think it might need an [NSTextView edited: range: changeInLength:] call, but it throws an exception that doesn’t make any sense.

Someone, anyone, figure it out…

We’ve got emoticons now 🙂

Colin and I have changed the default status colors around a bit. If you want to see them, trash your Contact Status Coloring.plist file. Now typing is light blue, which turns into dark blue for unviewed content. A few minor changes to the other colors as well.

Well, it seems that my task isn’t so confusing after all. The reason OSA is only on the carbon side is that you implement the OSA components (the perl OSA component gives you system-wide perl support, the applescript OSA component gives you system wide applescript components) in Carbon.

You can use those other OSA components besides AppleScript by hooking on to the Apple Events, and then you just have a popup menu to select the language.

I’m torn about whether to have an In-Adium script editor, or to open Apple’s. If we use Apple’s, it would feel slightly hackish, but it’d be more “standard,” more “integrated” with the OS.

If we use an Inline editor though, we could do our own syntax highlighting, completions, and other neato tricks.

I’m always open to advice. I’ll make a long winded post when I come to a conclusion 😉

My contact info is on the contact page, as always.

Yup, leave the spaying and neutering to me 😀

After using a version of Adium equipped with the status labels in tabs for a while now, I’ve come to dislike them. Three complaints I have with regard to status labels on tabs:

• They’re very bold, gaudy, and clutter the tabs.

• They clash with the metal.

• They don’t work on the selected tab, and there’s no way to make this look good.

My plan is to regress a bit (no, not back to status circles… not regressing that far :-P), back to colored text. Now that we have embossing on the tabs, I know I can make colored text work. It’s looking great so far… hopefully I can finish and put the changes up tomorrow.

Well, all the cool kids are posting to-do lists.. why not?

• Clean up drag-and-drop on the tabs of text so that the tabs can accept a drop and the tab-switch doesn’t occur immediately

• Add a couple promised buddy alerts, including execution of an arbitrary application or script and selection of an arbitrary sound

• Eat dinner

• Add prefs for the contact list, the message window, and the dock so that any or all of them can have their BLINK tags permanently spayed or neutered. edit: or Adam can have that one. Colin said he’s already working on it.

Waah, OSA hooking looks so hard and confusing! *grumble grumble, sob sob* I’ve got a little help (thanks Paul! :-D), but it’s still tricky.

It’s got to be done though, so here’s the plan for now:

• Stall as long as possible.

• Seriously think about using a different scripting language, like Lua or Ferite.

• Try to delay by working on something else.

• Ask for help!

Yes, I’m asking you, users, to email me! Send me an email, tell me what you think about those crossed out options up there (especially number 2). If you happen to have experience, and want to help, IM or Email me, please 😛

I’m really not that desparate, but, help would be nice. I’ll manage on my own though.

My contact info is on the contact page (d’uh!)

Update: If I worked at this, I’m sure I could get it done. I’m not asking for pity, just good references and advice 😉

N.B. OSA is the Open Scripting Architecture, of which AppleScript is a Scripting Component. There are Scripting Components for everything from Perl to Ruby to shellscripting.

My current list of things to do:

• Track down a bug that causes the PostgreSQL backend to crash on first insert. It only seems to happen with OSCAR or MSN accounts, and could be related to the additional module I use for fast searching. Haven’t been able to reliably reproduce.
• Make Adium more gracefully handle said backend crash. Currently there’s no way to recover without quitting & restarting Adium, although all Adium-y actions work fine.




• Make a preference pane.

Edit: The night of homework was looking so good I got one done.

• Make an in-Adium log viewer, negating the need for the JSP/web stuff if it isn’t wanted. Initially would probably look very much like current log viewer, with a few additions. Part that worries me is the upper-right-hand pane (the distinct dates). That type of data isn’t what a database is designed for, and might be slow. It’s possible it won’t be too slow, and also possible that when PostgreSQL 7.4 comes out, the slowness will go away, due to new indexing capabilities.
• Improve documentation on performance and vacuuming.

If Colin has his way:

• Add a sort for most recently talked to
• Add a sort for most talked to

It appears I already have my hands full with the list mentioned previously 🙂

By the way, I’d like to thank Laura Natcher for the wonderful modifications to Adam Betts’ Adiumy Icons. They’re stupendous 😀