Axem - AutoHotKey Scripts Manager
(written in Autohotkey). It should help you manage your scripts
without dictating your workflow.
Features
* When you start Axem it discovers a list of .ahk scripts in a
userdefinable (saved) directory.
* Double clicking on tray will present a simple form with each
script listed on its own line with a checkbox on the left.
* The user can then enable and disable scripts from that dialog by
checking boxes.
* Scripts that are enabled will be launched if not currently
running; scripts unchecked will be closed.
* There's a contextmenu to edit, compile, and publish your AHK
scripts, and it recognises any existing compiled script and publishing
locations
* Checks will be shown for scripts that are currently running.
* It uses the correct script editor, with notepad as an
alternative.
My latest version via <!-- m -->http://justice.dcmembers.com/<!-- m -->
Collect all PIDs from running scripts, via Run command. Make OnExit routine where it parses the collection of pids and Process, Closes all scripts.
No signature.
All ahk script may not be in the same folder and maybe in sub folders.
It would be useful to have possibility to :
- chose many différents folders and files
- include, excude folder and files
- scan entire hard disk(s)
- scan chosen folder(s)
You see what I mean : have greater flexibility to choose what to index.
He wrote it in 2008 so I dont think he is updating it or working on it any more
However, it has some bugs:
1.a. When I start it - it (randomly?) kills another script, but in the Axem's list it remains checked, so I have to unchek it (when such kind of a bug happens - unchecking works as checking) to execute it again and then hit "Rescan" to draw the check in the checkbox.
1.b. When I hit "rescan" - the same script gets killed too. Seems like the problem here is with some particular script, but why?
2. Generally, the idea to use checkboxes to run/kill scripts is not so good, I think buttons would do better.
3. Every time you "rescan" or "reload" - the "Help" menu grows: there appear some useless separators at the end of the menu. Not harmful, but looks ugly.
4. Upon selecting a folder to scan - it may take pretty much time before the script is ready to work. This happens, because after selecting a folder - the scripts starts a search "*.ahk", which may take long time, if you've selected, say, root folder of your disk.
5. Axem sometimes cuts the start of the script's path. It looks like this:
Some more issues, that can't be called bugs:
1. The script doesn't scan the memory, so it doesn't handle the script you are already running.
2.a. The script works only with one selected folder (and all of it's subfolders), so in case you have scripts in different folders that have no common ancestor - Axem won't let you control them.
2.b. The script has doesn't store the scripts it knows of into a list, so you can't just add all of your scripts into one list, so Axem would remember their paths.
3. This script doesn't have commands like "suspend hotkeys" or "pause script".
A small, nice and unique feature of this script is called "Synopsis", which parses the code of the script and shows the first comment, so you may add some description as a comment to the start of the script, which Axem will show you. That's nice
p.s.: it's a pity, that the author of the script gave up working on it.
Thanks for everyone's feedback. The situation is I wrote Axem as a request for others and not as a solution for my own problems. As a result it's very much a first version. Also I'm not currently developing any new projects in Autohotkey, and therefore rely on feedback from yourselves for improvements.
I have made the source to Axem available via bitbucket and accept pull requests if you have made changes you think are worthwhile to share with others. At some point I hope to look at the issues raised in this thread and see if I can come up with fixes. At the moment that's all I can commit to unfortunately.
View the source on:
https://bitbucket.org/svandragt/axem