[zackmorris]

I grew up in the 80s during the era of MacroMaker and QuickKeys, when you could just hit the record button and make macros to play back sequences of mouse and keyboard events. It was especially useful in programs like Photoshop before they added their own macro systems. I'm having trouble finding links about it:

https://en.wikipedia.org/wiki/System_6#MacroMaker

http://basalgangster.macgui.com/RetroMacComputing/The_Long_V...

The frontier was to eventually make everything scriptable and deterministic by getting more apps to have hooks that could be controlled directly (so like a specific command to click the close box of a window for example, rather than sending a click event right and down from the top left corner).

Anyway, this whole concept of how to use computers seems to be all but dead today and I can't help but feel that something of tremendous value has been lost. Please, if you ever write macro tools like Phoenix, add a record feature.

[l_t]

It does seem like we've realized that GUIs are not really the most automation-friendly way to interact with programs. But there are a lot of nice macro tools out there still.

For Windows, there is a macro scripting language Autohotkey [0], which has powerful recording GUIs built on it [1]. Although it doesn't support application-specific hooks that I'm aware of, it does allow introspection into the rendered GUI of the application, so you can "click a button" instead of "click a pixel".

OS X has Keyboard Maestro [2], which I've heard is good.

Also, many keyboards have macro recording built in. My Ducky keyboard can record and save macros with no custom software/driver needed. (the macros can even include mouse clicks, but that's a little janky.)

As a final note, I think the place I've seen macro recording still used the most is in gaming. In most other areas of computing, it's seen as preferable to make a special-purpose utility to solve a problem instead of building layers of automation on top of a more general-purpose tool.

(btw, this is just based on my personal experience -- I love automation so I've never been far from the macro-space. I'm not trying to argue against your point.)

[0]: https://www.autohotkey.com/

[1]: https://www.macrocreator.com/

[2]: https://www.keyboardmaestro.com/main/

[capableweb]

> It does seem like we've realized that GUIs are not really the most automation-friendly way to interact with programs. But there are a lot of nice macro tools out there still.

Yeah, in general the opinion seems to be "you want to manually do stuff, use a GUI. If you want automation, use the API of either a server-side backend or CLI tool", but there is a huge segment of users that are between that. Imagine power users that don't know how to program. For them to be able to quickly record > playback some common thing they do, would save a lot of time and be valuable

[bryanrasmussen]

For automation I like to have at least something like AutoHotKey or Sikuli, because there will always come up little temporary tasks that are time limited that you don't have the time to learn the apis needed to automate it before the whole task is supposed to be done, but the task itself is still so tedious and time consuming that it might run over time if not automated.