You know, I run haml & sass vendored in my rails app, I don't do the gem thing because I'm not usually running a released version. Just do a git checkout into vendor/plugins/haml and the init script should grab that code instead of the gem.
-chris On Fri, Nov 28, 2008 at 9:28 PM, s.ross <[EMAIL PROTECTED]> wrote: > It's at: > http://pastie.org/326501 > > This is just an excerpt. The bug shows up immediately. Here's the weird > part. Assume the file is called application.sass. If I do: > > sass application.sass > > everything works just as you would expect clean translation to stdout. If I > run Rails, then I get the problem I described. So I checked to see what > obsolescent versions of the haml gem might be installed. Well, plenty of old > ones, so I cleaned all of them out, created a new gem package off github, > installed, and same behavior. Ok from command line, not from Rails. > > ??? > > --steve > > > On Nov 28, 2008, at 7:49 PM, Chris Eppstein wrote: > > Glad you like compass. > Can you paste the code online so I can try it out? > -c > > On Fri, Nov 28, 2008 at 7:36 PM, s.ross <[EMAIL PROTECTED]> wrote: > >> >> Chris-- >> >> [topquoting to be more iPhone-friendly] I'm running Haml version >> 2.0.4. I thought the changes for mixins happened around 2.0.3 but I >> could be wrong. I updated from github (and Haml version is 2.1.0!) but >> even then the same problem occurs: Sass::SyntaxError: Undefined mixin >> 'sprite'. That would be on this exact line of code: >> >> #navigation >> li >> => +sprite >> >> >> BTW: Great work on Compass. Truly impressive stuff. >> >> --steve >> >> >> On Nov 28, 2008, at 4:13 PM, Chris Eppstein wrote: >> >> > >> > Hi Steve, >> > Your mixins look fine. What version of haml do you have installed? >> > You need to be running off the master branch of haml to use mixin >> > arguments. >> > >> > Regarding your second question, SassScript is certainly capable of >> > expressing manipulation of arguments. Take a look at compass's grid >> > module for an example. That said, be careful not to trade too much >> > clarity for DRYness. That's a judgement call, of course. >> > >> > -chris >> > >> > Hunt & pecked on my iPhone... Sorry if it's brief! >> > >> > On Nov 28, 2008, at 3:45 PM, "s.ross" <[EMAIL PROTECTED]> wrote: >> > >> >> >> >> After looking over Compass a bit, it looked like a good time to >> >> revisit some of my monolithic CSS. I wanted to create a mixin for >> >> background positioning: >> >> >> >> =sprite(!x=0px, !y=0px) >> >> :background url(/some/place/my/png/lives.png) no-repeat >> >> :background-position !x !y >> >> >> >> And then: >> >> >> >> .accept-button >> >> +sprite(-320px, -440px) >> >> >> >> Without the arguments everything is dandy, but when I add the >> >> arguments, the sprite mixin is not found. Bonus question: As all my >> >> offsets are negative and specified in pixels, it would be great to >> >> just write: >> >> >> >> +sprite(320, 440) >> >> >> >> Is that level of interpolation possible? >> >> >> >> Any help appreciated! >> >> >> >> Steve >> >> >> >>> >> > >> > > >> >> >> >> > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
