search

blackfalcon / fontcustom.sass

Toadstool/Sass version of the fontcustom application
4 stars 1 forks source link

Separate Sass output #1

Open blackfalcon opened 11 years ago

blackfalcon commented 11 years ago

Right now the @font-face CSS and the silent placeholders are output into a single file.

I would like to have these output into separate files so that customizations to the output could be preserved. As of now, if you edit the Sass file and then run the fontcustom app, the Sass file will be over-written.

Zarabadoo commented 11 years ago

Would it make sense to roll some of this into an initialization mixin along with some !default variables? This would be something like how Compass handles vertical rhythm. It uses a bevy of default variables that are referenced with the establish-baseline() mixin.

Something similar could be done with this to declare the paths (I do not use the same directory structure this outputs) and class names for the links (I find "icon" a bit too generic). It would also allow a person to include the output as a library without the css at the top of the file. Then the css could be output exactly where the developer wants it. It will allow for tidier final output and make it so that the file does not have to he edited.

The downside is that this would not "just work", but it would be more flexible and useable in more application environments.