![]() ![]() So I may, when/if I get time, take a look at your system to see if it can easily be modified to only backing up changed macros. No problem backing up an extra 30 or 60 MB. Well, that's pretty cool! I'll give it a shot. JXA can read/write both Local and Instance Variables: This is what SourceTree shows has changed - one file: Yeah, but that's not really an issue, which is why I talked about using a VCS that compares file contents, not dates.įor example: I just changed a macro, and re-ran the updater macro. If it looks like it's actually going to be used, then I'll consider doing something about that. I would be great if you could provide us with a true restore option that would first delete the existing Macros, and then do the restore from your Repository, so that the Macro UUIDs are retained. Honestly, I didn't want to put the work into a UI to handle that. not a Local or Instance) variable long enough for the JXA script to use it.īut, if I want to "restore" an existing Macro to a prior version, so that all other Macros and scripts that rely on its UUID will continue to work, then it looks like I have to manually take other steps before I use your system to restore: The macro deletes the variable at the end. Since that does not follow the convention that you and I were using, which has a prefix of "DND_" for all Variables to Do Not Delete, what about this Variable? Is it a Variable we must retain? This looks like it uses a Global KM Variable, macrep_repositoryFolderPath. I'm just trying to make sure I understand correctly. Don't take any of my questions in a critical way. Is there a way to know when then last time a Macro was modified? Is this correct?Īlso, it appears that I have to manually invoke your backup system, as opposed to having it run periodically and do a classical backup strategy of either "full, differential, or incremental"? I suppose we can add a Macro Trigger to your backup macro that runs on some schedule, right? So, if I understand this correctly, your backup system is an all-or-nothing, with no option to just backup selected macros, or backup macros that have changed since the last backup. So, after running the Macro Repository Updater macro, you can update your VCS if you want.īecause every time the Macro Repository Updater macro is run, ALL the source files are recreated. If you don't want to read any documentation, at least read the comments at the top of the Macro Repository Updater macro.Įach time you run the Macro Repository Updater macro, the Data folder is trashed and re-created, and populated with all your source files.This should cause Keyboard Maestro to import two macros into a group named "KM". Unzip the contents, which will give you one ".kmmacros" file.Macro Repository.v1.1.0.kmmacros.zip (65.1 KB) Installation Added the variable Instance_showLog.Īdded option to bypass the trash when deleting the Data folder. Added links to the online documentation.įixed an issue with "blank" Group names. TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THEĪdded the variable Instance_saveAsJson, which lets you save source files as JSON instead of XML. WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES IN NOĮVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. ![]() THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMSĪLL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL Granted, provided that the above copyright notice and this Software for any purpose with or without fee is hereby Permission to use, copy, modify, and/or distribute this So although I think this Suite works well, please be aware that something could go wrong, and I can't guarantee perfection. I've tried my best to eliminate bugs, but nothing's perfect. Lets you select Group or Macro source files from the Repository Folder, and import them back into Keyboard Maestro. ![]() Saves all of your Groups and Macros to individual source files, in your Repository Folder. The Macro Repository Suite contains two Keyboard Maestro macros that are extremely easy to use: Macro Repository Updater ![]() This makes it easy to back them up, reload them if needed, and optionally place them under Version Control. (I know, famous last words.) PURPOSEĬreates separate source files for each of your Groups and Macros, in a Repository Folder of your own choosing. Update : I've been using this for a couple of years now, and I've never encountered a problem, so it's pretty stable. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |