Installing OmniWeb in alternative locations

[Ken Case]

> I don't have permission to write in to the /LocalLibrary and
> /LocalApps directories so I installed all the OmniWeb stuff
> (browser, frameworks, components) elsewhere.  However, OmniWeb
> won't start up. How do I tell it the new locations for the
> FrameWorks and Components?

The components can go anywhere listed in OFBundleRegistryConfig's  
"SearchPaths" (defined in OmniWeb.app/Resources/Info-nextstep.plist).   
This list includes the ~/Library/Components directory by default, so if  
you install the components there OmniWeb should find it.   
(Alternatively, you can put the components directly in the  
OmniWeb.app/Resources directory.)

If you're using Rhapsody, you can put your frameworks in  
~/Library/Frameworks.  If you're using Windows, you can put the  
framework executables anywhere in your PATH (just  make sure the  
framework resources are in ..\Frameworks).

If you're using OPENSTEP/Mach 4.2, you can't relocate the frameworks  
unless you define the DYLD_FRAMEWORK_PATH environment variable to point  
at the new location.  (One way to do this is to set the environment  
variable from the command line, then launch OmniWeb from the command  
line.  Unfortunately, it's difficult to set environment variables in  
the Workspace.  Maybe someone should write a Workspace bundle...)

				Ken