101–105 of 105 posts
http://learn.shayhowe.com/advanced-html-css/detailed-css-pos... "For this to work within Internet Explorer 6 [...] in Internet Explorer on an Apple computer will also [...]" Seriously, when was this written, in 2003? Totally irrelevant and makes newcomers confused.
> One functionality of CSS often abused without awareness are selectors [...] How elements are selected within CSS affects performance, including how fast a page renders This assertion used to be thrown around as one of the supporting arguments for using OOCSS, but I'm sure I later read that it was largely debunked; the performance implications were negligible and so it was just making CSS less legible/maintainable f…
[0] http://www.stevesouders.com/blog/2009/03/10/performance-impa...
Further reading:
http://csswizardry.com/2011/09/writing-efficient-css-selecto... https://developer.mozilla.org/en-US/docs/CSS/Writing_Efficie...
Earlier quoted context omitted.
Not really sure what you mean by 'regular' website, it sounds like you're talking about a variety of different things. Google the following: Responsive Design, Object Oriented CSS, SASS, Compass, Susy Grids. Any help? I don't think you're going to get tutorials on how to create something like Gmail because AFAIK it's JavaScript generated from JAVA. Nicole Sullivan writes a lot about this sort of thing. EDIT fixed for…
I think the best way to describe the difference between a 'regular' website and the advanced layouts I talk about is that an 'advanced layout' often looks similar to a desktop application. Remember the first BaseCamp? Given designs, I reckon I could build the front-end for that. However given designs for GrooveShark, icloud.com or the new spotify web-app - I wouldn't know where to begin. I've tinkered with responsive…
Have you played with Sencha Touch or Google's Angular JS or Ember or Backbone?
These are all great starting points and will teach you a lot about how to structure your code, but for anything large like iCloud, you're going to probably need to write your own libraries because nobody else is doing exactly what you want.
Get good at using jQuery to animate stuff, then re-work your UI using CSS3 transitions (because jQuery suffers performance issues on mobile).
Design for mobile first and scale upwards; by design I don't mean PSDs I mean open an HTML document and just start chopping it up.
> One functionality of CSS often abused without awareness are selectors [...] How elements are selected within CSS affects performance, including how fast a page renders This assertion used to be thrown around as one of the supporting arguments for using OOCSS, but I'm sure I later read that it was largely debunked; the performance implications were negligible and so it was just making CSS less legible/maintainable f…