Did you get home only to find that Mac OS X 10.5.3 had been released today? Well, just as some users were unpacking and installing the shiny new update, issues with SIMBL plug-ins were discovered. If you have SIMBL plugins installed, then you may have an error show up when you try to launch an application. Past updates on systems with these plugins installed have been known to run into some issues.

If you are experiencing plugin predicaments, there is a way to fix the problem. SIMBL plugins (or other, non-SIMBL InputManager plugins, which may also be problematic) can be installed in any one of the following directories:

• ~/Library/Application Support/SIMBL/
• /Library/InputManagers/
• ~/Library/Contextual Menu Items/
• ~/Library/Internet Plug-Ins/
• ~/Library/InputManagers/

When you see the error in an application, just jot down the name of the plugin and look in those directories for it. When you find the plugin, just move it to a separate folder or toss it into the trash can. The application launch problem should cease.

Have you experienced plug-in issues since installing the 10.5.3 update? If so, tell us about it in the comments.

Well slap my Safari and call me Susan-- it seems that the rumors of Inquisitor's demise (like so many things nowadays) were greatly exaggerated. Apple Reporter points out that Inquisitor, the Safari search plugin that everyone likes so much, has been "repackaged" for Leopard. Originally, we were told that the fact that InputManagers were being discontinued in the new OS would kill off Inquisitor and other Safari plugins that used them, but Inquisitor works.

Of course, as we've already noted, noone knows for how long. But it seems that instead of deleting them whole hog, Apple just reined InputManagers in, and Inquisitor was able to stay in business. Good news.

Inquisitor, a bee-you-tiful Safari plugin that allows you to get instant, Spotlight-esque search results, has updated to 3.0 v43, adding "aesthetic tweaks" (always nice) and slightly better output from Google. The new version is available for free download right now.

And unfortunately, it may be the last version-- Dave Watanabe, the creator, writes on his blog that the rumors say Input Manager, which is the construct that Inquisitor uses to work the way it does, may be eliminated in Leopard. And that would leave a lot of plugins, including Inquisitor, out in the cold. It's not guaranteed yet-- some say that while Input Manager may be disabled by default, it'll still be allowed to be enabled when a plugin tries to use them-- but Watanabe says that if Apple ditches it completely, it would mean the end of Inquisitor.

Supposedly Apple claims Input Managers are a security risk, but Watanabe is asking Inquisitor fans to send them feedback asking to keep the construct in Leopard. Then again, Apple isn't really a company that takes advice on how to update its software, but losing plugins like Inquisitor would definitely be a shame.

Thanks, Space Taker!

There's a disturbing rumor floating around the Mac web today. According to this article at Infinite Loop, Leopard will no longer support Input Manager hacks. Input Managers allow programmers to insert code into cocoa applications, thus allowing the addition of new functionality. etc. These are somewhat controversial as some claim this is a potential security hole. Nonetheless, Jon Hicks brings this up in connection to my absolute favorite input manager plugin, Saft for Safari, which will presumably be rendered non-functional in Leopard. As Hicks notes, its not clear yet whether this also affect the widely used SIMBL plugin architecture (whose author, Pith Helmet developer Mike Solomon, says he won't be sure until he can play with Leopard). If, like me, you're a big fan of Saft and SafariStand and Chax, etc. this is cause for concern.

It is to be hoped, of course, that the authors of the various plugins will find some other way of implementing their feature enhancements, even if Apple does close the Input Manager route. The best thing would be for Apple to implement an open plugin architecture for doing this sort of enhancement, but I won't be holding my breath on that one. In any case, this is a potential concern for those of us sure to upgrade to Leopard right after it launches.