The IE Team has now updated the IE6 and 7 (w/ XP SP2) VPC Images. They have all the updates and are set to expire December 7, 2007.
If you don’t know about these, they’re Virtual PC “images” of Windows XP SP2 with either Internet Explorer 6 or Internet Explorer 7 installed. They’re great for cross-browser/Windows version testing purposes. You can see my previous post on them here.
Download IE6 or IE7 VPC Image (appox. 500-700 MB)
Download Virtual PC 2007 (appox. 30 MB)
Conditional comments are special HTML comments that can be used to do certain things in Internet Explorer only without using any scripting. They only work in Internet Explorer and were introduced starting with version 5. This can be quite useful when making a Website because all Browsers don’t display things exactly the same. Usually Opera, Safari and Firefox all display it alike, but Internet Explorer may display it differently (for me, usually correctly 😛 ). This is where you can use conditional comments to make IE use, say, some different CSS values than other Browsers.
Take Matt’s Blog’s current theme for example (the upcoming theme also does this). I use conditional comments to have a stylesheet called ie7style.css to be loaded if the Browser is Internet Explorer 7. In that stylesheet, it overrides values set in the main stylesheet to make the Sidebar display correctly in IE7. These conditional comments are only recognized in IE. Other browsers just see them as meaning-less HTML comments.
Conditional comments start are usually in the format of:
<!--[if <em>expression</em>]>Special IE Only HTML<![endif]-->
Usually (if not always) the expression contains “IE”. You can then add a version number after that (eg. “IE 7”). Here’s an example of what you would use if you wanted to show it to all versions (above 5) of IE:
<!--[if IE]>Will Show Up in Internet Explorer Only<![endif]-->
For IE 7 only:
<!--[if IE 7]>Will Show Up in Internet Explorer 7 Only<![endif]-->
You can only use operators such as less-than (lt), less-than or equal-to (lte), greater-than (gt) and greater-than or equal-to (gte). Here’s an example:
<!--[if gte IE 7]>Will Show Up in Internet Explorer 7 and Above Only<![endif]-->
Conditional comments are particularly useful for specifying IE only stylesheets that overwrite settings in the main stylesheet, to make your Site look good cross-browser.
You can see the full list of expressions in the Microsoft Developer Network.
Now, if only other Browsers would implement conditional comments…
WordPress 2.2.2 and 2.0.11 have been released. Anyone running older versions should upgrade immediately since they include security patches. Plus, they include some minor bug fixes.
I’ve upgraded, have you? If you haven’t, don’t wait or procrastinate, upgrade now, or you might regret it… 😀
The PHP Team has released End of Life information for PHP 4. There will be no more releases of PHP 4 after December 31, 2007 (the end of this year), and critical security issues will no longer be patched after August 8, 2008.
PHP 4 was initially released on May 22, 2000. PHP 4 was a huge step-up from PHP 3, and people started using it soon after it’s release. PHP 5 was initially released on July 13, 2004. Although PHP 5 offered much more better things than PHP 4, PHP 5 adoption was taken very slowly. Mostly because PHP 4 offered everything people needed, and PHP 5 just improved on those features and added some other stuff that people didn’t really need, but they were useful. Even today, in 2007, PHP 5 is still second to PHP 4.
Hopefully the PHP 4 EOL will start to make people use PHP 5. Let’s face it, PHP 4 obsolete. Hosts have plenty of time to get PHP 5 on their servers, and software writers have lots of time to make sure their software works on PHP 5.
PHP 5 adoption by hosts would go a lot quicker if software starting requiring a minimum of PHP 4. GoPHP5.org is trying to get software writers to make PHP 5.2 a minimum requirement.
We’ve had this discussion on the WordPress WP-Hackers mailing list a couple of times. The majority wants to make PHP 5(.2) a minimum requirement. The “lead developers” haven’t really said much on the discussion, though. Although, by the looks of this post that Matt Mullenweg (founder of WordPress) wrote on his Blog, it doesn’t look like it’ll be happening anytime soon…
iTunes 7.3.1 has been released which fixes a Library Saving error. I previously posted the workaround.
I must say, it’s good that Apple patched this. But, why did it take so long? iTunes 7.3 was released on June 29, 2007, and the fix was released July 12, 2007. That’s like 12 days! I doubt it took them more than an hour to fix it, and it’s not like they didn’t know about it, everybody was having the problem.
I’m disappointed in you Apple, even though I don’t really like you anyways… 😛
So, go download the update (Go Start > All Programs, click “Apple Software Update”).
You are currently browsing the archives for the Software category.