OmniWeb 3.1 plugins
Charles R Wiles
charles at teaching.physics.ox.ac.uk
Wed Mar 7 04:06:08 PST 2001
Peter,
Peter Aamodt spoke thus at 22:08:40 on Tue, 06 Mar 2001:
} I am using OmniWeb 3.1 under OS4.2.
Likewise (or, at least, I think it's 3.1--it's been some time since I
installed it--and I have a vague recollection that 3.1's info panel still
said 3.0!).
} I have two questions re: the unsupported plugins (e.g., Flash, QuickTime,
} etc) available on the OmniGroup web site:
}
} 1. Where is the proper place to install these plugins? Is it
} /LocalLibrary/Plugins, in the .app directory itself where the other
} (supported) plugins are, or someplace else?
I think you can put them in several places (including within the app
wrapper), but the most sensible place is probably: /LocalLibrary/PlugIns/
It works for us, though do note the capitalisation of "PlugIns": I initially
tried "Plugins" and it didn't work! :->
} 2. Has anyone successfully used the unsupported Flash plugin with 3.1, or
} is it incompatible with version 3.1? (when I look at the plugins loaded
} with OmniWeb, the app reports that the plugin is invalid.)
We do have a Flash.plugin which is happily registered by OmniWeb: I'm not
sure if it's necessarily a full implementation of Flash (though I could be
wrong). Within the Flash.plugin directory/wrapper you'll see a Resources
directory. In that is an Info-nextstep.plist file. At the bottom is a line
something like:
OFRequiredSoftwareVersions = {OmniHTML = 1999C; };
When you launch OmniWeb, look in the Console for the line:
OFBundleRegistry: Registering
/LocalApps/OmniWeb.app/Resources/OmniHTML.framework (version 1999C)
You may need to edit the Info-nextstep.plist file if its version number
doesn't match that of the OmniHTML.framework bundle.
} And of course, there's always one more
} vote in favor of a finished OmniWeb version 3. Thanks in advance.
Ditto: though I guess the guys are rather pre-occupied with OS X. It is a
shame that OWeb 3 has never quite been finished: there's still the spinning
cursor annoyance due to the multi-threading problem.
regards,
charles
More information about the OmniWeb-l
mailing list