chriseppstein / compass
- Source
- Commits
- Network (73)
- Issues (13)
- Downloads (34)
- Wiki (48)
- Graphs
-
Branch:
master
-
Blueprint Form Style Not Applied to Password Fields
1 comment Created 15 days ago by threadheadIn 'frameworks/blueprint/stylesheets/blueprint/modules/_form.sass' consistant input styling is not applied to password fields.
line 24:
--- &.text, &.title, &[type=text] +++ &.text, &.title, &[type=text], &[type=password]Comments
-
Sass SyntaxError: Undefined Variable... but it still works fine
6 comments Created 29 days ago by gpbmikeThis is just more of an annoyance since it works anyway.
overwrite media/vine/css/skin_black.css Sass::SyntaxError on line 7 of /Users/gpbmike/vines/sass/././_default.sass: Undefined variable: "!primary_copy_color".I'm pretty sure it has to do with the way I'm importing files.
skin_black.sass: defines color variables, imports base.sass at the end
base.sass: imports a bunch of things, including default.sass
default.sass: uses !primary_copy_color variable
I can change !primary_copy_color in skin_black.sass and it shows up fine in skin_black.css, so I probably shouldn't be getting the error.
I don't get the error if I use
sassto compile instead ofcompass -w.Comments
chriseppstein
Wed Dec 02 17:37:04 -0800 2009
| link
Can you post the relevant bits of the files to a gist and link it here, from this description I can't diagnose the issue.
You got it! http://gist.github.com/247826
chriseppstein
Wed Dec 02 19:54:42 -0800 2009
| link
I had to move the comment, but once I did that I get the following:
$ compass exists stylesheets compile src/skin_black.sass create stylesheets/skin_black.css $ compass -v Compass 0.10.0 [2465bab] Copyright (c) 2008-2009 Chris Eppstein Released under the MIT License.As you can see, it works fine. Perhaps you can tell me more about your environment? Are you using compass stand alone or with another framework?
I'm going to see if I can reproduce it without my crazy huge files.
Chris, I found the problem. For some reason I had a vine.sass and a vine.sass that were identical. They were both importing default.sass so when I saw the error I didn't realize it was being generated from vine.sass. I removed vine.sass and everything is right in the world again.
Sorry to bug you!
chriseppstein
Thu Dec 03 10:58:38 -0800 2009
| link
glad you got it sorted out.
-
=dquo(!offset = 0.5em) margin-left: -!offset
margin-left: -!offset should be margin-left= -!offset or margin-left: #{-!offset}
Comments
chriseppstein
Tue Dec 01 01:57:14 -0800 2009
| link
Thanks. I'll get that into the next release.
chriseppstein
Thu Dec 03 00:55:01 -0800 2009
| link
[Blueprint] Bug Fix: variable referenced in a non-script context within the dquo mixin in the fancy_type module. Closed by 5f32043.
-
required libraries are not automatically inserted into the config file
1 comment Created about 1 month ago by chriseppsteinThe command line option
-r libraryshould causerequire 'library'to be in the configuration file.Comments
chriseppstein
Tue Dec 01 00:05:47 -0800 2009
| link
fixed.
-
`exception_to_css' method does not exist on Sass::SyntaxError:Class
1 comment Created about 1 month ago by chriseppsteinIt's only in haml edge. Need to either get this into stable haml or monkey patch sass...
Comments
chriseppstein
Mon Nov 30 20:55:31 -0800 2009
| link
fixed by f1bb236
-
line comments don't get turned off from the configuration file setting.
1 comment Created about 1 month ago by chriseppsteinFrom this mailing list thread:
http://groups.google.com/group/compass-users/browse_thread/thread/9a030ab76c0cc436?hl=enComments
chriseppstein
Tue Dec 01 00:05:41 -0800 2009
| link
fixed. turns out you couldn't effectively set any boolean property to false.
-
_reset.css body line-height should not be in ems
3 comments Created about 1 month ago by gpbmikeShould be:
line-height: 1;Not:
line-height: 1em;see http://meyerweb.com/eric/thoughts/2007/05/01/reset-reloaded/
Comments
chriseppstein
Mon Nov 30 12:06:38 -0800 2009
| link
Interesting. Aren't these the same?
I thought they were the same too until just now. I changed it from 1em to 1 in firebug and saw the computed line-height change from 12px to 24px which is what I had expected. Learn something new every day.
chriseppstein
Mon Nov 30 22:54:04 -0800 2009
| link
fixed. Thanks for the patch.
-
I've found that in several of my projects I've had trouble with compass seeing my configuration changes unless I manually clear my .sass-cache directory. Also when I'm running Compass watch, changes to the config file do not cause the sass to be recompiled. This seems like an oversight, because most of the configuration options would necessitate a rebuild. I often have to kill the watch process to run the update, and then re-run watch.
I think this seems like something that should be taken care of by Compass. I would assume that the desired behavior would be that an update to the configuration would cause the .sass-cache to be cleared upon the next recompile. I also feel that Compass watch should pay attention to the config file.
Comments
johnthedebs
Mon Nov 30 10:42:02 -0800 2009
| link
I was thinking about this just yesterday - I'll second this motion.
chriseppstein
Mon Nov 30 12:07:43 -0800 2009
| link
I will talk to nathan about whether this is a sass or compass bug.
chriseppstein
Tue Dec 01 10:35:15 -0800 2009
| link
If the configuration file changes, wipe out the sass cache and force
compilation. Closed by 3bb5e6d.
chriseppstein
Tue Dec 01 13:06:59 -0800 2009
| link
Not a sass bug. When the configuration changes, there's no way for Sass to know that the function calls will generate different results. At first, I thought this bug and the one related to line_comments might be related via a root cause in sass, but no.
-
On edge compass, if I follow the instructions in examples/README and run "rake examples" at project root, I get an error "wrong number of arguments (0 for 1)", here's the full traceback with --trace
carljm@kale:~/projects/compass/compass$ rake examples --trace (in /home/carljm/projects/compass/compass) rake aborted! wrong number of arguments (0 for 1) /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:31:in `index' /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:31:in `register' /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:60:in `register_directory' /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:46:in `discover' /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:45:in `each' /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:45:in `discover' /home/carljm/projects/compass/compass/lib/compass/frameworks.rb:92 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/carljm/projects/compass/compass/lib/compass.rb:21 /home/carljm/projects/compass/compass/lib/compass.rb:20:in `each' /home/carljm/projects/compass/compass/lib/compass.rb:20 /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `gem_original_require' /usr/local/lib/site_ruby/1.8/rubygems/custom_require.rb:31:in `require' /home/carljm/projects/compass/compass/Rakefile:16 /usr/lib/ruby/1.8/rake.rb:2149:in `load' /usr/lib/ruby/1.8/rake.rb:2149:in `raw_load_rakefile' /usr/lib/ruby/1.8/rake.rb:1897:in `load_rakefile' /usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling' /usr/lib/ruby/1.8/rake.rb:1896:in `load_rakefile' /usr/lib/ruby/1.8/rake.rb:1880:in `run' /usr/lib/ruby/1.8/rake.rb:1948:in `standard_exception_handling' /usr/lib/ruby/1.8/rake.rb:1878:in `run' /usr/bin/rake:28Quite likely this is just because I have a crazy-out-of-date rake; I'm not a Ruby dev and don't really ever use it. Thought it was worth reporting anyway.
carljm@kale:~/projects/compass/compass$ rake --version rake, version 0.8.1Comments
chriseppstein
Mon Nov 23 13:52:35 -0800 2009
| link
What version of compass?
Well, I have compass 0.8.17 installed globally, but from the traceback it appears to be using the git checkout I'm in, not the global gem. The checkout is from here http://github.com/ericam/compass/tree/edge (testing Eric's Susy example); based on a checkout of your edge as of this morning.
chriseppstein
Mon Nov 23 14:55:59 -0800 2009
| link
Eek. the issue is that I'm using a form of Array#index that only exists in ruby 1.8.7+
chriseppstein
Mon Nov 23 15:17:10 -0800 2009
| link
I pushed a change to my edge branch
-
Hey Chris !
It looks so easy (http://gemcutter.org/pages/create) how about switching ?
Thanks for your great work on Compass and Sass !
Later,
-- Arnaud
Comments
chriseppstein
Fri Nov 20 08:01:48 -0800 2009
| link
-
Stack trace:
$ compass --config=src/sass.rb --trace my_project NameError on line 68 of /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/commands/project_base.rb: undefined local variable or method `file' for #<Compass::Commands::CreateProject:0x5a3c00> /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/commands/project_base.rb:52:in `read_project_configuration' /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/commands/installer_command.rb:9:in `configure!' /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/commands/project_base.rb:18:in `execute' /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/exec.rb:242:in `do_command' /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/exec.rb:57:in `perform!' /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/lib/compass/exec.rb:40:in `run!' /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.8.17/bin/compass:8 /usr/bin/compass:19:in `load' /usr/bin/compass:19Comments
-
I wanted to give it a shot and ran with the rails template using:
rails -m http://compass-style.org/rails/installerand did worked successfully.
Now I am installing in my existing project which is already hamlified.
So I ran the following rake command:
rake rails:template LOCATION=http://compass-style.org/rails/installerand now the execution halts and does nothing as the following
[~/rails_apps/myapp (design)âš¡] âž” rake rails:template LOCATION=http://compass-style.org/rails/installer (in /home/millisami/rails_apps/myapp) applying template: http://compass-style.org/rails/installer =================================================== Welcome to the Compass Installer for Ruby on Rails! =================================================== What CSS Framework do you want to use with Compass? (default: 'blueprint') 960 Where would you like to keep your sass files within your project? (default: 'app/stylesheets') Where would you like Compass to store your compiled css files? (default: 'public/stylesheets/compiled') gem haml gem chriseppstein-compass rake gems:install GEM=haml rake gems:install GEM=chriseppstein-compass rake gems:unpack GEM=chriseppstein-compass gem chriseppstein-compass-960-plugin rake gems:install GEM=chriseppstein-compass-960-plugin rake gems:unpack GEM=chriseppstein-compass-960-plugin file vendor/plugins/compass/init.rb executing haml --rails . from /home/millisami/rails_apps/myappI tried couple of time and its the same. Is it due to my already hamlified app?
Comments
-
I keep getting an error when running the watch script on ruby 1.9.1.
I'm using version 0.8.17
Compass is watching for changes. Press Ctrl-C to Stop. TypeError on line ["969"] of /System/Library/Frameworks/Ruby.framework/Versions/1.9.1/lib/ruby/1.9.1/pathname.rb: can't convert Pathname into String
Run with --trace to see the full backtraceI have traced it to the following:
Basically what's failing is
Pathname.glob(Pathname.new('/Users/bryan/Sites/ushaf/public/src/**/*.sass'))(fails in irb as well) The pathname is passed in, I just used Pathname.new to test
but Pathname.new('/Users/bryan/Sites/ushaf/public/src/**/*.sass').to_s works fine.
If I change vendor/fssm/state.rb from
def add_glob(base, glob) Pathname.glob(base.join(glob)).each do |fn| @cache.set(fn) end endto:
def add_glob(base, glob) Pathname.glob(base.join(glob).to_s).each do |fn| @cache.set(fn) end endThere is no longer a problem, but I'm not sure why.
the trace...
/System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/1.9.1/pathname.rb:969:in
glob' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/state.rb:49:inadd_glob' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/state.rb:45:inblock in snapshot' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/state.rb:45:ineach' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/state.rb:45:insnapshot' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/state.rb:37:inrecache' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/state.rb:9:inrefresh' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/backends/polling.rb:10:inadd_path' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm/monitor.rb:18:inpath' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/commands/watch_project.rb:26:inblock (2 levels) in perform' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/commands/watch_project.rb:25:ineach' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/commands/watch_project.rb:25:inblock in perform' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm.rb:19:incall' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/vendor/fssm.rb:19:inmonitor' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/commands/watch_project.rb:24:inperform' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/commands/base.rb:15:inexecute' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/commands/project_base.rb:19:inexecute' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/exec.rb:242:indo_command' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/exec.rb:57:inperform!' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/lib/compass/exec.rb:40:inrun!' /System/Library/Frameworks/Ruby.framework/Versions/1.9/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.16/bin/compass:8:in<top (required)>' /usr/local/ruby/bin/compass:19:inload' /usr/local/ruby/bin/compass:19:in `'Comments
I also encountered this problem. The fix works but it is also unclear to me why. I believe it might have something to do with the new Dir.glob method in 1.9
chriseppstein
Thu Nov 19 02:27:29 -0800 2009
| link
Fix a bug in FSSM for ruby 1.9. Closed by bad615e.
-
Use CSS-style properties instead of the old Sass-style properties
1 comment Created 3 months ago by chriseppsteinWe need to convert the compass sass code to use properties with colons that come at the end instead of the beginning of the property name.
Comments
chriseppstein
Thu Nov 19 01:46:38 -0800 2009
| link
-
enumerate outputs grid-1, grid-2, etc in the 960 plugin
Comments
chriseppstein
Thu Sep 24 09:07:31 -0700 2009
| link
[Compass Core] The enumerate function now accepts an optional argument to specify the separator. Closed by e0732c8.
chriseppstein
Thu Sep 24 09:12:45 -0700 2009
| link
Fixed. Please grab the latest versions of compass and the 960 plugin.
-
3 comments Created 3 months ago by chriseppsteinblueprintxUpgrade Blueprint to v0.9.1featurexBlueprint version 0.9.1 was recently released with the following changes:
9be68576 Fixing bugs, see Lighthouse for changes 414d9242 Add visibility:hidden to hr.space so it's useful outside of white backgrounds. 7cdabb82 Added PSD template to help with mockups c2493689 css_parser now uses Array#join instead of Array#to_s for ruby1.9 compat 74d7ecf9 Change CSS append order to put custom CSS after plugin CSS--allowing custom CSS to over-ride plug-in properties. 4d61d5db Changed custom CSS comment to file name instead of file path--removing the need to sanatize the CSS comment for security/privacy reasons. b881bf59 Fixed some typos in TUTORIAL.textile. e9e91bb9 When splitting on a colon for key/value CSS pairs, use first colon as the only split Signed-off-by: Joshua Clayton <jclayton@fusionary.com> eb58cdef Fix grid builder to properly generate png 0811b3d6 Allow for the specification of a non-default settings file via the command line in compress.rb d77e914e Password inputs got the same style as regular text inputs. 0f7588a5 Cleaned up whitespace in changelog; updated version numbers within stylesheets 05312a80 Updating authors one last time 2dd0d5ed Updating contributors, fixing grid.css 7e63ed3e Cleaning forms.html 3bf83f71 Test form whitespace cleanup bdd4568f Remove p tagCompass needs to merge these changesets into it's port.
Comments
chriseppstein
Tue Sep 08 17:52:11 -0700 2009
| link
This change should be part of the v0.10 release.
chriseppstein
Sat Nov 21 18:58:43 -0800 2009
| link
chriseppstein
Tue Dec 01 00:03:55 -0800 2009
| link
fixed in v0.10
-
Hi.
I noticed that compass' _forms.sass doesn't put the same css around input[type=text] & input[type=password] that Blueprint does. Blueprint has suff like (SHA: 63795c8):
input[type=text], input[type=password], input.text, input.title, textarea, select { background-color:#fff; border:1px solid #bbb; }whereas Compass has stuff like:
input.text, input.title, textarea, select :border= 1px "solid" !unfocused_border_color &:focus :border= 1px "solid" !focus_border_colorI can create an easy patch to fix this, but I just wanted to make sure that that the project aims to copy blueprint very closely and that this would be a wanted patch. Thanks!
Comments
chriseppstein
Tue Sep 08 17:49:34 -0700 2009
| link
That change was introduced as part of the v0.9.1 release of blueprint. Compass is currently at v0.9.0. I would like to update to blueprint v0.9.1 as part of the compass v0.10 release. If you'd like to help with that effort, let me know. I'll file a separate issue for the v0.9.1 upgrade.
-
Comments
chriseppstein
Thu Aug 27 13:30:32 -0700 2009
| link
This was recently brought up on the mailing list.
I will add it for the next release. Thanks!
chriseppstein
Sun Aug 30 11:55:29 -0700 2009
| link
fixed in 0.8.13 -- just released.
-
In trying to add compass to a rails project, I get some output that says...
= stylesheet_link_tag 'compiled/partials/_base.css'
However, that is in a directory that is under app. I was under the impressions that was to be mixed in, and I didn't need to link to it?
Or perhaps I totally misunderstand. If I misunderstand, I apologize, however if it is incorrect, it's confusing.
Thanks.
Comments
chriseppstein
Fri Aug 21 19:43:21 -0700 2009
| link
You're correct. That line is not needed. That it shows up is a bug.
I've fixed it on edge about a week ago and it will go out with the next release. Thanks for the report.
chriseppstein
Thu Aug 27 13:32:01 -0700 2009
| link
This was fixed in v0.8.12.
-
Sass compliation error produces inifite loop in Windows locking the sass file
2 comments Created 4 months ago by MarisicDotNetAnytime compass is set on watch mode and a sass file is updated that causes a sass compilation error compass will become locked in an infinite loop trying to compile the file. During this loop the file is locked for writing so it can never be fixed until ctrl+c is issued.
Comments
chriseppstein
Sun Aug 30 11:55:43 -0700 2009
| link
Fixed in 0.8.13. Just released.
MarisicDotNet
Mon Aug 31 09:52:29 -0700 2009
| link
I can confirm this issue is resolved.
-
11 comments Created 4 months ago by joshjhallbugxcompass corexBug: Found IE bug with inline-block mixinfeaturexAppended the last line to the current inline-block mixin to fix IE6 / IE7 display. Seems to be working fine for me, but might require additional testing.
=inline-block :zoom 1 :display inline :display -moz-inline-box :display inline-block :vertical-align top :*display inlineComments
chriseppstein
Sun Aug 16 16:46:13 -0700 2009
| link
That the +inline-block mixin doesn't work on block elements in IE6 & 7 is a known issue. If someone gives a well tested solution that works across a broad array of both inline and block elements, I will accept that patch.
However, I would encourage you to revisit the choice to use a block level element, in many cases a span is more semantically correct for an inline-block based layout.
please test my fix that was posted to the newsgroup.
=inline-block :display -moz-inline-box :-moz-box-orient vertical :display inline-block :vertical-align middle :#zoom 1 :#display inline // fixes alignment against native input/button on IE6 :#vertical-align auto
chriseppstein
Mon Aug 17 07:47:41 -0700 2009
| link
This implementation was also posted:
=inline-block :display -moz-inline-box :-moz-box-orient vertical :display inline-block :vertical-align middle :#display inline // fixes alignment against native input/button on IE6 :#vertical-align autoCan someone please explain why the
:#zoom 1style is needed or not?
chriseppstein
Mon Aug 17 07:53:00 -0700 2009
| link
I found this post on the subject. They use conditional comments to target IE < 8, is that what the # hack does?
rules with # will target IE6+7. rules with * will target IE6, but not 7. IE8 seems to have significantly more sane support of CSS in general... not only do the old hacks not work, but most of the time they aren't needed either.
as for the version you post second... the zoom is there to trigger hasLayout engine. inline-block in IE6+7 just triggers hasLayout for inline elements. you can achieve the exact same effect without using inline-block by making it display inline and then triggering hasLayout (like with zoom). that's why the hack works on both inline and block level elements, whereas inline-block in IE6+7 will only work for inline elements.
ah, i see what you mean with that post. what happens there only happens because it's in two separate css blocks. the first block sets it to inline-block, which triggers hasLayout. the second block sets it back to display inline, without un-triggering haslayout because it's done in a separate block. if it was one rule, that would not work. it would instead ignore the inline-block and use the inline statement... never triggering hasLayout.
in short, you can do without the zoom part only if you're using multiple css rules to do it. it our situation, this is not the case. you need the zoom.
chriseppstein
Mon Aug 17 08:11:50 -0700 2009
| link
Using
&in our mixin will allow us to generate two selectors that are the same. I use this trick in the +clearfix mixin. But it seems with any complex selector that would result in more generated css, not less.chris - use whatever technique you believe to be the most elegant solution. personally... i cheat. i cheat like crazy. i cheat either by using a rails plugin or dojo to add css classes to the html element representing what browser the client claims to be, what os, etc. it lets me avoid css hacks entirely without using conditional comments (which i would not be able to use to target firefox2, for example). it's unfortunate that such a solution is out of the scope of what sass, and compass, could provide. i mean... it makes the selectors themselves more specific, so you could theoretically run into problems. dojo's own inline-block hack is pretty much the same as the one i posted, without the additional firefox2 fix, so as to avoid css specificity issues.
chriseppstein
Mon Aug 17 08:44:35 -0700 2009
| link
I'm not looking for elegance. Just trying to find a reasonable balance in this effed up world of hacks that we live in. Thank you for your contribution and explanation. I think adding a class to the document body that indicates browser is a nice solution, but not general purpose enough.
chriseppstein
Thu Aug 27 13:32:30 -0700 2009
| link
I've merged a fix for this into my local edge. It will be part of the v0.10 release.
-
[bug] [core] Image files in plugin templates get corrupted, when copied into the app.
3 comments Created 4 months ago by kosmas58Issue
I've images included in the templates of a compass plugin. In manifest.rb I've written something
like:image 'jquery.ui/dynatree.base/cbChecked.png'When installing the template, the template is installed as described in manifest.rb, but the images are corrupt.
Possible reason
I think the issue occurs incompass/lib/actions.rb:
compass/lib/actions.rb: def copy(from, to, options = nil) ... contents = File.new(from).read write_file to, contents, options end def write_file(file_name, contents, options = nil) ... file.write(contents) ... endThis seems to break files with binary content.
Comments
chriseppstein
Sun Aug 16 10:09:21 -0700 2009
| link
grrrrr. Yes, that should write the file in binary mode...
chriseppstein
Sun Aug 16 11:23:40 -0700 2009
| link
Fixed in v0.8.10
chriseppstein
Mon Aug 17 13:06:43 -0700 2009
| link
I received a report that this bug still exists. Can you confirm or deny?
-
Is the
$stderr.puts "Loading haml-edge gem."in dependencies.rb necessary? If so, does it have to go to stderr? Why not stdout?
It's making all my cron scripts that send emails if there are any errors send me emails constantly...and every time I run tests or anything I see it too...
Thanks.
Comments
chriseppstein
Fri Jul 31 08:09:42 -0700 2009
| link
Now that we have Bundler, I think I can just make compass do a basic require of haml and leave what to load to the user...
-
blueprint_semantic examples missing class .left on the p img (dog)
1 comment Created 5 months ago by swingerbonethe image (of the dog) in the fancy_type and liquid blueprint_semantic example pages appears to be missing a class of .left - the style is there in the generated screen.css for body.blueprint p img.left - the version on compass-style.org applies the same styling to body.blueprint p img (so it defaults to floating an image in a paragraph to float left)
This has the effect of lacking the margin styles for the image (text butts against it) in fancy_type.html and without the float:left in liquid.html the image keeps the text from flowing around it.
I imagine this is a simple fix in the sass file - but I wanted to let you know.
Comments
chriseppstein
Mon Aug 03 09:52:51 -0700 2009
| link
Actually, this one is still just a css class that is scoped by a paragraph... I changed the markup.
-
Merb: overwrites existing :template_location setting
2 comments Created 5 months ago by merbjediCompass seems to overwrite any existing Merb::Plugins.config[:sass][:template_location] settings. This is fine if its set to a string, however, if its set to another hash, it should retain those mappings.
Comments
chriseppstein
Mon Aug 03 09:45:20 -0700 2009
| link
merged to edge for the next release.
-
The code generated from the blueprint module is incorrect, it generates the following CSS:
/* line 22, ../../../../../.gem/ruby/1.8/gems/chriseppstein-compass-0.8.8/frameworks/blueprint/stylesheets/blueprint/modules/_typography.sass */ body.bp body { line-height: 1.5; font-family: Helvetica Neue, Arial, Helvetica, sans-serif; color: #333333; font-size: 75%; }body.bp bodycan't be matched...Comments
chriseppstein
Sun Aug 09 21:46:36 -0700 2009
| link
fixed in v0.8.9
With a better fix in 0.10.0 coming.
adamsalter
Sun Aug 09 21:54:44 -0700 2009
| link
ok thanx ;)
-
Thanks for creating compass!
I have issue on ruby 1.9.1 and passing test:
http://pastie.org/559276Moreover I got the same issue as on the list: http://groups.google.com/group/compass-users/browse_thread/thread/e2d57f9d408343ea
Should I fork and fix the bugs or leave it to you?
Cheers, keep up good work!Comments
adamsalter
Sat Aug 22 02:39:46 -0700 2009
| link
I'm also getting these issues... Ruby 1.9.1p0
How long do we expect until this gets fixed?Hi, I fixed my problem and pushed up to my own master fork http://github.com/priit/compass/tree/master (I made fork only for fixing this bug). By the way, the fix are already pulled to chriseppstein edge branch, so you can use edge or my temporary master branch. Cheers!
chriseppstein
Thu Aug 27 13:31:28 -0700 2009
| link
I release the fix for this in v0.8.12. Please let me know if you're having any more issues with ruby 1.9.1
adamsalter
Thu Aug 27 20:54:48 -0700 2009
| link
seems to be working fine. sass files generate no problems.
chriseppstein
Thu Aug 27 20:55:49 -0700 2009
| link
:-D Great!
adamsalter
Thu Aug 27 21:05:39 -0700 2009
| link
One less ruby 1.9.1 bug to deal with ;)
... Actually it all works pretty well: db drivers - 'kwatch/mysql-ruby' and 'qooba/sqlite3-ruby' being major needed updates. ... and tempfile problem with passenger: http://www.taylorluk.com/articles/2009/08/12/ruby-19-and-passenger
Anyway cheers, ;)
-
compass doesn't work on windows out from the box
it shows up the error box "CORE_RL_magick_.dll not found"
Comments
chriseppstein
Tue Jul 28 07:48:58 -0700 2009
| link
I've had several reports that compass does work on windows. Please indicate the steps to reproduce this issue. What command are you running? What version of windows? Steps you followed to install compass?
Thanks
Hi, thanks for your feedback.
I finally spent some more time on this issue and find out a solution:
* Got to install ImageMagick manually (important: mark "add ImageMagick to system path" during install) * You have to install RMagik gem manually on windows instructions a there http://rmagick.rubyforge.org/best regards, Alex
chriseppstein
Mon Aug 03 09:34:18 -0700 2009
| link
closing. Hopefully google will help people find this issue if it affects them. Feel free to edit the wiki as you feel is appropriate.
-
The README @ http://github.com/chriseppstein/compass-rails-sample-application/tree/master is correct, however.
Comments
chriseppstein
Fri Jul 24 11:20:25 -0700 2009
| link
I think you need to upgrade. I fixed the bug a while ago and cannot reproduce it using Compass 0.8.7 [9aa9867]
agibralter
Fri Jul 24 13:47:30 -0700 2009
| link
$ compass --version Compass 0.8.8 [6ae3f9a] $ mkdir test $ cd test $ rails test $ cd test $ compass --rails -f blueprint . ... Congratulations! Your rails project has been configured to use Compass. Sass will automatically compile your stylesheets during the next page request and keep them up to date when they change. Make sure you restart your server! Next add these lines to the head of your layouts: %head = stylesheet_link_tag 'compiled/screen.css', :media => 'screen, projection' = stylesheet_link_tag 'compiled/partials/_base.css' = stylesheet_link_tag 'compiled/print.css', :media => 'print' /[if lt IE 8] = stylesheet_link_tag 'compiled/ie.css', :media => 'screen, projection' (You are using haml, aren't you?) -
Re-scoping in blueprint-typography results in partial resetting
1 comment Created 5 months ago by jdrowellThe _typography.sass module of blueprint generates markup like
body.bp body { line-height: 1.5; font-family: Helvetica Neue, Arial, Helvetica, sans-serif; color: <a href="/chriseppstein/compass/issues/#issue/333333" class="internal">#333333</a>; font-size: 75%; }when a regular mixin call like +blueprint-typography is called (using the generated screen.sass). Clearly the extra "body" child class prevents the rule from ever being put into effect (body inside a body), thus not resetting the fonts for the whole body. This was observed with compass 0.8.7 and haml 2.2.1. These are several ways to prevent this from happening (like calling -body and -defaults explicitly) but the real bug seems to be in the
=blueprint-typography(!body_selector = "body")block itself. The default placement for the +blueprint-typography mixin call is already scoped inside the body, so re-scoping it causes the problem. I just started using compass so will not attempt to mess with the code before I'm more familiarized. BTW thanks for compass, having fun with it so far.
Comments
chriseppstein
Fri Jul 24 11:33:50 -0700 2009
| link
This is fixed in edge already and will go out with the next release.
http://github.com/chriseppstein/compass/commit/7b28e9af4ab70b995239158a8c6a809c76184fa0
-
Some future requests for better (IMO) project / folder managment
2 comments Created 5 months ago by joneffWhat about templates that could be used when creating new projects? Something like
$compass "project / folder name" --from "template name" $compass "project /folder name" --to "template name"
to create from templates and create templates. I suppose templates could be directories in the gems folder.
Also, the ability to rebuild all projects within a specific folder
$compass "folder name" --rebuild
where folder name has the folders where I keep my projects in the form of other folders. There could be switches like "--rebuild all" (which could be the default). Or "--rebuild modified" to rebuild only those who are modified after the latest rebuild for this folder. Or "--rebuild registered", where it rebuilds only the registered projects.
Speaking of which -- registered projects. Say I not always am in my project dir. Invoking compass is easy, since the path is added to the system path. But not projects unless you add the project dir in the path. So if i do something like
$compass "folder name" --register "short name"
it might be added to a list of projects. Of course it have to be taken in mind if there is a project dir in the current dir, that matches a name from the registered projects.
I could go on like this forever ;) So I stop for now.
-- Ivan
Comments
chriseppstein
Fri Jul 24 11:30:26 -0700 2009
| link
It's pretty easy to make a new project using an existing setup:
mkdir new_project cp old_project/config.rb new_project/config.rb cd new_project compass -f blueprint --installPerhaps an example should be added to command line wiki page.
Regarding the project registry and related commands, I feel this might be too much complexity. A simple bash script could accomplish the same. Maybe I don't understand the use case...
chriseppstein
Mon Aug 03 09:33:02 -0700 2009
| link
http://github.com/ttilley is currently working on some multi-project thing called sassinator. Maybe it will meet your needs when he releases it into the wild.
-
6 comments Created 5 months ago by chriseppsteinblueprintxBlueprint form alignmentsbugxThe fields of blueprint forms are not the same within compass as they are in blueprint.
Comments
I posted a revised forms.html.haml to the Compass google groups that should be useful for testing this once fixed. HTH.
chriseppstein
Sat Jul 11 14:06:23 -0700 2009
| link
That file is now part of the compass/examples/blueprint_default example. Now we just need a fix ;-)
Sorry it has taken me so long to get around to this but I've finally taken some time to look into these issues. It seems that the inline form mixin wasn't getting applied to
form.inlinein the example, so I've fixed that in the master branch of my fork.This fixes the alignment of all of the elements except for the submit button, which for some reason is way up. I haven't been able to track it down but it's probably outside of
_form.sass, since_form.sassdoesn't contain any styles that directly affect the button. =(I haven't been able to solve it yet and I currently can't allocate time to look into it further. >_<
chriseppstein
Sat Nov 21 18:54:52 -0800 2009
| link
I applied Enrico's patch and then I poked around for a while. It's very strange. I can't find any CSS difference that matters. But I did find that I could make it render correctly if I added a non-breaking space.
http://github.com/chriseppstein/compass/commit/81942836d095a7a82fb4ddc966bb40eea6b9345b
I think it looks pretty good. If this issue is troubling others enough for them to find the root cause, I'd be happy to accept their patch/fix in any form.
-
4 comments Created 5 months ago by gravis[blueprint] ie.sass template should include a little help about layoutfeaturexHi,
I've discovered today that compass will center all text under IE with blueprint framework. Sounds like without this option, the container gets stuck to the left, and is not centered.
I think the ie.sass template file should include some comments to help new comers figure out why their css behave like this, and what to do next.
Something maybe like :
// Compass will center text to fix IE6 container centering. // That means all your texts will be centered under all version of IE by default. // Please don't forget to restore the correct behavior to your main container (but not the body tag!) // // Example : // // .container, .footer // :text-align left // //Comments
chriseppstein
Thu Jul 09 12:28:03 -0700 2009
| link
There's a similar comment in the compass implementation file, but perhaps one here would be more useful.
Indeed :)
Anyway, I don't which file you're mentioning, I don't see anything like that in frameworks/blueprint/_ie.sass ?
chriseppstein
Thu Jul 09 12:51:12 -0700 2009
| link
chriseppstein
Thu Jul 09 13:00:57 -0700 2009
| link
merged. thanks.
-
needless haml-edge warning when using haml 2.2.0
1 comment Created 5 months ago by merbjediThere's a warning in
chriseppstein-compass-0.8.5/lib/compass/dependencies.rbthat shows even when haml 2.2.0 is installed. Probably not needed anymore since anyone using haml-edge should be upgrading to haml 2.2.0
Comments
-
Check out lib/compass/dependencies.rb
It's still requiring haml-edge.. I noticed when unpacking it in a rails app.unless defined?(Sass)
require 'rubygems' begingem 'haml-edge','>= 2.1'rescue Exception
$stderr.puts "WARNING: haml-edge gem not found. Trying to find haml on the load path."end require 'sass' end
Comments
chriseppstein
Thu Jul 09 12:26:15 -0700 2009
| link
Compass will continue to default to haml-edge if it is installed, but I will change the behavior to printing out a message only when it is used, not when it is missing.
chriseppstein
Thu Jul 09 13:00:37 -0700 2009
| link
Load haml-edge if it's all new and shiny. Closed by 59a6067.
-
Blueprint colborder should should be + rather than minus
1 comment Created 5 months ago by samsmDescribed here: http://pastie.org/535929
colborder calculates too small of a padding/margin due to a minus that should be a plus. Change produces CSS that matches Blueprint.Comments
chriseppstein
Thu Jul 09 13:00:36 -0700 2009
| link
[Blueprint] Fixed a bug in the calculations for the +colborder mixin. Closed by d2b1370.
-
Hi,
Nice job ;)
index.css is missing in blueprint-default example.
It seems as well that the css framework is not compiled into the generated css. I don't have a nice rendering... and the produced css lack of span-x definitions.
Jej
Comments
chriseppstein
Thu Jul 09 12:30:47 -0700 2009
| link
you have to run
rake examplesand it will build them for you. -
Compass doesn't work in some environments
2 comments Created 6 months ago by sporkmongerI've tried running it in Ruby 1.9 and Ruby 1.8.7 p72 and both failed. The copy of Ruby that comes with OS X Leopard seems to like it just fine.
>> require "compass" NameError: uninitialized constant Sass::Script from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass/sass_extensions/functions.rb:8:in `<top (required)>' from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass/sass_extensions.rb:4:in `require' from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass/sass_extensions.rb:4:in `<top (required)>' from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass.rb:5:in `require' from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass.rb:5:in `block in <top (required)>' from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass.rb:4:in `each' from /usr/local/ruby19/lib/ruby/gems/1.9.1/gems/chriseppstein-compass-0.8.1/lib/compass.rb:4:in `<top (required)>' from (irb):3:in `require' from (irb):3 from /usr/local/bin/irb19:12:in `<main>'Comments
chriseppstein
Thu Jul 09 12:29:55 -0700 2009
| link
What version of haml do you have installed? This is likely because you have haml 2.0 and not 2.2 or haml-edge.
sporkmonger
Thu Jul 09 12:39:47 -0700 2009
| link
Yeah, I figured that out, but forgot to close this issue.
-
Use the data URL scheme to inline images into css.
All major browers except ie6 & ie7 support data urls.
Comments
chriseppstein
Mon Jun 29 22:41:36 -0700 2009
| link
This feature is available in 0.8.
-
Option to output the CSS compressed #feature
2 comments Created 6 months ago by renatocarvalhoAbility to output the CSS style completely compressed
Comments
renatocarvalho
Mon Jun 22 23:06:39 -0700 2009
| link
Sorry, this message was suposed to have a label #feature, but I don't know how to apply labels for messages. Perhaps is because I don't have permission.
renatocarvalho
Mon Jun 22 23:16:56 -0700 2009
| link
I just realized that I can configure this on the "config.rb" file. Sorry. I didn't saw anything about the config.rb file in the wiki. Closing this message.
-
1 comment Created 6 months ago by chriseppsteinControl over the image url link algorithmfeaturexIt should be possible to provide your own image link algorithm with whatever cache busting and asset host strategy you want.
Comments
chriseppstein
Fri Jun 26 12:24:40 -0700 2009
| link
[Sass Extensions] Allow the asset host and cache busting strategies to be defined as part of the compass configuration. Closed by ef47f3d.
-
NoMethodError on line 44 of /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/commands/watch_project.rb: undefined method `>' for nil:NilClass /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/commands/watch_project.rb:25:in `perform' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/commands/watch_project.rb:17:in `loop' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/commands/watch_project.rb:17:in `perform' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/commands/base.rb:15:in `execute' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/commands/project_base.rb:19:in `execute' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/exec.rb:197:in `do_command' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/exec.rb:57:in `perform!' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/lib/compass/exec.rb:40:in `run!' /home/joneff/.gem/ruby/1.8/gems/chriseppstein-compass-0.6.15/bin/compass:8 /home/joneff/.gem/ruby/1.8/bin/compass:19:in `load' /home/joneff/.gem/ruby/1.8/bin/compass:19Comments
chriseppstein
Sat Jun 27 18:51:23 -0700 2009
| link
fixed in 0.8
-
default width/height for blueprint forms breaks rows/cols attribute
8 comments Created 6 months ago by chriseppstein(reported on twitter - https://twitter.com/userscripts/status/2189080080)
While it can be argued that you shouldn't use the rows/cols attribute, I still think the hard-coding of dimensions in a file you're not supposed to modify is a bad idea. So we should make it configurable somehow.
Comments
anotherjesse
Tue Jun 16 21:06:41 -0700 2009
| link
Thanks for filing this. I wasn't sure if there was already a way to override and I was just being dense.
I've created a patch here:
http://github.com/tdreyno/compass/commit/9b1f32bd9c9a147eab9e7030eb6c02bbee630a07However, I don't actually agree with the concept. In my opinion, Compass should not contain any defaults and users would just use Sass normally to inject the colors and sizes like normal. The problem is, that's not how Blueprint is designed. It's designed to automatically have a very solid starting place for sites. This means sites using Blueprint with CSS have a lot of duplication thus the need for Sass & Compass in the first place.
I guess the defaults that are intrinsic to Blueprint muddle up the philosophy of Sass. Hopefully this patch makes people happy, but I can't help but think the increasing complexity is turning Compass into it's own weird language which will need more and more documentation as time goes on.
chriseppstein
Tue Jun 16 23:29:12 -0700 2009
| link
I agree. The main stylesheet provided by compass if you don't specify a framework is a reset and an empty file.
New frameworks built on Sass from the ground up are already under development and will be much more elegant to use. The compass core framework, tries to provide simple, basic mixins that are common patterns -- not anything that would make a site look presentable out of the box.
Thanks for the work, your thoughts on the matter are well founded, and your effort here is helpful.
anotherjesse
Tue Jun 16 23:40:15 -0700 2009
| link
There are also issues trying to override a:visited since it is set in the framework.
Perhaps a way to filter out rules on import?
@import foo.sass remove:"css selectors here"
right now I would have to fork the blueprint framework in order to fix this.
Or perhaps a rake task to "pull a snapshot of the framework into my app/stylesheets/framework" then I can tweak and periodically update if needed.
Overriding is easy, it's resetting or removing unwanted styles that's a hassle. I hate to inject more stuff into Sass itself, but maybe a - (minus) prefix to match the + (plus) prefix which removes information from the compiler's view of the sass structure. Obviously, I have no idea if that's even possible with the way Sass is implemented.
anotherjesse
Tue Jun 16 23:52:34 -0700 2009
| link
I knew I should have waited until the morning to post - I mean removing a:visited
chriseppstein
Tue Jun 16 23:52:51 -0700 2009
| link
Overriding is the way to go. The Sass compiler can trivially remove the duplication from the generated css in a future version. Maybe that should have been my response to the original request as well...
chriseppstein
Sun Jun 21 02:44:19 -0700 2009
| link
Fixed by b84dd30
-
frameworks/blueprint/stylesheets/blueprint/_screen.sass
@import modules/colors.sass @import modules/grid.sass // @import modules/typography.sass @import modules/utilities.sass // @import modules/form.sass @import modules/interaction.sass @import modules/debug.sass =blueprint(!body_selector = "body") // +blueprint-typography(!body_selector) +blueprint-utilities +blueprint-grid +blueprint-debug +blueprint-interaction // +blueprint-formif you want to specifiy your own css classes, behaviors, it would be good, if the modules could be commented out, but not whithin the gem. I have to manually comment it out unfortunatelly.
e.g. typography and form conflicts with jquery css styles (and or personal customization)
greetinxComments
beyoumedia
Sun Jun 14 02:40:50 -0700 2009
| link
instead of doing this:
@import blueprint.sass +blueprintI do this
@import blueprint/modules/grid.sass @import blueprint/modules/utilities.sass @import compass/reset.sass +blueprint-utilities +blueprint-grid
chriseppstein
Mon Jun 15 10:55:29 -0700 2009
| link
@beyoumedia is right, you can and should use the sub-mixins if you don't want ALL of blueprint
-
Replace-text doesn't work on Safari 4. Discussion with Chris (and pull request for patch) is at http://github.com/inbox/147846 ; filing here for tracking purposes.
Comments
I suppose I should mention that the commit (in my fork) that fixes this is http://github.com/marnen/compass/commit/36f83511383fdd02be58b0a596a53080b0cb3861 .
I am having no issues with Safari 4. Perhaps you're mistaking !x and !y for the !width and !height (as in your patch), when they are actually for positioning the background image.
Works here: http://www.quicksnapper.com/files/9241/5712114684A3983E08A53A.png
Additionally, it seems quite easy to add width/height to the selector in the normal Sass fashion (I always do this) than to add more variables to the mixin.
You're right that I was a bit confused about the function of the !x and !y parameters, but even when I omitted them entirely, replace-text didn't work. I'll test again and report if anything changes.
Setting height and width and using 0 for !x and !y seems to have done the trick. I guess I'll just wrap that all in my own convenience function. Thanks for your advice here.
chriseppstein
Sat Jun 20 21:34:08 -0700 2009
| link
I added more comments to the mixin in the code.
-
5 comments Created 6 months ago by wilkerlucioErrno:EACCES on Windows when trying to compile identical file (on watch)bugxIn command line, when you save a file a Sass file with same content (changing organization or including a new module for example) the Sass gives a EACESS error, if this happens when the watcher is on before the error, the watch keep listening for changes, but if happens when you start to watch, the program exit, to keep it back working you need to delete the generate CSS files.
Comments
wilkerlucio
Sun Jun 07 16:40:50 -0700 2009
| link
after some tests, i found the problem is when the Compass try to touch the file (when detect identical content), after comment the line of touch the scripts runs without problems. The solution maybe is to create a touch implementation to deal with this problem.
chriseppstein
Mon Jun 08 12:57:26 -0700 2009
| link
It would be good if there was a patch that fixes this issue on windows that I could then test on unix based systems. I don't have easy access to windows.
chriseppstein
Fri Jun 12 14:11:50 -0700 2009
| link
The ruby implementation is supposed to work on windows. I'd like to have this bug reproduced by others before taking any action. Are you sure you don't have permission or some other issue that's causing the EACCESS error to be able to modify the file.
Patch at http://gist.github.com/140766
chriseppstein
Thu Jul 09 12:24:44 -0700 2009
| link
Fixed.
-
I found a project on rubyforge but no gems on there. Why not submit gem there?
Comments
chriseppstein
Mon Jun 08 12:54:59 -0700 2009
| link
The plan is to host the stable gem there and the development gem on github. The account is a placeholder until I get around to it. Maybe I can do it for the 0.8 release.
adamsalter
Wed Oct 14 21:42:05 -0700 2009
| link
Github gems are no more. I've since learnt that you can create 'prerelease' gems with a special version string:
http://rubygems.rubyforge.org/rdoc/Gem/Version.html
I'm changing all my old github gems back to normal syntax...
ERROR: could not find gem compass locally or in a repository;)You could move it to Gemcutter instead. It should be a bit easier, and it seems like Gemcutter might take over gem hosting from Rubyforge.
chriseppstein
Thu Oct 15 07:04:57 -0700 2009
| link
The compass gem is already on gemcutter:
http://gemcutter.org/gems/compass
This is where I'll posting new releases.
-
Current compass version (0.6.13) has a dependency to haml-edge 2.1.12. Where does this exist? I can only find haml-edge 2.1.0
Comments
I just did a gem install:
$ gem install haml-edge Successfully installed haml-edge-2.1.16That worked. Thanks. I guess then, the install doco needs to be updated to say this.
chriseppstein
Mon Jun 08 12:52:32 -0700 2009
| link
haml edge is hosted on rubyforge, some older versions of gem don't handle cross-server dependencies. By adding http://gems.github.com/ to you gem server list and not specifying --source for the gem install, you should have installation success. We should update the wiki and blog posts to reflect this, so I'm going to leave this issue open until they do.
I added http://gems.github.com/ to my gem server list, and I actually get
gem install haml-edgeERROR: could not find gem haml-edge locally or in a repository
Not sure whats going on.
chriseppstein
Tue Jun 09 12:02:57 -0700 2009
| link
haml edge is hosted on rubyforge. compass is hosted on github.
I have:
$ gem sources *** CURRENT SOURCES *** http://gems.rubyforge.org/ http://gems.github.com/ $ sudo gem install haml-edge --no-ri Successfully installed haml-edge-2.1.24 1 gem installed Installing RDoc documentation for haml-edge-2.1.24...I don't have enough details to diagnose your issue.
chriseppstein
Sat Jun 20 20:57:17 -0700 2009
| link
I think this works, closing.
-
Line 49 of compass/utilities/lists/_horizontal_list.sass now states:
+horizontal-list-item-containerand this generates the error:
Sass::SyntaxError on line 49 of /Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.6.12/frameworks/compass/stylesheets/compass/utilities/lists/_horizontal_list.sass: Undefined mixin 'horizontal-list-item-container'.I think it should be:
+horizontal-list-containerComments
jeroenvandijk
Wed May 27 02:12:26 -0700 2009
| link
I can confirm this too. I just rebuild edge (0.6.12) to make sure I wasn't using an old version.
Btw, is there a way to add a patch to these issues?
I have already sent a pull request for http://github.com/marcenuc/compass/commits/5868c2e4e19ff2b0d12e326aaa6961f6674575ef
chriseppstein
Mon Jun 08 12:50:23 -0700 2009
| link
Fixed in 0.6.13.
-
Syntax Error: Indenting at the beginning of the document is illegal
1 comment Created 7 months ago by sant0sk1line 2 of: frameworks/compass/stylesheets/compass/utilities/general/_float.sass
This is with a vanilla Rails app using:
Compass gem 0.6.6
Haml 2.1.8
Rails 2.3.2I tried just fixing this one piece of the code but that results in another error:
SyntaxError: Illegal nesting: Nothing may be nested beneath import directives.
on line 2 of: frameworks/compass/stylesheets/compass/utilities/general/_float.sass
Comments
-
An app with Compass will not run if Haml is installed on the server
5 comments Created 7 months ago by endymionCompass requires haml version 2.1 which is only available currently in haml-edge. But Compass will happily load haml version 2.0 and not haml-edge version 2.1 if Haml is installed. Then the app won't run. The existence of Haml 2.0 on a server should not prevent a Compass app from running.
It's frustrating to descend into DLL Hell when I try to deploy, since Compass isn't necessary in production. The CSS has already been generated and Compass is irrelevant to the production server. Yet Compass is the only thing stopping me from deploying. Very frustrating.
Is there a workaround for using Compass on servers where Haml is already installed? I have the option of installing my own local haml-edge but I do not have the option of uninstalling the existing Haml 2.0.
Comments
chriseppstein
Tue May 19 18:45:35 -0700 2009
| link
I assume your running a rails application environment. It's not "best practice" to check in your generated css in such environments. But assuming you do not agree with me, I still think it's incredibly dangerous to run with a different version of haml in development than in production. I recommend that you either freeze your haml-edge gem in vendor or install it in your production environment. Existing apps will be unaffected by the presence of the haml-edge gem, but compass will pick it up if it sees it.
I, too, look forward to the next stable release of haml so that we can simplify the dependencies. Hopefully it will be soon.
chriseppstein
Tue May 19 19:35:04 -0700 2009
| link
If you're only using compass in development, you can also do two other things:
1. Use compass in standalone mode without the rails integration. In an existing rails project, you can just delete the config/initializers/compass.rb and then run compass --watch to compile your stylesheets.
2. Conditionally run compass by wrapping the contents of config/initializers/compass.rb in a block that checks the current rails environment.Thank you for the suggestions, I really appreciate it. I like the idea of Compass but if it depends on an edge version of something else and that dependency causes deployment problems then Compass isn't something that I would depend on in production. So thanks for the suggestions for ways to use it during development only. I solved my deployment problem by removing Compass from the project, since I don't have the option of removing the Haml gem from the deployment environment. If I continue to tinker with Compass then I'll just use it in development to trigger Sass. I do like that --watch feature.
You can reproduce the problem very easily. "gem install haml" Then try to run that sample Rails app. If you have both haml and haml-edge then Compass will load haml and then complain that it requires haml 2.1. If you have the ability to totally control what gems are installed in your production environment then that's no problem but Compass won't work on hosting environments that provide Haml and then don't let you mess with your GEM_PATH. That sounds like a niche thing but Dreamhost is one of those hosts and they're popular enough to be relevant.
chriseppstein
Tue May 19 20:02:38 -0700 2009
| link
I explicitly tested the case of having both gems installed, but I will retest. It shouldn't break if both are there and if that's the case, then a patch will be forthcoming. If it's not reproducible in a simple app with just haml and compass installed, then there must be something else that is requiring haml. Can you show me what your gem configuration in your environement looks like? It could be that you're setting the dependency incorrectly and causing the wrong version to get picked up.
I really appreciate your assistance, I know that you're a busy guy. I'm trying to repay Karma by contributing my own gem to the world for doing layouts, which will be compatible with Compass.
To start out my day today, I decided to add Compass back into that problem project that has to go to Dreamhost, to help you to troubleshoot any possible haml/haml-edge incompatibility. I re-ran compass --rails to add config/compass.config and config/initializers/compass.rb, and it WORKED. It deploys to the problem server and it runs. ZOMG now I'm so confused.
I think you can maybe mark this issue closed because I think maybe I was totally wrong. I'm going to continue tinkering with it today to try to reproduce the haml/haml-edge incompatibility that caused me so much grief last night.
Either way, Compass is really neat. Thank you for making it and for releasing it so that I can use it.
-
I just sent you a pull request for http://github.com/marnen/compass/commit/572291d9993e83314354148be3beb1b322534bf7 , which adds better scoping to horizontal-list so that it can apply (if desired) to one level of li, not the whole list tree. This is good for making dropdown menubars.
Comments
chriseppstein
Tue May 19 12:46:58 -0700 2009
| link
I agree that a change would be useful here to control the scoping of LI for nested lists. Please see my comment for more details.
chriseppstein
Sat May 23 10:08:19 -0700 2009
| link
[Compass Core] Extracted two new mixins from +horizontal-list. Closed by faadde2. The new +horizontal-list-container and +horizontal-list-item mixins can
be used to build your horizontal list when you need more control over
the selectors (E.g. when working with nested lists).
chriseppstein
Sat May 23 10:11:54 -0700 2009
| link
Thanks for your patches, but I decided to fix this using a different approach altogether This approach gives more control to the user when the default mixin doesn't work.
-
1 comment Created 7 months ago by chriseppsteinbugxSass cache gets written to the wrong place during project creationcommand linexThe sass cache gets written to the working directory instead of the project directory.
Comments
chriseppstein
Sat May 23 10:08:19 -0700 2009
| link
[Command Line] Store sass cache files in the sass directory of the project. Closed by fcdaf41.
-
1 comment Created 7 months ago by chriseppsteinAccess to Sass Engine Options HashfeaturexThere should be a way to set options for the Sass::Engine directly within the compass configuration file.
Comments
chriseppstein
Sat Jun 27 13:22:05 -0700 2009
| link
Will be part of the 0.8 release.
-
1 comment Created 7 months ago by chriseppsteinClear Licensing of the Compass Codebase and included LibrariesfeaturexA standard LICENSE file should be available and viewable on Github. The licensing for the included frameworks must also be clear.
Comments
chriseppstein
Sun Jun 21 13:06:09 -0700 2009
| link
More clear licensing. Closed by 99f608e.
-
Everytime I try to create a new project I get this
"ArgumentError on line 18 of C: marshal data too short"Comments
chriseppstein
Wed May 13 22:26:32 -0700 2009
| link
Please double check that you are running the latest version of haml. If it still happens, please post the full stack trace
Here's what I get.
C:\>haml -v Haml 2.0.9 C:\>compass -f blueprint sample-project --trace directory sample-project/ directory images/ directory src/ directory stylesheets/ create config.rb create screen.sass create print.sass create ie.sass create grid.png exists stylesheets compile ie.sass ArgumentError on line 18 of C: marshal data too short C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/files.rb:18:in `tree_for' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/file_node.rb:19:in `perform!' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:73:in `_perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:61:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `map' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/file_node.rb:20:in `perform!' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:73:in `_perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:61:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `map' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/file_node.rb:20:in `perform!' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:73:in `_perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:61:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `map' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/file_node.rb:20:in `perform!' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:73:in `_perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:61:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `map' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:82:in `perform_children' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:78:in `perform!' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:73:in `_perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:61:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/tree/node.rb:39:in `render' C:/Ruby/lib/ruby/gems/1.8/gems/haml-edge-2.1.8/lib/sass/engine.rb:108:in `render' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/actions.rb:68:in `compile' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/compiler.rb:37:in `run' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/compiler.rb:36:in `each' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/compiler.rb:36:in `run' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/commands/update_project.rb:19:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/commands/stamp_pattern.rb:19:in `perform' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/commands/base.rb:15:in `execute' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/commands/project_base.rb:19:in `execute' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/exec.rb:197:in `do_command' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/exec.rb:57:in `perform!' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/lib/compass/exec.rb:40:in `run!' C:/Ruby/lib/ruby/gems/1.8/gems/chriseppstein-compass-0.6.6/bin/compass:8 C:/Ruby/bin/compass:19:in `load' C:/Ruby/bin/compass:19
chriseppstein
Thu May 14 08:25:53 -0700 2009
| link
Compass requires edge haml (version > 2.1). You can install it from source, or using the "haml-edge" gem. Instructions are on the wiki.
-
1 comment Created 7 months ago by chriseppsteinbugxDon't set output_style in the compass.config file for rails projectsrailsxoutput style will default to the right thing based on the rails environment.
Comments
chriseppstein
Sat May 23 10:08:20 -0700 2009
| link
[Rails] Don't set the output style in the compass.config file for rails projects. It will default according to the runtime environment. Closed by 7b90aef.
-
rails-blueprint integration sass errors after install
3 comments Created 7 months ago by rodebrahimiin appropriate general gem directory...
_float.sass -- line #2 "Float" needed to be commented out
_clearfix.sass -- comments to be malformed originally, needed edits to resolve and run properly
Comments
chriseppstein
Wed May 13 09:27:17 -0700 2009
| link
This is a Sass bug that has been fixed. You need to upgrade to haml-edge:
sudo gem uninstall haml sudo gem install haml-edge
rodebrahimi
Wed May 13 09:30:39 -0700 2009
| link
I have both running actually... will this mess with my environment if I don't use haml-edge for other projects but use haml? I guess I'm not clear on the diff btwn these releases...
chriseppstein
Wed May 13 10:07:14 -0700 2009
| link
You can just download and install the latest from haml's master branch, that is what haml-edge is. Compass will try to pick up haml-edge if it's installed, but YMMV.
-
2 comments Created 7 months ago by shanesvellerbugxSilent failure of compass commandcommand linexI am running on Leopard 10.5.6, with Ruby 1.8.6pl114, Rubygems 1.3.1.
My installed gems are listed here.Compass is gem version 0.6.6.
While attempting to follow this tutorial, when running the command
compass --rails -f blueprint ., if the the target path ('.' in this case) is left off, it will fail silently.Comments
chriseppstein
Wed May 13 09:20:05 -0700 2009
| link
Yes, I've seen this bite people a couple of times now. I'll make a fix.
chriseppstein
Sat Jun 27 18:48:38 -0700 2009
| link
Print a message when updating a project that has no files. They probably meant to install but forgot the directory argument. Closed by 15ebbfe.
-
I ran my CSS against the W3C validator (http://jigsaw.w3.org/css-validator/validator), and got the following error:
Property overflow-x doesn't exist in CSS level 2.1 but exists in [css3] : hidden
This occurs on line 176 of the screen.css generated by the compass framework for Blueprint:
/ line 97, ../../../../../../../Library/Ruby/Gems/1.8/gems/chriseppstein-compass-0.6.5/frameworks/blueprint/stylesheets/blueprint/modules/_grid.sass / html .column, html div.span-1, html div.span-2, html div.span-3, html div.span-4, html div.span-5, html div.span-6, html div.span-7, html div.span-8, html div.span-9, html div.span-10, html div.span-11, html div.span-12, html div.span-13, html div.span-14, html div.span-15, html div.span-16, html div.span-17, html div.span-18, html div.span-19, html div.span-20, html div.span-21, html div.span-22, html div.span-23, * html div.span-24 { overflow-x: hidden; }
Comments
I agree, the blueprint grids are overflow happy, & setting to hidden is not always the desired effect. Can this be abstracted out into a mixin unto itself?
chriseppstein
Wed May 13 09:24:43 -0700 2009
| link
This property was added in blueprint 0.8 and I don't fully understand what it is trying to achieve. My goal is to have the blueprint port stay as true to blueprint proper as makes sense. I'm not inclined to make a change just to silence a validation error that is valid in css3 and likely harmless in css2 (browsers discard properties they don't understand).
What, if any, real issue does this cause?
chriseppstein
Mon May 18 11:44:28 -0700 2009
| link
Ok. I waited 5 days for further comments. Closing this issue.
- 960.gs▾
- blocker▾
- blueprint▾
- bug▾
- command line▾
- compass core▾
- feature▾
- merb▾
- rails▾
- yui▾
- Apply to Selection
-
Change Color…
Preview:preview
- Rename…
- Delete





This has already been fixed in v0.10. you can install it like so: