Evergreen DokuWiki

This is an old revision of the document!

Do I Need The Java Shim (AKA Hatch) For My Browser Staff Client?

Firefox and Chrome both provide mechanisms for dialog-free printing.
- For example, in Firefox, it means adding an about:config boolean preference called "print.always_print_silent" with a value of "true".
Note: only activate silent printing after initial printer configuration.

When printing via the browser, use the browser's native print configuration dialog instead of the Evergreen/Hatch print configuration tool.

NOTE: the development community decided as a policy to require Hatch for storage of offline transaction files. Hatch provides better security from unintentional deletion, more capacity, and allows us to back the files up locally for disaster recovery / historical reference, etc. Technically, though, small batches of offline transactions could be stored directly in the browser, avoiding the need for Hatch. Whether that's a good idea, though, is debatable.

See also note from above
NOTE: uploading externally created offline files will be handled via file upload, similar to the XUL client. It's conceivable that a shared Hatch instance could aggregate the files instead, avoiding the need for manual file upload, but there are no specific plans yet to implement anything like this.

Do this to persist preferences across multiple browsers
Do this to prevent tampering with preferences or the workstation name by staff via the browser developer tools.
- Note: you can also do this by disabling access to the developer tools through browser configuration. (e.g. Chrome User Policies)