Ruby would've suited well for the DSL this project is trying to implement.
Self Driving Desktop
31–39 of 39 posts
Re: Self Driving Desktop
#32Seems like a small wrapper around PyAutoGUI - that I've used before and is great: https://pyautogui.readthedocs.io/
Or an alternative to Automagica: https://github.com/OakwoodAI/Automagica
Re: Self Driving Desktop
#33Seems like a small wrapper around PyAutoGUI - that I've used before and is great: https://pyautogui.readthedocs.io/
Or an alternative to Automagica: https://github.com/OakwoodAI/Automagica
That one also depends on PyAutoGUI https://github.com/OakwoodAI/Automagica/blob/master/setup.py...
Re: Self Driving Desktop
#34Autohotkey: Xdotool edition
Re: Self Driving Desktop
#35Is it normal for devs to be able to read and understand github reps without any explanations, introductions or context beyond the title? I remember much more of this in github's early days and always wondered if this doesn't faze the talented devs reading it.
Re: Self Driving Desktop
#36Is it normal for devs to be able to read and understand github reps without any explanations, introductions or context beyond the title? I remember much more of this in github's early days and always wondered if this doesn't faze the talented devs reading it.
I think it would be fair to say that you shouldn't expect anyone to be able to understand a bare repo with just a glance, but if you're well versed with the technologies that the repo uses and you know of similar products, then I think you can guess it.
Here's how my thought process went on this one:
# I open the repo on github and look at the readme
1. Okay it's doing something automatic
2. It uses python
3. Okay there's this playlist thing which has a bunch of commands in it. Looks like of like an autohotkey script.
# I look at the file list
4. Okay I know lark. Looks like the author wrote a domain specific language parser for their input files. They probably get those commands out as a nested list from the parser.
# I look in test.txt
5. Okay that doesn't tell me much new
# I look in main.py
6. Oh there aren't any comments in here...
7. Alright the main function parses the commands from the input file and runs "do" on them.
8. Okay this is just like autohotkey
Re: Self Driving Desktop
#37Earlier quoted context omitted.
This is an excellent tool! But you forgot to mention that the user codes it in python, it comes with a purpose built ide, it recognises both text and images the latter with an approximation capability.
There are a number of other commercial and free desktop automation tools that exist, some of which I've used to automate GUI testing in the past. https://en.m.wikipedia.org/wiki/Comparison_of_GUI_testing_to... My favorite on the Windows side was vTask Studio, but it looks like the domain is down and the link was removed from that wiki page.
You can still grab vTask Studio via the WBM, thanks for that, shall be trying it out;
https://web.archive.org/web/20170927151003/http://www.vtasks...
Re: Self Driving Desktop
#38I think I have been looking for a framework this simple and straightforward for about...12 years now? Ever since I got my own personal computer as a college student, pretty much. I can't wait to completely go off the wrong quadrant of this chart with it. https://xkcd.com/1205/
re: xkcd, sometimes, it's not just about the time in minutes you save in aggregate. I often find routines especially helpful during flow states -- maximizing time for more creative work. There's also just something satisfying about using something like Alfred to launch a complex sequence of things that would have taken many mouse clicks and hand movement. Or using keyboard shortcuts to resize and move multiple window…
It mostly do not matter. The main goal for automating something is rarely to save time nowadays (the low hanging fruit are much rarer). It is to document procedures, prevent defects, or to test before running.
Re: Self Driving Desktop
#39One of the most unknown tools (>10 years) http://sikulix.com/ It allows play mouse/keyboard event scrips BUT it allows to find components (coords) via screen OCR so you can make your scripts multi resolution/desktop independent. Also, it's Java based so you can play it multi SO.
I don't think Sikuli is unknown at all - I have used it for a long time. But there has not been much progress over the last years, especially the OCR features are lacking. A good alternative to Sikuli is the newer Kantu, which is also much easier to install (just a browser extension + small native EXE).