Interesting. Initially I chose to use helper tool to run sudo commands. After wrapping all those poorly-documented Authorization/ServiceManagement/XPC C APIs into Swift 3, I was like, sh*t, lemme just use askpass. Also, many of those APIs are deprecated in newer version of macOS and it's unclear that when Apple will remove them. That said, I can see the HUGE benefits of using launchd under the hood.
Hmm..I'm also using 10.11 with the dark theme. Does the app on your machine look very different from what I show in the second screenshot at http://www.marathono.com/? If it does, please consider reporting a bug thru the Help menu of the app.
The "Show Output" menu of Marathono opens a Terminal/iTerm tab to tail the output. Currently Marathono is designed for start-and-forget kind of processes - outputs are for occasional debugging purpose only.
The "may start charging for it" piece is mostly for stopping people from asking me to open source the app. If I do start charging money, it will probably be at the price of a burger.
I'm the developer of PSequel (a popular PostgreSQL client, http://www.psequel.com/) and it has been free since it came out two years ago. I got people asking for open sourcing it almost every single day. Many people assume free == open source.
Correct me if I'm wrong, "brew services" work for launchd services installed with homebrew only. But Marathono allows you to run any arbitrary commands.
2. When you switch from one DB to another in postgres, you are essentially making a new connection instead of reusing the same connection[1]. In PSequel, you could create different connection bookmarks for different databases and open multiple connections at the same time in multiple windows.
3. In my company, we write migration scripts (activerecord migration) to modify table structures. We usually don't modify them directly/manually. 80% of the time we use GUI tools just for viewing data and testing out complicated SELECT queries. I didn't realize that many other people's usage patterns are different. Anyway, the feature of modifying table structures is in PSequel's roadmap.
Writing a PostgreSQL adapter for Sequel Pro is a good idea. I don't know how an adapter can fit into Sequel Pro's architecture though. I'll take a look at Sequel Pro's codebase and consider this approach. Any help would be appreciated!