Difference between revisions of "ChromeBrowsers.sbs"
(New page: This file allows you to set up detection patterns for Chrome based browsers that are not yet supported by the main executable files. ==Structure== The structure of the file is a standard ...) |
(No difference)
|
Latest revision as of 10:38, 16 December 2009
This file allows you to set up detection patterns for Chrome based browsers that are not yet supported by the main executable files.
Contents
Structure
The structure of the file is a standard .ini file, with a free number of blocks of the format
Path=<path(string)> UserDataFolder=<path(string)> Executable=<path(string)> ExecutablePathRelative=<flag(boolean)> CheckExecutable=<flag(boolean)> BrowserType=(Beonex|Firebird|Firefox|Flock|K-Meleon|Lolifox|Mozilla|Netscape (6 or later)|Netscape (4.x)|Wyzo|Thunderbird|Postbox|Songbird)
Path
Full path to data folder. Supports path templates.
UserDataFolder
Relative path to the actual data.
Executable
Path to the main executable (used to get version information, for example).
ExecutablePathRelative
Set to 1 if path above is relative to data path.
CheckExecutable
Set to 0 if you do not want to test whether the main executable exists.
BrowserType
Only currently supported browsers are listed here, you'll have to pick the nearest one for yet unlisted browsers. This is just for display purposes - all Mozilla support includes automatic detection of old (up to Firefox 2) or new (Firefox 3) data files.
Example
Path=<$LOCALAPPDATA>\Google\Chrome\ UserDataFolder=User Data Executable=Application\Chrome.exe ExecutablePathRelative=1 CheckExecutable=1 BrowserType=Chrome
An updated file of this format can be put into regular 2.0 updates to extend browser support withouth the need for a larger binary (executable) file update.