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

With font-awesome, I want weppy-assets copy fonts folder automaticly #2

Open
laozhu opened this issue Apr 3, 2016 · 3 comments
Open

Comments

@laozhu
Copy link

laozhu commented Apr 3, 2016

Font-Awesome will read ../fonts/xxx.otf in font-awesome.min.css file, but weppy-assets can't copy fonts folder in assets to static/out automaticly. I think weppy-assets lacks some functions dealing with images and fonts.

@gi0baro
Copy link
Owner

gi0baro commented Apr 3, 2016

This might be quite tricky. Maybe I can provide additional APIs to instruct weppy to copy some files from assets to static, but right now I've no idea about the syntax.

How would you expect to use it? Maybe something like this:

css = app.ext.Assets.css(
    'css/base.css',
    'css/theme.sass',
    'css/partial.scss',
    statics=['fonts/somefont.otf'],
    output="all.css").minify()

?

@laozhu
Copy link
Author

laozhu commented Apr 3, 2016

The above usage is well enough for me, I want to copy fonts or images in bower packages which I used. Recursive copy should be supported.

@gi0baro
Copy link
Owner

gi0baro commented Apr 3, 2016

Ok, I will think about this. In the meantime you can put everything related to font-awesome or other minified libraries in the static folder directly, avoiding to pass them to the assets extension (I usually do that) and including them in the template using include_static helper.

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

2 participants