4 ms·

Hi, I'm one of the thoughtbot designers behind Neat. I have been using Semantic.gs for a while and it is one of my favorite grid frameworks out there. My gripe

by kaishin 14y ago

Hi, I'm one of the thoughtbot designers behind Neat. I have been using Semantic.gs for a while and it is one of my favorite grid frameworks out there. My gripe with Semantic.gs is that it is not responsive, i.e. it doesn't come with a straightforward way to change the grid for specific breakpoints. I also don't see how span-columns() is any less semantic than .column().

alexanderh 14y ago
I was thinking more of the "alpha" and "omega" mixins which made no immediate sense to me. I'm guess its part of your "golden ratio" code, but it still doesnt seem truly "semantic" And I really dont see how Semantic.gs isn't responsive? Set its grid representation to percentages, write a few media queries, and its as responsive as any other grid system out there. The inherent behavior of the CSS box model + Percentage based semantic.gs + media queries is as responsive as I think you can get.... its all I've ever needed to do ANY responsive design I can imagine. I've never felt limited by Semantic.gs in terms of responsive design. I really dont see how you could make that any easier? Are your mixins generating media queries? Is it really that hard to calculate a golden ratio and use it with Semantic.gs? Edit: http://semantic.gs/examples/responsive/responsive.html http://semantic.gs/examples/responsive/responsive.html they even have a Responsive example on the front page of their website, so I really dont understand why you think Semantic.gs isnt responsive? > i.e. it doesn't come with a straightforward way to change the grid for specific breakpoints. isn't that what media queries are for?
- kaishin 14y ago
  Please take some time to read the documentation and see the examples. The omega() (there is no alpha() mixin btw) mixin doesn’t compile to CSS, so debating whether it's semantic or not is beside the point. If, after having a closer look, still think that Neat would not be solving any of your current problems, then you are more than welcome to stick to your guns. No tool is perfect for everyone.

by kaishin 14y ago

alexanderh 14y ago

I was thinking more of the "alpha" and "omega" mixins which made no immediate sense to me. I'm guess its part of your "golden ratio" code, but it still doesnt seem truly "semantic" And I really dont see how Semantic.gs isn't responsive? Set its grid representation to percentages, write a few media queries, and its as responsive as any other grid system out there. The inherent behavior of the CSS box model + Percentage based semantic.gs + media queries is as responsive as I think you can get.... its all I've ever needed to do ANY responsive design I can imagine. I've never felt limited by Semantic.gs in terms of responsive design. I really dont see how you could make that any easier? Are your mixins generating media queries? Is it really that hard to calculate a golden ratio and use it with Semantic.gs? Edit: http://semantic.gs/examples/responsive/responsive.html http://semantic.gs/examples/responsive/responsive.html they even have a Responsive example on the front page of their website, so I really dont understand why you think Semantic.gs isnt responsive? > i.e. it doesn't come with a straightforward way to change the grid for specific breakpoints. isn't that what media queries are for?

kaishin 14y ago
Please take some time to read the documentation and see the examples. The omega() (there is no alpha() mixin btw) mixin doesn’t compile to CSS, so debating whether it's semantic or not is beside the point. If, after having a closer look, still think that Neat would not be solving any of your current problems, then you are more than welcome to stick to your guns. No tool is perfect for everyone.