Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Textblock usage tracking #16

Open
GeorgeCiesinski opened this issue Jan 24, 2020 · 2 comments
Open

Textblock usage tracking #16

GeorgeCiesinski opened this issue Jan 24, 2020 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@GeorgeCiesinski
Copy link
Owner

Track how often textblocks are used so that it is easier to decide which templates are not needed any more.

@GeorgeCiesinski GeorgeCiesinski added the enhancement New feature or request label Jan 24, 2020
@GeorgeCiesinski GeorgeCiesinski added this to the 2.0 Release milestone Jan 24, 2020
@GeorgeCiesinski GeorgeCiesinski self-assigned this Jan 24, 2020
@GeorgeCiesinski
Copy link
Owner Author

GeorgeCiesinski commented Jan 30, 2020

Options:

  • 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

@GeorgeCiesinski
Copy link
Owner Author

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.

More thought needs to be put into this feature.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant