issues specific to macOS

[PerBothner]

Here are simplified and tested build instructions for macOS (tested on Monterrey with HomeBrew and Qt6).

Some issues specific to running DomTerm on macOS:

• Window buttons ("traffic lights") when using a custom titlebar is implemented on Electron, but other platforms (Qt, Wry) simulate them using CSS, which doesn't have correct hover behavior. Seems fixable on Qt (see here) but may require Objective-C code.

• No menu entries in system menubar when using a custom titlebar on Wry frontend.

• Dragging sub-windows (panes/tiles) only works on Electron. Don't know the cause - likely missing/faulty drag-and-drop support in some browsers. Consider an alternate implementation using mouse-events (rather than drag-events). The upsteam GoldenLayout library does not, but at the cost of not being able to drag between top-level windows. However, at least on Qt when using sub-windows (as opposed iframes) we can use Qt6 pointer events (rather than browser events), which might be preferable.

• Maximize (full-screen) button doesn't work except on Electron.

• Need to figure out application close vs window close. Typically on macOS closing windows leave application running, but this doesn't make sense for DomTerm unless we also keep the backend process around.

• There are still problems with clashing openssl versions (native directory vs home-brew directory). Perhaps add a --without-openssl configure options, and add it to the "simplified" instructions.

[PerBothner]

This issue is now fixed:

• Can't use Safari or the preferred browser because /usr/bin/open ignores the hash part of a URL. Probably fixable by changing start.html to be specific to a browser invocation.

See 3254411.