Hey there! snookca is using Twitter.
Twitter is a free service that lets you keep in touch with people through the exchange of quick, frequent answers to one simple question: What are you doing? Join today to start receiving snookca's updates.
|
Oldest tweet of mine: http://twitter.com/snookca/... Nov 15th, '06 (idea: @jnunemaker) |
just realized that I have uncashed cheques on my desk. I should probably go to the bank. |
Will probably do lunch next Thursday at Clocktower pub on Bank. Who's in tentatively? |
@vero no pierogies in the UK? for shame. (mmm, w/sour cream and bacon) |
Screencast: Playing with light in design. http://tinyurl.com/bjhrbf |
uploading another screencast |
@mbavio I have no plans to write a CakePHP book at this time. |
@graphical_force designed and developed for a co-worker at the time. I was never into it. |
@greghoyboy isn't 90% consistent with the current market? |
My first non-personal website from 1999: http://tinyurl.com/avm9l7 (idea: @trammell) |
@raisinbread have I contributed enough to write my own CakePHP book? :) |
@danjordan Webkit has an implementation but not sure if it made it into Safari http://tinyurl.com/6h3hd8 |
@zacharyjohnson Haha, no! Use advanced selectors. I was playing devil's advocate. Because the devil and I? We're like *this*. |
Remember when we all had blogs and we discussed things there? |
@MattWilcox: I think we should have CSS vars, but don't expect to use them for 5 yrs. :) |
@MattWilcox Use of CSS vars in near term would either reduce quality of design for majority or duplicate effort until users upgrade. |
@MattWilcox if you have to declare it twice, why use the variable? |
@jcroft eg: background-color: $sitecolor; What do all current browsers get? |
Biggest problem with CSS vars now is the lack of backwards compatibility. How do you degrade gracefully? |
@nateklaiber the processing overhead of CSS vars would be less than complex selectors, imo. |
