You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
1 - Use a list containing all textblocks ever added
Pro:
-- Complete history
Con:
-- List will continuously get longer
-- No way to remove history
-- Some shortcuts may be private
2 - Use separate list for removed text blocks
Pro:
-- Ability to bring textblocks back into use and maintain history
Con:
-- More work to program: two separate lists and mechanism to move item between lists
3 - Use single list only with existing shortcuts
Pro:
-- Easiest to implement
Con:
-- Doesn't maintain history for removed shortcuts
4 - Modify textblock files to keep their own history
Pro:
-- Most professional setup
-- Better data files for textblocks
-- Can be later modified to keep more data such as custom or varied delimiters
Con:
-- Hardest to implement
-- Requires additional mechanism to convert old text files into new format
Another requirement is keeping history for personal and network (shared) textblocks. How would option 4 work if multiple people try to edit the same file?
Lists are most likely the best way.
There can be a USAGE TRACKING folder that is automatically generated in the root of each directory (local and remote) if it does not exist. This can automatically load every textblock into the list and keep tracking.
A system would have to be setup to avoid consecutive writes.
Another option would be to keep all the usage tracking locally, and write to the file as the program is started the next day, or at another time.
Track how often textblocks are used so that it is easier to decide which templates are not needed any more.
The text was updated successfully, but these errors were encountered: