ChromeXt
ChromeXt copied to clipboard
Improve Userscript Manager Front End
I have a couple suggestions for improving the front end: • make deleting scripts deletes instantly rather than refreshing the page • add @description @version section under the script • add ability to import Userscript from link/file • add @updateUrl ability for auto updating the Userscript • add backup/restore ability These are just suggestions not necessarily important and doesn't effect the performance but hopefully you add them
Partially done in 6cb6cfb560b981525889a8d90f737c8a0516b8dc.
It is diffcult to support back/restore functions if we want to keep the app size less than 100k. Current size is 96k, I think it can then only be done in the front-end. Because font-end size is not counted into app ;)
I think it can then only be done in the front-end. Because font-end size is not counted into app ;)
I was thinking the same actually
@MohamadBayz I have some questions.
- Import UserScripts from link, what does it means? Which kind of links have you imported in other script manager?
- Auto-updating function is tricky, it requires me to download the script each time for checking updating. Maybe this is not necessary.
For your first question, Tamper monkey has that feature where you can type the UserScript's direct link to install it, but since we can just paste the link in The browser and install it then it's probably not needed. For the second question if that's the case then i agree that would effect the performance of the module and it better to not have it. Sorry for late reply :)
I would like to see a feature on the list which adds a enable/disable button per script. So you don't need to delete it. This would bei useful if you wanna test and/or edit scripts.
I would like to see a feature on the list which adds a enable/disable button per script. So you don't need to delete it. This would bei useful if you wanna test and/or edit scripts.
Usually, I disable a script by changing its matching / excluding rules.
I would like to see a feature on the list which adds a enable/disable button per script. So you don't need to delete it. This would bei useful if you wanna test and/or edit scripts.
Usually, I disable a script by changing its matching / excluding rules.
I do it like that too, but I think it would be faster and more convenient to have a toggle/button.
adds a enable/disable button per script.
Good suggestion!
-
Great project! Much needed! Seems that the list of features to do is long...
-
Frontend management of ChromeXt and userscripts/extensions would be great :)
-
Adblocking: ad to block AMP ads and also "sponsored" ads (like in Reddit and Google search)
-
Kiwi browser for android supports all Chrome Web Store extensions, it's open dource.
-
Firefox for Android is getting open extensions ecosystem later this year
@G-D-B-9-9 For AD blocking, see my opinion at #124 In 2023, I cannot finish the support of extension. Let us wish that it can be done in the next year.
@Retardium I can implement a temporary blocklist of UserScript so that in the current browser session the enable / disable is working well. Do you think it will be helpful for you? I suggest so because a permanent enable / disable requires me to the change data structure of UserScript in ChromeXt.
I would like to see a feature on the list which adds a enable/disable button per script. So you don't need to delete it. This would bei useful if you wanna test and/or edit scripts.
Yes. So boring to delete! When you could turn off/on :)
It is diffcult to support back/restore functions if we want to keep the app size less than 100k. Current size is 96k, I think it can then only be done in the front-end. Because font-end size is not counted into app ;)
Violentmonkey from CWS is only about 500KB whereas Tampermonkey/ is 4-5MB.
@G-D-B-9-9 For AD blocking, see my opinion at #124 In 2023, I cannot finish the support of extension. Let us wish that it can be done in the next year.
Kiwi mobile browser has put out their Chrome extensions fork. Lemur browser copied it.
But FF android stable is getting the full AMO access later this year. Other than that mobile browsers and extensions progress slowly.
What I do know is that Vivaldi has recently considered ext support but dunno maybe they did a roadmap? Then again Vivaldi (on desktop) is full of features and options and customizations that they might push it to mobile. Anyhow - Opera and Brave (esp. Opera) take what they can from Vivaldi's published code and make gimmicky versions - lot's of colorful icons and details and many times commercial partnerships/promotions over deep well though excellent features.
@Retardium I can implement a temporary blocklist of UserScript so that in the current browser session the enable / disable is working well. Do you think it will be helpful for you? I suggest so because a permanent enable / disable requires me to the change data structure of UserScript in ChromeXt.
Hello, thank you. Yes, this would be definitely a big help. 👍
I can't get the front end to show up when i visit the pages on the readme, all I get is a message that it's working