mindful_sass 0.0.2 → 0.0.3

Sign up to get free protection for your applications and to get access to all the features.
Files changed (1) hide show
  1. metadata +23 -24
metadata CHANGED
@@ -1,7 +1,7 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: mindful_sass
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.0.2
4
+ version: 0.0.3
5
5
  prerelease:
6
6
  platform: ruby
7
7
  authors:
@@ -12,32 +12,31 @@ bindir: bin
12
12
  cert_chain: []
13
13
  date: 2011-08-01 00:00:00.000000000Z
14
14
  dependencies: []
15
- description: ! "\n Sass or the much better approach of scss is really helpful and
16
- a big silver bullet for my css structuring in \n ruby projects.\n \\n\\n \n
17
- \ Standard sass command works for whole directories or single files only. In general
18
- it gets the jobs we want done, \n but in practical usage i think the sass command
19
- tool is a little bit unconvinient. A common scenario for me is, \n that you have
20
- whole bunch of sass files, which you want to compile to a single compressed output
21
- file.\n But if you have splitted your sass files in component based modules and
22
- you want to watch the complete folder you \n have to care for dependency handling
23
- in each file, because each file will be compiled for its own.\n \\n\\n\n # compiling
24
- a complete folder with scss\n ~ $ sass css/scss:css/compiled\n \\n\\n\n So
25
- converting the whole folder is not what i want, because i don\\'t want to import
26
- for example my color.sass config file\n in each module again. Compiling a single
27
- file seems to be the better solution, and it works in general, as expected,\n but
28
- the devil is in the detail. \n \\n\\n\n # compiling a single file where the
29
- other files are imported.\n ~ $ sass css/scss/main.scss:css/compiled/main.css\n
30
- \ \\n\\n\n If we change a file with impact to our main.sass file, the --watch
15
+ description: ! "\n <p>Sass or the much better approach of scss is really helpful
16
+ and a big silver bullet for my css structuring in \n ruby projects.</p>\n \n
17
+ \ <p>Standard sass command works for whole directories or single files only. In
18
+ general it gets the jobs we want done, \n but in practical usage i think the
19
+ sass command tool is a little bit unconvinient. A common scenario for me is, \n
20
+ \ that you have whole bunch of sass files, which you want to compile to a single
21
+ compressed output file.\n But if you have splitted your sass files in component
22
+ based modules and you want to watch the complete folder you \n have to care for
23
+ dependency handling in each file, because each file will be compiled for its own.</p>\n
24
+ \ \n <pre># compiling a complete folder with scss\n ~ $ sass css/scss:css/compiled</pre>\n
25
+ \ \n <p>So converting the whole folder is not what i want, because i don\\'t
26
+ want to import for example my color.sass config file\n in each module again.
27
+ Compiling a single file seems to be the better solution, and it works in general,
28
+ as expected,\n but the devil is in the detail. </p>\n \n <pre># compiling
29
+ a single file where the other files are imported.\n ~ $ sass css/scss/main.scss:css/compiled/main.css</pre>\n
30
+ \ \n <p>If we change a file with impact to our main.sass file, the --watch
31
31
  handle will not get it, because it observes only\n the timestamp of the given
32
- main.sass.\n \\n\\n\n Here is it, where mindful_sass tries to help out. You
32
+ main.sass.</p>\n \n <p>Here is it, where mindful_sass tries to help out. You
33
33
  use it according to the single file variant of \n sass, but it tries to observe
34
34
  the whole folder the given sass file is placed. If a timestamp of file in the sass
35
- folder\n or its children changes it will compile the specified main.sass again.\n
36
- \ \\n\\n\n This gem is not aimed to replace anything in the sass universe. It
37
- is only a wrapper to avoid the described unconvinience, \n and i hope that it
38
- gets useless as fast as possible, because the sass development gets this feature
39
- done for themselves.\n \\n\\n\n Thanks anyway to the sass developer team. \n
40
- \ "
35
+ folder\n or its children changes it will compile the specified main.sass again.</p>\n\n
36
+ \ <p>This gem is not aimed to replace anything in the sass universe. It is only
37
+ a wrapper to avoid the described unconvinience, \n and i hope that it gets useless
38
+ as fast as possible, because the sass development gets this feature done for themselves.</p>\n\n
39
+ \ <p>Thanks anyway to the sass developer team.</p>\n "
41
40
  email: info@systems-engineer.net
42
41
  executables:
43
42
  - mindful_sass