Autohotkey for Mac
Posted: 18 Jan 2017, 12:29
Hi, is this compatible with OSX? If not any alternatives you suggest
Let's help each other out
No, it is not compatible. I am not familiar with alternatives for OSX.Laura wrote:Hi, is this compatible with OSX? If not any alternatives you suggest
AutoHotkey Mappings to emulate OSX behavior with a Mac keyboard on Windows
This AutoHotkey configuration file makes usual keyboard shortcuts work with an Apple keyboard on Windows. It has been testet with a german keyboard layout, but should work under different layouts as well.
by Jonathan Ströbele (stroebjo)
I've heard you can do this by translating AHK via another common language, such as Lua. For instance have Lua "interpret" the AHK code by reading regular AHK code and then tranforming it into something Mac OS can understand. (untested on my end, so not 100% sure)
That sounds like a Transpiler or Source-to-Source Compiler, https://en.wikipedia.org/wiki/Source-to-source_compiler. Many other programming languages make use of such. It's interesting that this isn't being done for AutoHotkey. I don't know how well Lua works out as a cross-platform language. C#, Object Pascal, or Red would be good cross-platform candidates as well.Tigerlily wrote: ↑07 Apr 2019, 13:08I've heard you can do this by translating AHK via another common language, such as Lua. For instance have Lua "interpret" the AHK code by reading regular AHK code and then tranforming it into something Mac OS can understand. (untested on my end, so not 100% sure)
True, but that doesn't have to be the case. I think it requires developers willing to go outside of the Windows OS and possibly knowing a programming language other than C++. Strong candidates would be Lua, C#, Object Pascal, Red, and maybe Dart.
Yes, IronAHK could work on different OSes. This is because of .NET and Mono, and Microsoft's (and the company they bought, Xamarin) push to make C# cross-platform. But part of the problem with IronAHK, and part of why it was never finished, appears to have been a major fight between the developers and the AutoHotkey websites. There is possibly still a lot of bad feelings, so IronAHK went untouched. To include that it requires developers to switch focus from C++ and Windows centric, to C# and cross-platform development, which is harder to do.
AytiH0tKyFn wrote: ↑30 Oct 2019, 01:29Personally. I think you as a business need to honestly look at the LARGE amount of potential revenue and business you are passing up by not creating a macOS version of this simple yet useful app. THERE IS NO TRUE ALTERNATIVE LIKE YOUR ANYWHERE FOR MAC!!!
And frankly, I personally believe that if you have not already done so, the only conclusion I come to is you pure 100% lazy-a-holes and I hope you go bankrupt and have horrible diarrhea everyday from now until you finally smarten up and create a macOS comparable version!
But hey, that's just my 2-cents!
This is not true. People are confusing the C++ interpreter for the Windows OS with the AutoHotkey language. These are separable entities. That means you can create an interpreter for the MacOS, to include in various other programming languages (C#, Object Pascal, Red, Lua, Python, etc...). The C++ AutoHotkey Interpreter is heavily dependent on the Windows API, not the AutoHotkey language.Getfree wrote: ↑30 Oct 2019, 18:52Unfortunately there's no way to implement a version of AHK for Mac. Its implementation is way too tied to the Windows API. You would have to emulate so much about the Windows API inside Mac OS that you would end up with an emulation layer similar to Wine. But we already know that such an emulation layer is doomed to fail because Windows is closed-source, and so trying to reverse engineer the entire Windows API is not feasible.
The DllCall function alone can tie any AHK script to the Windows API at such a deep level that the only way to run that script successfully on MAC is with a virtual machine.