Hi everyone - I’m looking for some advice…
Greg’s brought it to my attention that the ThoughtAsylum Action Group as it currently stands is pushing some of the iCloud limits that Drafts actions sync is built upon. As a result, I need to make some changes before I make it so big that it stops working
Step 1 - The Relatively Easy Change
The first change is that in the next update I plan to make some amendments that will move the
TAD-Library action out of the main library. This is only currently actively used for the download of the file version of the library, but there’s also a setting where you can switch the action group to use that action rather than the file. I plan to just make the
TAD-Library action a separate download in a separate group (to dissuade anyone putting it in the original group and busting the limits) for anyone who wants it, and I still plan to keep it up to date, in line with the file version. The file download action (
TAD-Setup/Refresh) will be modified to run independently.
This will roughly halve the library size, but I plan to keep expanding, so I’d like to build in more growth capacity just in case. This is where I want to get some advice.
Step 2 - A Change Where I Need Advice
I want to put in place a strategic solution rather than a tactical fix. Drafts gets features so frequently that I can take advantage of (I currently have some sat in a
TA - Beta Only action group for instance), I really want to ensure that I include the potential for more growth in the TADpoLe library and the action group without bumping into the same size issue in a year’s time.
The current action group has 55 sections containing 380 actions.
Expand to show the sections
- Whitespace Removal
- Sort & Permute Lines
- Draft Status
- Draft Syntax
- Move Cursor
- Insert Content: General
- Insert Content: Current Date/Time
- Drafts Markup
- Mass Processing
- Slash Command
- Tag Management
- Create Drafts
- Recent Drafts
- Populate Clipboard
- Share as Content
- Share as File
- Persistent Variable Examples
- Action Groups
- Action Groups - From Install URL
- Editor Insertions
- Text Modifiers
- Sample Content
- Reader Mode
- URL Encoding/Decoding
- Online Information
- Word Actions
- Action Control
- Helper Actions
- Advanced Logging
- Mac Audio
- Matched Line Removals
- MediaWiki Syntax
- Meta Based File Management
- App Control
- Link Note
- Draft Embedding
There are so many dependencies on the library, and for ease of manual update for users (and to an extent me), I’ve kept everything in one action group. But I feel that the next logical step is going to have to be to split it.
The question is what would be the best way to split this for such future growth?
- Would it make sense to just switch to a new action group when this one reaches a particular size (e.g. 400 actions)?
- Should I split the sections in the existing group and split those off into two or three other groups of somehow related sections?
- Should I sort the sections alphabetically and split into a number of groups by alphabetic section (e.g. A-M & N-Z)?
I’d like to make the transition as easy and sensible as I can. There is no single “correct” answer, so I figured the best way to figure out what might be best was to ask and see if there are any other ideas or a consensus around one of the ones above.
Thanks in advance for any and all suggestions and recommendations.