Using the formal HTTP authentication scheme was too cumbersome and I couldn't pre-fill out that information as part of the request.  IE11 emulation ignores any credentials as part of the URI.  The web browser control insists on displaying a credentials dialog when challenged.

So for now, look for a 'secret' header which just contains a thread identifier.

Authentication is skipped if the app was started with the --debug command line argument.  You'll be able to attach and debug your HTML application via the port number written in the Window title.

* Implement a mini HTTP server to service file requests from the slot
directory.  Have the browser control download the file(s) via the
HTTP protocol instead of the FILE protocol.

TODO: Lock down the authentication mechanism so that it is reasonably
protected even though it is only bound to the loopback adapter.

* Configure the browser emulation level for the executable to
Internet Explorer 11.

The translation code (translation.inc) had a special case
where if the first accepted language was "en", it would show English.
Problem: if the accepted languages are, say, "en-us", "en", "es"
then you'll see Spanish.
Fix: check for both "en" and "en_*" in the special case.

The logic of this code is still flawed, however.
It builds a list $languages_in_use of accepted languages
for which a translation file exists,
and to translate a word it tries these in sequence.
So a page could have translations from several languages.

What it should do is scan the accepted languages until it
finds one that either is English or for which a translation file exists.
Then use that one.
(there could be a check that skips languages for which
the translation is very incomplete).

HTMLGFX: Normalize the URLs configured by way of the configuration file.  MSHTML would attempt to use HTTP when only a filename was given.

HTMLGFX: Remap the JavaScript methods and properties to camel case to match the JavaScript standards.

HTMLGFX: Do not overwrite the State URLs if a project also exposes a Web API port as well.  A project may choose to have a running HTML page that makes JSON calls to a web server running within a VM or science application.

HTMLGFX: parse a boinc_graphics.xml file for a list of optional urls the htmlgfx can use for various states (running, suspended, network suspended, exiting).
HTMLGFX: look for and use various vboxwrapper state files for extracting the remote desktop port number and the webapi port number.

HTMLGFX: Remove progress bar for now.  It appears to be a bit too fancy and is distorting the page layout.

API: Introduce the graphics_status APIs which will be used by vboxwrapper/wrapper/project app to inform htmlgfx what is going on.

MGR: To allow WCG and other "branded" BOINC Managers to customize the "More info ..." hyperlink in the Diagnostic Log Flags dialog, build the URL using the value from the skin's <organization_help_url> field.

MGR: Add "More info ..." hyperlink to Diagnostic Log Flags dialog; clicking it takes you to the Log Flags wiki page.

HTMLGFX: Add some more infrastructure for passing APP_INIT_DATA stuff to the HTML web page via the DOM.

e.g. say the prefs don't apply to Android, or if set locally

Force the COM libraries to look within the executable instead of going out to the registry for the typelib information.

MGR: Work around a probable bug in wxWidgets on Linux which prevented some wxListCtrl rows from updating.