On Tue, May 31, 2016 at 12:40 PM, Chris Rockwell <ch...@chrisrockwell.com>
wrote:
> Sorry Tom, I completely glossed over your actual question.
>
> I can only guess that your method (fewer files I presume) is faster to
> compile but I can't imagine that being anything noticeable. From an
> organization standpoint I strongly prefer breaking everything into
> components and including the relevant media queries with each component.
> I've worked with large codebases that have separate files for media
> queries, each breakpoint, and I've always found it more difficult to track
> down what I need.
>
>
> On Tue, May 31, 2016 at 12:32 PM Chris Rockwell <ch...@chrisrockwell.com>
> wrote:
>
>> I have used the method from the second article since I started using
>> Sass. I break components/objects/atoms/whatever into their own file and it
>> makes more sense, to me, to include the media query with the components.
>>
>> I make mine "more inline" though:
>>
>> .selector {
>> color: red;
>> @media (min-width: 767px) {
>> color: blue;
>> }
>> }
>>
>>>
>>>
One of the driving forces for using my method was the ability to easily
create a "old IE (8)" sheet by having a second main scss file for old IE
only, with the main difference being the removal of the MQs as IE 8 and
older don't understand MQs. So my second main sheet was just all the same
imports as the first main sheet, minus the MQs. I would compile the two
main sheets simultaneously and deliver the MQ-less sheet to <= IE8. Since
we have *finally* kicked IE8 to the curb here, I may need to rethink my
method.
--
Tom Livingston | Senior Front End Developer | Media Logic |
ph: 518.456.3015x231 | fx: 518.456.4279 | medialogic.com
#663399
______________________________________________________________________
css-discuss [css-d@lists.css-discuss.org]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
