Thanks Eric. I'm learning this as I familiarize myself with Compass. On May 7, 3:25 pm, Eric Meyer <[email protected]> wrote: > There is nothing back-end specific about Compass, if that's what > you're worried about. While there's a lot of interest from the Ruby > folks, I use it with Python and I know many people are using it with > wordpress and static sites of various sorts. Compass is as back-end > agnostic as sass is. > > Cheers, > -e > > On May 7, 3:29 pm, Michael <[email protected]> wrote: > > > > > I've been using Sass in back-end agnostic front-end development (Pure > > HTML/CSS/JavaScript). I'll have to learn Compass. > > > On May 7, 2:03 pm, Chris Eppstein <[email protected]> wrote: > > > > I think this is a case where a compass plugin could really shine :) > > > > On Fri, May 7, 2010 at 2:01 PM, Michael <[email protected]> wrote: > > > > Thanks for the link > > > > tohttp://github.com/nex3/haml/issues/closed#issue/143 > > > > > The unquot("") workaround mentioned at the link above works nicely for > > > > SmartSprite reference directive (css property) comments. I switched my > > > > Sass source style to scss and the image directive comments are left > > > > alone. > > > > > Based on some testing and the link above I've determined the following > > > > rules for an unsupported SmartSprite workflow for those interested: > > > > > 1. Use scss syntax. (Required for image directives to be left > > > > untouched) > > > > 2. Background position must come before background image in property > > > > order. (SmartSprite requires this) > > > > 3. Background image property must not be the last rule. (Or else > > > > SmartSprite will not see the last '}' and break the css) > > > > 4. SmartSprite reference directive (css property) comments must be > > > > placed before the semicolon and wrapped in unquot("") > > > > > Thanks, > > > > Michael > > > > > On May 7, 12:18 pm, Nathan Weizenbaum <[email protected]> wrote: > > > > > No, this is not currently (directly) supported. Seehttp:// > > > > github.com/nex3/haml/issues/closed#issue/143. > > > > > > If enough people want this, I could potentially add a special case, > > > > > but > > > > I'd > > > > > rather not. > > > > > > On Fri, May 7, 2010 at 11:41 AM, Michael <[email protected]> wrote: > > > > > > I use SmartSprites CSS Sprite Generator in my front-end development > > > > > > work. Sass modifies SmartSprite directive comments and removes > > > > > > property comments. Are there plans for an option to leave comments > > > > > > alone? > > > > > > > Example SmartSprite directive: > > > > > > /** sprite: button_arrows; sprite-image: url(../img/ > > > > > > button_arrows.gif); sprite-layout: vertical */ > > > > > > > Sass Output: > > > > > > /* sprite: button_arrows; sprite-image: > > > > > > url(../img/button_arrows.gif); > > > > > > sprite-layout: vertical */ > > > > > > > Example SmartSprite property comment: > > > > > > background: no-repeat url(../img/button_arrows_gray.gif) scroll > > > > > > right > > > > > > top #e5e5e5 /** sprite-ref: button_arrows; sprite-alignment: right; > > > > > > */ > > > > > > > SassOutput: > > > > > > background: no-repeat url(../img/button_arrows_gray.gif) scroll > > > > > > right > > > > > > top #e5e5e5 > > > > > > > I am using Haml/Sass 3.0.0.rc.4 (Classy Cassidy) > > > > > > > Thanks, > > > > > > Michael > > > > > > > -- > > > > > > 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]<haml%[email protected]>< > > > > haml%[email protected]<haml%[email protected]> > > > > >. > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/haml?hl=en. > > > > > > -- > > > > > 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] <haml%[email protected]>. > > > > > For more options, visit this group athttp:// > > > > groups.google.com/group/haml?hl=en. > > > > > -- > > > > 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] <haml%[email protected]>. > > > > For more options, visit this group at > > > >http://groups.google.com/group/haml?hl=en. > > > > -- > > > 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 > > > athttp://groups.google.com/group/haml?hl=en. > > > -- > > 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 > > athttp://groups.google.com/group/haml?hl=en. > > -- > 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 > athttp://groups.google.com/group/haml?hl=en.
-- 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.
