Greasemonkey and Tampermonkey User Scripts

[miztizm]

Preflight Checklist

• [X] I have read the Contributing Guidelines for this project.
• [X] I agree to follow the Code of Conduct that this project adheres to.
• [X] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

The current solution for user.css and user.js is mediocre

Proposed Solution

If we can implement the Greasemonkey and Tampermonkey structure of scripts and create a simple manager for those scripts , we could user a css and and js in one place with already dozen of scripts and architecture

Alternatives Considered

• implement chrome extensions
• modify the current implementation with better scripts and styles management

Additional Information

• Implement Chrome extensions, altering the current setup
• improved scripting and styling management.

[victorbnl]

The scope of what you are suggesting is pretty large, and it will not be an easy task to deal with it. Plus, what you’re asking for is vague. “Implementing a simple manager” is already a lot of work by itself. What exact features are you missing? Also, it would help if you provided the use case.

In case you just want to be able to write scripts in different files, why not make it possible to have a folder from which every script is loaded?

we could user a css and and js in one place with already dozen of scripts and architecture

I never really used Greasemonkey so I don’t know how it differs from pure javascript, but what prevents you to use the current scripts by putting them in the user.js?