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

A different way of handling custom Java Scripts #259

Open
bouncepaw opened this issue Dec 3, 2024 · 0 comments
Open

A different way of handling custom Java Scripts #259

bouncepaw opened this issue Dec 3, 2024 · 0 comments

Comments

@bouncepaw
Copy link
Owner

It was pointed out in #258 that the way custom scripts are configured makes little sense.

See https://mycorrhiza.wiki/help/en/config_file#CustomScripts

My idea was to support both internal and external scripts, that's why this URL-based approach made sense. Now, I'm not sure anybody really uses the external scripts, also, it's not a good idea to use them anyway.

I'm thinking of a filesystem-based approach instead. Something like:

wikidir/
   scripts/
      common/
         ...
      view/
         ...
      edit/
         custom-btns.js

Perhaps it should be part of static/, similar to how custom CSS is applied. Also, sounds like a great opportunity to rethink the JS API. I remember some thought being put into the shortcuts so that they could be extended by custom scripts. Nobody does that, probably.

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

No branches or pull requests

1 participant