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

Track activity to allow productivity feature #69981

Closed
Goaman opened this issue Mar 7, 2019 · 2 comments
Closed

Track activity to allow productivity feature #69981

Goaman opened this issue Mar 7, 2019 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@Goaman
Copy link

Goaman commented Mar 7, 2019

Feature

Track activity when using VSCode. For instance:

  • Executing a command from "Quick Open"
  • Executing a command from a shortcut
  • Clicking on a tab
  • Focus on a pane
  • ...

The more the activity tracked, the more we can do with it.

Purpose

  • Someone want to learn new command/shortcuts but don't know where to start.
  • Someone already knows many command/shortcuts but don't know which one they don't know that will increase his efficiency.
  • Get insight from inefficient usage (e.g. from data visualization).

The question to solve is: Which are the most important commands/shortcuts/features to learn/discover that will most effectively increase my productivity and efficiency?

Having the activity tracked will allow building an extension that:

  • Have a view that filter out the command already known.
  • The view shows a list of the commands/shortcut never used.
  • The view order the commands/shortcuts/feature by their relationship with the one I already use.

Conclusion

To allow this kind of improvements, it is required to add a tracking feature of the activities and expose them through the API.

What are other benefits can you think of from tracking activities and exposing them in the API?

@jrieken
Copy link
Member

jrieken commented Mar 10, 2019

/duplicate of #26729

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 10, 2019
@vscodebot
Copy link

vscodebot bot commented Mar 10, 2019

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Mar 10, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

2 participants