support for other extensions than .css and .js

faassen / bowerstatic

Serve Bower-managed static resources using WSGI

BSD 3-Clause "New" or "Revised" License

49 stars 17 forks source link

support for other extensions than .css and .js #11

Closed faassen closed 10 years ago

faassen commented 10 years ago

This takes two forms:

API to let developer add in other renderers (such as a link tag, script tag) for other extensions than .js and .css
support out of the box for a variety of those extensions where we can think of a sensible way to support them.

faassen commented 10 years ago

Some examples from the bootstrap main:

"dist/fonts/glyphicons-halflings-regular.eot", "dist/fonts/glyphicons-halflings-regular.svg", "dist/fonts/glyphicons-halflings-regular.ttf", "dist/fonts/glyphicons-halflings-regular.woff"

What does it even mean to include some of these? I think we also need to ignore extensions we can't deal with in the case of 'main'.

faassen commented 10 years ago

I've implemented the API now and ignore unknown extensions in main. I'll keep this issue open to collect extensions we want to always support.

mrijken commented 10 years ago

Fonts does not need to be included, because they are imported via css.

faassen commented 10 years ago

We do want to support a default for .ico, right?

mrijken commented 10 years ago

Yes, I think we should provide a default favicon renderer for all image types which can be used as favicon (see http://en.wikipedia.org/wiki/Favicon#File_format_support).

2014-11-11 10:44 GMT+01:00 Martijn Faassen notifications@github.com:

We do want to support a default for .ico, right?

— Reply to this email directly or view it on GitHub https://github.com/faassen/bowerstatic/issues/11#issuecomment-62523852.

faassen commented 10 years ago

@mrijken contributed quite a few, so I'll close this.