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

Unify paths to plugin static files #566

Closed
redhog opened this issue Mar 21, 2012 · 3 comments
Closed

Unify paths to plugin static files #566

redhog opened this issue Mar 21, 2012 · 3 comments

Comments

@redhog
Copy link

redhog commented Mar 21, 2012

Currently javascript files are available at /javascripts/lib/PLUGINNAME/static/js/.... other static files are available at /static/plugins/PLUGINNAME/static/... this is not very obvious...

@marcelklehr
Copy link
Contributor

How about implementing one of the following... ?

httpfsexample
/static/<plugin>/*path/to/<plugin>/static/*http://ether.pad/static/ep_apples/js/foo.js
/static/<type>/<plugin>/*path/to/<plugin>/static/<type>/*http://ether.pad/static/js/ep_apple/foo.js
/static/plugin/<plugin>/*path/to/<plugin>/*http://ether.pad/static/plugin/ep_apple/js/foo.js
/static/lib/<plugin>/*path/to/<plugin>/*http://ether.pad/static/lib/ep_apple/js/foo.js

@cweider
Copy link
Contributor

cweider commented Sep 3, 2012

I think mapping /javascripts/lib/:plugin_name/ to path/to/<plugin>/static/js/. Addressing the JS module through static does work, but it precludes (useful, though unimplemented) packaging. The inclusion of /static/js in the paths would be great to get rid of (though simply placing files in the module’s root directory may make more sense).

@JohnMcLear
Copy link
Member

Closing because it would be a breaking change for little gain.

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

No branches or pull requests

4 participants