http://writemonkey.com/wm3/

satis wrote:

http://writemonkey.com/wm3/

Looks like this update (3.0.5 Beta) is not just for Mac but also Windows and Linux.

On macOS High Sierra you need to take steps to bypass Gatekeeper. In Safari, turn off Preferences > General > Open "safe" files after download. This prevents macOS from unzipping the file. Download to Applications (not to Downloads) by right clicking the download link and using Save As… Do not use Archive to unzip the file -- use ForkLift or some other 3rd party archive utility. You might not need all of these steps, but over here I've found that this recipe guarantees that this and previous WriteMonkey betas operate correctly on macOS.

I thought that a Mac version was something new (I could be wrong), which is why I posted this. The dev said a year ago he'd hoped to come out with a Mac beta by the end of the year but I didn't notice it actually appearing until just now.

Paul Korm wrote:

On macOS High Sierra you need to take steps to bypass Gatekeeper.

Paul Korm wrote:

On macOS High Sierra you need to take steps to bypass Gatekeeper.

This is nothing new. Gatekeeper has been around since 10.7, and the solution isn't complicated. If the app isn't from the MAS or an 'identified developer' select the app in the Finder and [O]pen it. macOS asks if you're sure you want to open it - just click yes. If you're still having an issue just to into Privacy and click to make an exception for a given app.

Video:

https://www.youtube.com/watch?v=jiUOODUR1GQ

I'm downloading for Windows. Looks like 3 has folding!

Yes. Very very aware of all that. Thanks. However, the extra steps are needed for WriteMonkey -- as I described, based on the developer's notes for running WriteMonkey on Sierra/High Sierra. YMMV.

satis wrote:

Paul Korm wrote:
On macOS High Sierra you need to take steps to bypass Gatekeeper.



Paul Korm wrote:
On macOS High Sierra you need to take steps to bypass Gatekeeper.

This is nothing new. Gatekeeper has been around since 10.7, and the
solution isn't complicated. If the app isn't from the MAS or an
'identified developer' select the app in the Finder and [O]pen it. macOS
asks if you're sure you want to open it - just click yes. If you're
still having an issue just to into Privacy and click to make an
exception for a given app.

Video:

https://www.youtube.com/watch?v=jiUOODUR1GQ

This is thanks to "App Translocation", where .app bundles extracted into ~/Downloads/ are treated a bit differently: when you launch them, they will be copied to a secret location behind the scenes (= translocation) and opened from there. Even when you move the .app bundle out of Downloads and into /Applications/, the translocation stuff will still be operational. Thus the app may have a hard time knowing where it is, effectively breaking app updates, among other things.

Perhaps, but in the WriteMonkey case there appears to be more. Even if the .zip is downloaded directly to applications, the .app package can fail to launch correctly unless the developer's instructions (as I mentioned above) are followed. The 'incorrect' aspect is that when the unzipped .app is run, it only launches the JS console and does not execute the program logic. It's a beta product and the developer probably hasn't had time to "productionize" the package for macOS.

Christian Tietze wrote:

This is thanks to "App Translocation", where .app bundles extracted into
~/Downloads/ are treated a bit differently: when you launch them, they
will be copied to a secret location behind the scenes (= translocation)
and opened from there. Even when you move the .app bundle out of
Downloads and into /Applications/, the translocation stuff will still be
operational. Thus the app may have a hard time knowing where it is,
effectively breaking app updates, among other things.