Chris Casciano: CSS properties box-shadow and rgba() and others like text-shadow are absolutely usable in the wild right now.
Works fine on elements that are position: fixed (example: my nav bar). When I try to put it on either my articles or my section h2s, scrolling becomes jerky on Firefox 3.5.3, but remains smooth on Chrome 4.0.222.5. Primary environment is Ubuntu 9.04, but I see similar things on Windows XP.
Having completed his tech training, my son is now stationed in Mountain Home, Idaho. In between, he took some leave, visited home and friends in NC and Virginia. Having a number of possessions he needed to get to his new base, including a car, he opted to drive. It is a tough trip, and doing so alone would have made it tougher, so I surveyed my options and decided to take the opportunity travel with him. I’m glad I did.
For existing applications, the changes needed will tend to be small and easily spotted. The biggest impact will be to books and tutorials. For new applications, this is all goodness. Edition 4 will be updated to reflect this change.
Brad Neuberg: View Source Tutorial: Fancy Web Page Using HTML5, CSS, and SVG [via Tim Strehle]
Not only is it a thing of beauty (both visually and from a view source perspective), it also nearly validates... and furthermore the validation errors are useful. This is hopefully an indicator of the way the web is heading.
With a little content negotiation and with this bug fixed, perhaps it could even work on IE.
Aditya Bansod: We created a new compiler front end that allowed LLVM to understand ActionScript 3 and used its existing ARM back end to output native ARM assembly code. We call this Ahead of Time (AOT) compilation—in contrast to the way Adobe Flash Player and Adobe AIR function on the desktop using Just in Time (JIT) compilation. Since we are able to compile ActionScript to ARM ahead of time, the application gets all the performance benefits that the JIT would offer and the license compliance of not requiring a runtime in the final application.
582331: The course is based on the course book: Agile Web Development with Rails, Pragmatic Bookshelf, Third Edition, 2009 (Sam Ruby, Dave Thomas, and David Hansson) (original)
Erik Dahlström: something like ".footer { background: url(my.svg); }"
Eric uses this technique on his site, unfortunately this demonstrates a limitation in the ability of CSS to define fallbacks for browsers which do not support SVG as background images — Firefox and Chrome, for example, show white text on a white background.
I’ve implemented this on my web site, but instead of browser sniffing, I sniff the URI.
Despite bringing my Windows laptop. Despite setting my display to 1024x768. Despite arriving early. Despite testing my laptop with the presentation equipment. Despite all of that, I still couldn’t present from my laptop when my time came. Brad was kind enough to swap time slots to allow me an opportunity to regroup, and further nice enough to let me use his laptop when I still could not present from my laptop despite a total and cold reboot.
Tony Ross: A Distributed Extensibility model for standard HTML is desirable because it means that user agents from different vendors that adhere to the standard can be assured of correctly processing mark-up that contains extensions without destroying the integrity of the document.
Alex Russell: Right now, we aren’t supporting the HTTP header (although we do support a separate MIME type, application/chromeframe)
Current tally: Google Chrome Frame violates HTML 4 by using http-equiv to specify something other than an HTTP header, it violates HTML 5 by using an unenumerated value for http-equiv, and violates RFC 2616 by not specifying the correct ACCEPT header.
After a bit of work, I have managed to produce a single scenario with some minor “if” checks that works any combination of Ruby 1.8.7 or 1.9.2 with Rails 2.3.4 or Rails 3.0. I’m now making the working assumption that Edition 4 of Agile Web Development with Rails will target Ruby 1.9.2 (which if tradition holds, will be available at Christmas 2009), but will work with only minor differences noted in the book with Ruby 1.8.7.
Primarily due to the help of wycats and nzkoz, I’ve got a decent feedback loop going between ongoing book development and ongoing Rails development. The root problem is that given the rate of change of Rails, every single tutorial and book out there is atrophying due to either intentional or unintentional changes to Rails.
My, admittedly selfish, goal is to be aware of any such change that affects either the current edition of AWDwR, or the one under development.
codeplex.org: Our contribution agreement. This serves as a template for how companies or individuals may make intellectual property cntributions[sic] to the Foundation.
If Microsoft’s goal was to be at arm’s length, I would have recommended that they follow Eclipse’s or Apache’s model. Copyright assignment may provide benefits down the road, and can work for obviously independent organizations like the FSF, but in this case I’m concerned that this may prevent a successful and sustainable bootstrap.
Update: Sam Ramji is leaving Microsoft. I did’t see that one coming.
Eliminated md5 deprecation warning when running with Python 2.6.
While I’m dog-fooding this myself, it might be wise to wait a few days to see what bugs shake out before upgrading. When the bugs are shaken out the result should be more secure (example: HTML5lib will sanitize URI schemes), and should also fix Mozilla bug 514534 without the need to resort to the application/xhtml+xml mime type, which causes other problems.