[porrid]

Recently updated Safari to 3.1 and when I opened it a dialogue told me that the 3rd party SIMBL elements no longer worked.

There does not seem to be a Menu item in Safari that includes plug-ins or add ons as in Firefox there is a menu item called Tools which can help one figure out which tools are enabled or have been disabled by an Updated version !

I suppose Apple will never get around to showing which tools are enabled or disabled ion any of their apps, huh ?

[Person Man]

Originally Posted by porrid 

Recently updated Safari to 3.1 and when I opened it a dialogue told me that the 3rd party SIMBL elements no longer worked.

There does not seem to be a Menu item in Safari that includes plug-ins or add ons as in Firefox there is a menu item called Tools which can help one figure out which tools are enabled or have been disabled by an Updated version !

I suppose Apple will never get around to showing which tools are enabled or disabled ion any of their apps, huh ?

What you have to realize is that Apple does NOT have an official way to extend Safari via interface plug-ins or addons like Firefox. Third parties have to resort to hacks in order to do it.

Since Apple doesn't support them, they will never have a way of showing what is "enabled or disabled." In the future, Apple may remove the ability for people to write (or use) these types of hacks entirely, because the techniques used to implement them are a security risk.

For now, every time Safari is updated, you'll have to wait until the third parties that made whatever hacks you're using (PithHelmet, Saft, etc). are updated to work with the new version.

[kga1978]

This will probably not answer your question 100%, but if you open up "Console" after having opened Safari, you will be able to see which extensions are loaded and which ones aren't.

Hope that helps.

[Cold Warrior]

Safari is an application. Moving...

[JKT]

MacJournals News : Input Managers are not 'plug-ins'

Short story: what people are doing with their 'Input Managers' is not what the Input Manager API was included in the OS for - it is meant for extending the text entry capability of the OS for e.g. additional unsupported languages and/or universal access needs, and not for hacking applications.

[porrid]

Thank you all for the isights

So Personman is that sad or necessary ?

Hey kgl1978, that's excellent.

Often wondered why a dedicated program hasn't yet emerged that can inform users like that console trick which can identify added 3rd party parts to all apps in your system. Like we willy nilly go about downloading and installing parts to things but just how many of us can keep a record of these infiltrated additions ?

JKT, if Input Managers are not 'plug-ins' why don't programmers create Plugins in the Services Menu ?

So I wonder if Console can detect addons, plugins and input managers in other OSX apps ?

[King Bob On The Cob]

Input Managers work in an entirely different way than Services. Services are used to pass objects between applications while Input Managers allow you to replace code in applications. (Which is really quite useful as a programmer if I may say so myself). Yes it's a security risk, but I like being able to increase functionality without rewriting an entire application.

To detect add-ons that are installed, the only real way to do it is open up Activity Monitor. Then click "Inspect" then click over to the "Open Files and Ports." That will show EVERYTHING that the application has loaded including images, caches, preference files, etc... No really easy way to check otherwise.

[FireWire]

Originally Posted by JKT 

MacJournals News : Input Managers are not 'plug-ins'

Thank you! very informative!