and should be accessible to the webserver. By default the fonts directory
is the "fonts" subdirectory of the css directory but another location
can be set via the fonts_dir and http_fonts_dir configuration options.
* edge:
Fix test failure.
[Blueprint] Fixed clipping of ordinals for IE in an ordered list.
[Blueprint] When using the RTL plugin, columns are now text-align:right.
[Blueprint] Add visibility:hidden to hr.space and +colspacer so it's useful outside of white backgrounds
Fix grid builder to properly generate png
[Blueprint] Password inputs now the same style as regular text inputs
[Tests] Process expected result files thru erb to account for more transient behaviors across different systems.
fix broken test.
Don't use methods not available in ruby 1.8.6
Changes for blueprint commit 9be685760014b3258dcd83913b9b19f130551b2f
* edge: (118 commits)
Make the tests pass in ruby 1.9
Fix a bug in FSSM for ruby 1.9. Closes GH-48.
Version bump to 0.9.4
Update the TODO.
If a template provides a haml file, it can have compass-enabled sass filters within it.
Allow vendored frameworks to override built-in frameworks to enable
[Rails] Allow compass extensions to be stored in the vendor/plugins/compass/extensions directory.
Fix some issues regarding how the project type configuration gets applied.
Don't leave directories around after testing.
Name all configuration sources for debugging purposes.
[Command Line] Primary commands get special status in the initial help output.
[Command Line] Access the Sass Repl (sass -i) with the compass environment loaded.
Separate the project type default configuration from the installer.
Add config/compass.rb as a known config location. Default to config/compass.rb as the configuration file for rails projects.
Fix a bug when the welcome message was not provided by an extension template.
Version bump to 0.9.3
Starting work on the changelog for 0.10
Stuff that needs to be done before the next release.
Help for each template that ships with compass.
Allow the welcome message to replace the default one instead of just augment it.
...
Conflicts:
CHANGELOG.markdown
VERSION.yml
compass.gemspec
lib/compass/configuration.rb
lib/vendor/fssm.rb
lib/vendor/fssm/state.rb
All application specific behavior is now centralized within the app integration modules.
Plugins can now provide app integration using the --app command line option and by adding the appropriate classes to the compass module tree.
* master:
[Blueprint] Add mixins for +prepend-top and +append-bottom and corresponding grid classes when generating the css grid classes.
Use FSSM by Travis Tilley to monitor for filesystem changes. On mac this will use filesystem events instead of polling. Fixes an infinite looping issue when compilation errors occur.
frameworks by passing a directory that contains those frameworks. Each
framework can choose to adhere to the naming convention of providing a
'stylesheets' directory and a 'templates' directory, or it can register
itself by providing a ruby file at one of the following locations:
<plugin>/compass_init.rb
<plugin>/lib/<plugin>.rb
<plugin>/<plugin>.rb
The first file found in the above order will be required. The framework
should register itself there using the Compass::Frameworks.register method.
configuration. Configuration is now a singly linked list of configuration objects
that inherit values and defaults from the next configuration instance.
All instances hold a reference to the top of the configuration chain.
There is now a consistent API for reading configuration property values:
<attr>: Reads the fully-resolved attribute after taking
configuration inheritance and defaults into account.
raw_<attr>: reads attribute from a configuration object without
inheritance or defaults.
default_for(<attr>): reads the default value for an attribute
default_for_<attr>: specifies the default value for an attribute.
<attr>_without_default: reads the inherited attribute without applying defaults.
comment_for_<attr>: Specifies a comment that will be emitted above the
property when serializing the configuration to a file.
Additionally, method_missing and respond_to both work down the
configuration chain, so any method that is added to a configuration
instance, can be accessed from the top level.
The distinction between default and explicitly set values allows compass
to more correctly manage the serialization of attributes when creating
configuration files for projects.
The compass configuration can still be accessed via
Compass.configuration, however, the configuration object is no longer a
singleton. This means that you can build several configuration chains
to track several projects at once. This should ease the use of compass
in other frameworks and plugins that want to use compass internally.
