compass-sass

Sass looping through class names starting with number

倖福魔咒の 提交于 2019-12-01 12:33:20
I am looping through a list of names in sass and it seems that the sass is breaking when it arrives at a point where the class names starts with a number. Infact when i commented out the class names starting with a numeric value, the sass compilation worked fine. That said i cannot rename the class names. How I can make it work? Below is the code im trying: @each $car in bmwwhite hondared //22ltr-porche //30ltr-cossworth { .#{$car} { background:url(/img/cars/#{$car}.jpg) no-repeat } } HTML5 is fine with starting ID's and class names with digits these days, but CSS isn't ( Here's some info

Gulp can't seem to find compass mixins

时间秒杀一切 提交于 2019-12-01 12:27:15
I am trying out gulp as an alternative build tool to Grunt, to compile my scss to css, as I have heard it can be much faster. I having problems doing even a basic compile of my scss files. I have tried using the gulp-sass , gulp-ruby-sass and gulp-compass plugins for gulp and I get pretty much the same error message every time: error screen.scss (Line 2 of _grid.scss: Undefined mixin 'box-sizing'.) So it looks like it is falling down as soon as it hits a compass mixin. I have ruby installed on my PC with compass version 1.0.0.alpha.19 and sass version 3.3.7. Here is my gulpfile: var gulp =

Sass/Compass - Use variables for relative paths

℡╲_俬逩灬. 提交于 2019-12-01 12:04:15
Is it possible to use variables to set relative paths in Sass? I've tried to do it but just keep getting errors. In my admin css files I'm trying to avoid writing background(../../img/admin/img.jpg) for any images that need accessing from the css. I've tried writing something like $admin_img: '../../img/admin'; body { background: url($admin_img/background.png); } This code won't work and keeps saying that it expects ')' but found '.png);' Is it possible to set the paths using variables and how can it be done? Thanks I think you need to interpolate the variable: $admin_img: '../../img/admin';

Sass/Compass - Use variables for relative paths

落花浮王杯 提交于 2019-12-01 11:43:37
问题 Is it possible to use variables to set relative paths in Sass? I've tried to do it but just keep getting errors. In my admin css files I'm trying to avoid writing background(../../img/admin/img.jpg) for any images that need accessing from the css. I've tried writing something like $admin_img: '../../img/admin'; body { background: url($admin_img/background.png); } This code won't work and keeps saying that it expects ')' but found '.png);' Is it possible to set the paths using variables and

Susy grid - any (easy?) way to make 'columns' the same height?

点点圈 提交于 2019-12-01 10:53:56
问题 Getting my feet wet with Susy/sass/haml etc (using adjusted middleman - with latest susy from master branch) Have this in grid.css.scss @import 'susy'; $total-columns : 8; $column-width : 4em; $gutter-width : 0em; $grid-padding : $gutter-width; $break-max : 12; $container-style: magic; // Container .page { @include container($total-columns, $break-max); } // Layout .header { @include at-breakpoint($break-max) { @include pad(1,1); } } .pagenav { clear: both; @include at-breakpoint($break-max)

Sass @import directive when used in Rails engine can't find assets in plugins

孤人 提交于 2019-12-01 10:38:38
I was building a Rails engine that uses zurb-foundation's stylesheets, and kep hitting the same Sass::Syntax error. This seemed strange because I had followed the same procedure in a Rails application and it was worked on the first try. So I decided to zero in on the isse by starting two new rails projects--one application and one engine--and configure them to use foundation with a minimal amount of setup. I started with 2 clean Rails 3.2.9 projects--one application and one engine --full and configured them both manually for foundations by adding foundation_and_overrides.scss and require -ing

Weird misalignment in my Susy layout

☆樱花仙子☆ 提交于 2019-12-01 09:48:44
问题 The elements I set the Susy span-column() mixin to, do not obey to it. They are misaligned ever so slightly. How do I achieve perfect alignment of my HTML elements? Screenshot of full website misalignment Detail : <header> and <nav> misalignment Detail : <section class="main"> misalignment Here is my Sass code @import compass @import susy @import normalize /* Susy Settings */ $total-columns : 5 $column-width : 4em $gutter-width : 1em $grid-padding : $gutter-width $desktop : 12 /* Susy-grid

How to add DatePicker at JHipster UI

孤者浪人 提交于 2019-12-01 09:12:36
I want to modify one of JHipster entity page to use DatePicker . I Have include dependencies over Bower, add js library url to index page. I'm not sure how to include bootstrap css, should I use compass or something else? Or do you maybe know better library for UI. I added it to my project using WebJars: <dependency> <groupId>org.webjars</groupId> <artifactId>bootstrap-datepicker</artifactId> <version>1.3.1</version> </dependency> Then I use class="date" on my date fields and use the following HTML/JS to initialize the field. <link rel="stylesheet" type="text/css" media="all" href="/webjars

Compass taking too long to compile

别来无恙 提交于 2019-12-01 08:36:43
Since updated to the latest version of Compass it now takes 4.294s to compile. I need this version of compass due to needed susy Running "sass:dist" (sass) task Running "watch" task Completed in 4.294s at Tue Sep 30 2014 23:38:01 GMT+0200 (W. Europe Daylight Time) - Waiting...` // Running versions compass -v 1.0.1 susy -v 2.1.3 sass -v 3.4.4 I compile with grunt: sass: { dist: { options: { style: 'compressed', require: 'susy', compass: true }, files: { '<%= yeoman.css %>/style.css': '<%= yeoman.sass %>/style.scss' } } } How can I speed up the compile time? Is it something wrong with my config?

Sass @import directive when used in Rails engine can't find assets in plugins

独自空忆成欢 提交于 2019-12-01 07:40:43
问题 I was building a Rails engine that uses zurb-foundation's stylesheets, and kep hitting the same Sass::Syntax error. This seemed strange because I had followed the same procedure in a Rails application and it was worked on the first try. So I decided to zero in on the isse by starting two new rails projects--one application and one engine--and configure them to use foundation with a minimal amount of setup. I started with 2 clean Rails 3.2.9 projects--one application and one engine --full and