Why not use two classes for an element?
Like:
.common { common-stuff }
.one { unique1 }
.two { unique2 }
And in html:
<div class="one common">
<div class="two common">
On 6/6/07, twifkak <[EMAIL PROTECTED]> wrote:
>
>
> > Of course, I could be wrong. Thus, I'm asking you, both twifkak in
> > particular and the Sassy community as a whole: where, if at all, do you
> > think this would be useful?
>
> Meh, I keep forgetting to grab some exemplar CSS snippets from work,
> which is one of the reason's I've yet to post (another being I'm
> curious what others say, and a third being that I'm a lazy pig).
>
> My theoretic, language-pedant argument is that "," pulls the
> abstraction too far away from the individual things. With just two
> items it ain't that bad:
> .one, .two { common-stuff }
> .one { unique1 }
> .two { unique2 }
> vs:
> !common=
> common-stuff
> .one
> !common
> unique1
> .two
> !common
> unique2
>
> But as the stylesheet grows, I find the common section tends to pull
> farther and farther away from the individuals, and with no hint that
> it applies. In other words, the definition of the style of a given
> element ends up spreading across several files, and the only way to
> know that is grep and/or FireBug.
>
> Maybe I'm just stupid, but I've found it's hard to maintain
> abstractions in CSS, and I'd hoped that introducing traditional
> mechanisms would make that easier (at least for programmer-folken like
> myself). I know an alternative is to sully your markup by tagging
> elements with multiple classes, but most of the time, that's adding
> coupling -- sure, the .error is also an .emphasized now, but maybe it
> won't be in a few weeks. Also, thinner HTML is better, no?
>
> Perhaps I should try it out locally on a mini-project and report if it
> helps? Or perhaps I should hunt down a particularly junky snippet that
> I think would benefit from some mixin love?
>
> Yeah, I don't have any magical sales pitch, 'cause I'm just not sure
> either. It *feels* like it should be useful, and it's something I've
> wanted from CSS long before I'd heard of Haml/Sass, but I could just
> be f-in' crazy.
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
