ignore missing projection-bytes config

[will-moore]

Fixes #375.

Handle missing server config max_projection_bytes
Not found on OMERO.server before 5.6.1

To test:

• deploy with OMERO.server 5.6.0

[sbesson]

Tested on a pilot IDR server (with a 5.6.0 server). While OMERO.iviewer was previously failing with the last release, it now opens as expected.

Also tested on a couple of datasets with various Z sizes that the projection are enabled/disabled with the same criteria as current production IDR.

Using the developer tools, I can confirm that MAX_PROJECTION_BYTES is set to "None" which I assume is the expected behavior

            window.INITIAL_REQUEST_PARAMS['WEBGATEWAY'] = "/webgateway/";
            window.INITIAL_REQUEST_PARAMS['WEBCLIENT'] = "/webclient/";
            window.INITIAL_REQUEST_PARAMS['WEB_API_BASE'] = "/api/v0/";
            window.INITIAL_REQUEST_PARAMS['ROI_PAGE_SIZE'] = "500";
            window.INITIAL_REQUEST_PARAMS['MAX_PROJECTION_BYTES'] = "None";

The above made me wonder: where is the threshold logic now happening since MAX_PROJECTION_BYTES is set to -1 and there is no server configuration specifying the maximum pixel size for projections?

[will-moore]

I think that if there is no max_projection_bytes set anywhere, then iviewer will enable projection for non-tiled images below a plane size of 2048 x 2048 (see #349).

[sbesson]

Thanks. At least from the IDR use case standpoint, this is good to merge and I could conceive an immediate iviewer release that we could consume in prod96 (I can handle the release if everyone is happy with the suggestion) /cc @jburel @joshmoore

[sbesson]

Discussed today. Merging to move towards a 0.11.0 release of OMERO.iviewer that we can deploy on a pilot IDR for testing.