Henry Sobotka wrote:
> John Poltorak wrote:
> >
> > Is there any documentation available about the various configuration
> > files for Warpzilla?
>
> There are no config files as such, unless I misunderstand what you mean.
By config files, I am referring to files such as:-
C:\warpzilla\bin\defaults\pref\all.js
C:\warpzilla\bin\defaults\pref\config.js
C:\warpzilla\bin\defaults\pref\editor.js
C:\warpzilla\bin\defaults\pref\initpref.js
C:\warpzilla\bin\defaults\pref\mailnews.js
C:\warpzilla\bin\defaults\pref\os2pref.js
C:\warpzilla\bin\defaults\pref\security-prefs.js
C:\warpzilla\bin\defaults\pref\xpinstall.js
or registry.dat or anything which goes in the PLUGINS directory....
Is there a Warpzilla equivalent of NETSCAPE.INI ?
What I want to know is whether there is a way to install Warpzilla
with a predetermined configuration including fonts, schemes, helpers
etc so that it does not need to be customised manually after installing.
Being able to run some sort of REXX script to update every customisable
option would be OK, but having to manually click one's way round the
Preferences menu is too much like the Windows way of doing things and
is quite time consuming and obviously subject to 'operator error'.
> The binaries are simply the zipped up /bin directory created by the
> build process, minus the uncompressed versions of the files in .jars,
> and anything else the packager might want to remove (e.g. build
> utilities, sh scripts etc.).
>
> sehh's installation package supports CID AFAIK. It eats the /bin
> directory from any Warpzilla nightly, and could be tweaked to
> accommodate helpers.
I was wondering whether installation of helpers from the command line was
possible...
>
> h~
--
John
