Read the blogs!
Started by Antes, April 02, 2014, 03:47:58 PM
Quote from: Antechinus on April 03, 2014, 03:48:55 PMWhy frameworks suck
Quote from: Antechinus on April 03, 2014, 03:48:55 PMQuote from: Tekkla on April 03, 2014, 05:25:29 AMClean isn't only small code. It's also should be readable and reusable within and outside of the scope it was created for.Where did I say it shouldn't be? Why would I want code to be clean, if not to make it readable and useable? I'm all in favour of heavily commenting CSS, and minifying it before it's sent to the browser.Why frameworks suck
Quote from: Tekkla on April 03, 2014, 05:25:29 AMClean isn't only small code. It's also should be readable and reusable within and outside of the scope it was created for.
Quote from: DeroZ on April 20, 2014, 05:50:09 PMwhere can i see a demo?
Quote from: Alex@ on May 16, 2014, 05:47:13 PMTrying to guess how people wants to experience a website this way, isn't one I like. And honestly, I don't see the point. Tablets and phones are getting higher and higher resolutions, therefore responsive themes becomes less and less a great idea.Maybe a few years back...!
QuoteWhat really would be helpful, its that a screen also reported its physical size to the webpage somehow(maybe it does already?)..then you could design for 1080p on any physical size...
<meta name="viewport" content="width=device-width, initial-scale=1" />
Quote from: Colby67 on May 17, 2014, 07:13:29 AMYup, responsive is the way to go..but I need also to have a way to say: hey, this is 1280 and I can have 3 columns here, but on phones(since they are smaller) i just want 2 columns since the text will be more cramped here(when the text have the approx same physical size as the monitor).Do you see the problem? A lot of other things are solved fine by RD, but avoiding one-column-fits-all-design I need that kind of control to make best use of widescreens as well as mobile phones, especially when they both have high resolutions.