mindful_sass 0.0.1 → 0.0.2

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