Repository navigation
macOS port available as a fork (DMG, Apple Silicon + Intel) #83
Replies: 1 comment
|
@SVorobiev-ru hey, thank you for this, and for reading #21 and #67 first. On the README link: I am going to pass for now, and I want to be honest about why. A link from the README reads as my endorsement, and I cannot endorse a macOS build I have never run. My rule is that I only put my name behind what I can test myself, and with no Mac I can't do that here. Same reason I am not taking PRs for it right now. Keep it as your own community port, and I genuinely mean the other two offers: when I buy a Mac after graduation and look at a proper Mac port, I would love your help testing, and I would be happy to look at your approaches then. One small suggestion: consider shipping under a name other than "Edge-Drop". Searches for it are already cluttered by Microsoft Edge's Drop feature, and a distinct name will serve your port better. Thanks again, and glad you use the app every day. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi @Deepender25! I ported Edge-Drop to macOS in a fork and wanted to let you know in case it is useful: https://github.com/SVorobiev-ru/Edge-Drop (branch
macos-port, releasev0.3.2-mac.1, DMG and ZIP for Apple Silicon and Intel).I kept the codebase shared with yours: Windows code paths are untouched, and the mac logic sits next to them behind
process.platform === 'darwin'. Your Windows tests still pass, and CI runs the suite on both macOS and Windows. What differs on macOS is listed inMACOS.md.I saw #21 and #67 and understand you can't maintain a macOS build without a Mac. So no pressure to merge anything. A few options, whichever suits you:
The build is signed ad-hoc (no Developer ID, not notarized), so users have to remove the quarantine attribute once; this is described in the release notes.
And thank you for a wonderful app. I use it myself every day and I'm really happy with it.
All reactions