aecreations
commented
4 months ago If a clipping is renamed, it would invalidate all its references in clipping-in-clipping placeholders, and it would be an annoyance for the user to have to hunt for all the clippings and fix them.
Consider adding ability to scan for clippings that references the renamed clipping and ask the user if they want to update them. This should happen when a clipping is renamed and the clipping is referenced in other clippings via the $[CLIPPING(...)] placeholder.
Alternatively, the automatic scan-and-fix could happen automatically, and could be turned on or off via a pref.
New built-in (preset) placeholder, $[CLIPPING(clipping)], for inserting a clipping into a clipping. The argument to the placeholder name is the name of the clipping to insert.
Referencing the clipping by its name, e.g.
$[CLIPPING(Reply to customer inquiry)], may be the most user friendly approach, except that clipping names can be long, and there could be more than one clipping with the same name. As for IndexedDB database lookups, the name field in the clippings data store is already being indexed, so there's no concern about performance.If there are more than one clipping by that name, then the first clipping that is found via the IndexedDB lookup is used. If a clipping by that name doesn't exist, then the placeholder should be inserted as is.
Recursion won't be supported - i.e., a clipping contains a placeholder for inserting a clipping, which itself contains a placeholder for inserting another clipping, and so on. The clipping referenced by this placeholder should only be processed once. But any placeholders that exist in the inserted clipping will be processed along with any other placeholders in the containing clipping.
When processing placeholders, clipping in clipping placeholders should be processed first before any other presets and custom placeholders.
Clippings Manager UI:
Clipping In Clipping. This should open a dialog, where user can search for clipping by name and pick from an auto-complete listbox.