-
Notifications
You must be signed in to change notification settings - Fork 52
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
[Feature request] browser plugins #79
Comments
I'm not familiar with what is allowed or possible for browser plugins. For integrating with gtm it would be easy enough to call the CLI from a browser plugin. However, I am working on new feature for application monitoring. So stay tuned :). |
The problem with calling the CLI is I don't believe browser plugins are allowed to execute arbitrary commands-- they're generally written in JS and contained at the browser level, and very specific on allowed permissions. Application monitoring is also a gigantic plus, however if splitting the timing at the webpage level, this would allow the user to see where his time is actually spent in working on the project (SO/SE, the docs of the language, misc, or procrastination). |
One possible solution would be that gtm runs a lightweight local HTTP server that accepts The browser extensions can then simply {"site": "https://github.com/project-related/repo", "repo":"~/my-project"} Upon receiving such request Here EDIT: Another "Enterprise" use case of this feature would be that companies can host and run the |
We did consider this approach and it does have advantages. But we decided early on to have GTM be a command line tool and not a server. However you could create a HTTP server that uses GTM. That might be a good option to try. |
I'm putting this would also mean a valid way to import/export time in some special file format.
A simple "on/off" switch and export import system would work, tracking time spent.
Bonus points for tracking history of websites or domains themselves per page, and allowing this to be expanded/contracted in the report. If websites, POST requests and don't track paramaters/fragments for security purposes.
I'd say do this for Chrome, Firefox, maybe opera/safari/edge.
Of course, screw IE-- that's the only browser that would require a completely different codebase (in a different language even) whereas the others would be the same major codebase with only a few changes for different browser APIs
The text was updated successfully, but these errors were encountered: