There are loads of CSS frameworks out there, and plenty more of articles telling you that they are the devil and don't use them . I agree with these articles as a whole. So what am I trying to say? Frameworks can be good? It depends.
With the release of Firefox 3, we find all major browsers now support a single interface (mostly) for allowing the Browser to do all of our Rich Text editting needs. This allows us to set a single property, contentEditable, and then that element accepts rich text processing. No more loading in an iframe, having document.domain issues, and having little control over the style of the iframe. This, however, does mean Firefox 2 and below are excluded from the party.
I probably spend more time writing PHP than I do Javascript (I'd like to reverse that but oh well). Well, PHP has so many functions, I'm constantly going to something like http://php.net/substr_replace to simply remember how a function works. It's not a long process, but it involves opening a new tab (Control + T), selecting the address bar (Control + D), typing php.net/substr_replace, and then loading the page.
To learn the basics of a Ubiquity command, I made it so all I have to do is open Ubiquity (Control + Space) and then type:
php substr_replace
Here's a short tip today. I've been finding that when using foreach in PHP to check if there's more in the array, the use of next() has failed me on multiple occasions . I just converted every instance of next() in my code to instead use end() .
