What is important, at this very moment, is that I’ve adapted it (and my former Coda Plugin) to a system-wide service for Snow Leopard.

This lets you turn any (editable) text, anywhere in the system, into a linkified string: RTFs get clickable link attributes, and plain text gets a HTML A tag.

The code is here: http://bitbucket.org/sholt/autolink-service/

The binary is here: http://bitbucket.org/sholt/autolink-service/downloads/AutoLink.service.zip

Just drop it into Library/Services and go.

Issue 32 – maccode – Build PSMTabBarControl as 64Bit (patch included) – via Google Code:

The future is 64-bits, and that means leaving our 32-bit build processes behind.

Posting this as a patch just so we don’t break people building from trunk, as this patch requires the 10.5 SDK.

Every step forward is an important one: Any kind of help is needed and appreciated.

I’ve hacked together a quick plugin around the AutoHyperlinks framework that will find raw URIs and email addresses and link them.  URIs in existing markup is skipped, mostly.

get the plugin | get the source

Quality is still a little rough, but it handles simple markup well (and you can always run it on just a selection of text).

I’m releasing the plugin under a 3-clause BSD license. More to come, I hope.

Enjoy.

Now… SquirrelFish Extreme. Tacky name, but damn, does it look fast.

All of these use some form of JIT compiling and intelligent run-time caching schemes to get as much out of the interrupter as possible. But it looks like SFX’s regular expression JIT compiler is putting it over the top of V8.

I fully expect Google to answer in their typical fashion.

I do want to stress that comparing benchmarks of software that’s currently beta-quality (at best) is a bit misleading; however, with the oncoming wave of web-based applications (and rich JS frameworks, like Cappuccino), increasing JS performance is a beautiful, beautiful thing. And, so long as they’re sticking to standards, a little friendly competition never hurt nobody.

Steve Jobs must be a timelord, and he’s lost the keys to his TARDIS.

And the man’s got a point.

Apple promised a new (F)NDA would be delivered to developers “within a week or so” …over 3 weeks ago. And, while that won’t necessarily affect the public availability of the iPhone documentation, it at least will take some restrictions off current developers.

Right now, developers can’t (legally) trade expertise and information on working with the iPhone’s frameworks in public. This means no developer’s forums or 3rd party code sharing/how-to sites, no blog posts on some cool trick that will make everyone’s iPhone apps that much better and, most importantly, no open source apps (the ones that exist, do so on shaky ground—ground the Adium team, at least, is unwilling to stand on).

It’s Apple’s call, of course, but allowing devs to freely swap ideas and development tricks can only help the quality of applications offered through their storefront. And, personally, makes it a much more exciting and fun platform to develop on.

Update: As explained in the link above, the iPhone APIs went public with a new iPhone Developer Terms and Conditions document on Oct. 23rd.

COLIN IS A KNOWN AND UNREPENTANT ENEMY OF PANTS

#define NSBOOL(_X_) ((_X_) ? (id)kCFBooleanTrue : (id)kCFBooleanFalse)

COLIN IS A KNOWN AND UNREPENTANT ENEMY OF PANTS AND HAS EXTENDED HIS NO-PANTS AGENDA INTO THE HERETOFORE PURE AND PRISTINE NSFOUNDATION FRAMEWORK.

I QUOTE THE GREAT MR. JOSEPH WELCH FOR YOU MR. BARRETT:

HAVE YOU NO SENSE OF DECENCY SIR, AT LONG LAST? HAVE YOU LEFT NO SENSE OF DECENCY?

I’ll be continuing development on it over there and porting changes to adium (or just setting up an svn:external property – we’ll see) to prevent any GPL contamination of the main source.  Not that it’s likely, of course, but one can’t be too careful about these things.

In addition to tons of overall improvements, this release includes the new BSD-Licensed AutoHyperlinks Framework, which offers many, many improvements over the old architecture.

I don’t know if this is required for every python/mysql install, but I know it was needed when building for MySQL 5 insalled from macports, and the system provided python libraries.

Simply fetch the patch, then apply:

patch -u -p0 -i /path/to/_mysql.c.patch

After that, make and make install as usual. That should do it!

Combined with some API refactoring I’m doing (AHHyperlinkScanner works much like NSScanner now), it’ll be a nice slick little framework that’s thread safe and nice to work with.

I’m planning on committing the source post Adium 1.3 branch since it plays with API elements and I don’t want any surprise regressions to hold up release, but, if you’re curious, you can get a patch to apply to Adium’s svn trunk here.

[Update:] Just a quick edit to add that this version of the framework, which is included in Adium’s svn tunk and will be released alongside Adium 1.3, will be dubbed AutoHyperlinks.framework 1.0 and added to the maccode repository.