I'm building a list into a fancy-looking widget with different styles for a selected list item, the list items adjacent to the selected item, and the list items 2 spots away from the selected item. Also, the items following the selected item are slightly different than those preceding it.
Currently each list item has about four classes, e.g. <li class="timeline_tile unselected offset1 right">. Normally this would be fine, but I'm also building the UI in MVC JavaScript with Active.js and it seems wonky to have to manage all of these class names in the view logic. I'd much rather do: <li class="tile2">, and push all of the details into local sass mixins. Thoughts? On Oct 29, 2:52 pm, Chris Eppstein <[email protected]> wrote: > What's the motivation for allowing them to be defined in a scoped context? > > chris > > > > On Fri, Oct 29, 2010 at 2:47 PM, zachrose <[email protected]> wrote: > > I've been using Sass for about a year now and it's awesome. I just got > > the engineering guys at my company on board too. > > > One question, what's the motivation for forcing mixins to be at the > > root of the Sass document? (This is expected behavior, right?) > > > Just curious, > > Zach > > > -- > > 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 at http://groups.google.com/group/haml?hl=en.
