How to activate OmniWeb 3rd party plugins in OW 3.0 beta 9?

Floyd Hanson hanson at poincare.math.uic.edu
Sun Apr 4 12:50:33 PDT 1999


Holger Hoffstaette <holger at wizards.de> said:

=====
HH>"So, recompiling/relinking bundles should work and be all there is to it.
HH>Oh yes, you also need to set the key/value
HH>
HH>        OFRequiredSoftwareVersions = {OmniWeb = "3.0-beta-9"; };
HH>
HH>in the bundles' Info-nextstep.plist because otherwise your bundle will be
HH>marked 'obsolete'. The above worked fine for the PrintExtensions bundle;
HH>no guarantees etc."
=====

Since I heavily rely on HTTPS plugins for my professional transactions
within my university and the national computing centers, I need to make
sure I have the right before upgrading to OW3beta9.  What "bundles' 
Info-nextstep.plist" do I have to reset, since I have about a 
dozen such files associated with Omni alone?   Several of which have
the cited key "OFRequiredSoftwareVersions".

Thanks,
Floyd
OS=Openstep 4.2
~



More information about the OmniWeb-l mailing list