Utkarsh Sinha
Utkarsh Sinha
@michascholl Did you ping him? I can see this being a very useful feature.
Everything "seems" to work - the output is definitely wrong. I think I'll have to recheck the math that goes on for each frame.
I get alphamaps that "resemble" the ground truth i some vague way. Definitely need more research on the gaussian model generated for each pixel.
Tried this on master commit 0330934c8bf932 and could not reproduce this.
I think we should have the .map file at the same location as the generated CSS file. This keeps things consistent and the configuration easier to read. ``` ... files:...
Okay - so the .map should be generated at the same location as the CSS by default - but we need some mechanism to put .map files in another location.
I looked into this for a bit today and here are my findings. grunt-contrib-sass depends on Ruby's `sass` executable. Version 3.4 of this executable has support for generating sourcemaps -...
Here's what I have right now: ``` module.exports = function(grunt) { grunt.initConfig({ sass: { options: { sourcemap: 'auto', sourcemapDest: 'something/other/' }, dist: { files: { 'something/test.css': 'custom.scss' } } }...
I exposed a file name flag in the `sass` binary on my local machine. Let's see if this gets accepted into Sass. https://github.com/liquidmetal/sass/commit/5bfe9ccd09d6ae056b83ce9ec2842fb1472d8f55 If it does, we can have a...
Awaiting on https://github.com/sass/sass/pull/1844 to proceed.