Peter's Blog - Programming http://www.peterf.net/blog/ Not always right, but never wrong. en-us Peter F Tue, 10 Feb 2009 16:22:32 GMT newtelligence dasBlog 2.1.8102.813 peter@peterf.net peter@peterf.net http://www.peterf.net/blog/Trackback.aspx?guid=bdd78992-a084-40d7-a948-36476a8bc1c9 http://www.peterf.net/blog/pingback.aspx http://www.peterf.net/blog/PermaLink,guid,bdd78992-a084-40d7-a948-36476a8bc1c9.aspx Peter http://www.peterf.net/blog/CommentView,guid,bdd78992-a084-40d7-a948-36476a8bc1c9.aspx http://www.peterf.net/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=bdd78992-a084-40d7-a948-36476a8bc1c9 I've been programming for many years. I'm pretty good, but I'm no fool to think I am the best. One thing that has annoyed me was developers' blatant disregard for web standards. They keep throwing in <div> <center <p> in random places, refreshing the page to see how it looks, and saying "job done" when it looks the way they want. I still make little goofy mistakes like leaving an "&" without converting it to "&amp;", but that's the worst it should get.

I've adopted XHTML 1.1 for almost all of my sites* and decided to test it in IE8 RC1. One of my sites is http://www.newlenoxesda.net/. You can see the original site here that makes IE8 offer/recommend compatibility view. I loaded her up in IE8 and I got this cute little button telling me the site may not be compatible with IE8.




A few different angles here: IE 8 should be compatible with XHTML1.1 and therefore it should automatically know that a site listed as XHTML1.1 is IE8 compatible. Microsoft requires developers to add a meta tag to say the site is IE8 compatible. WHAAT? YOU HAVE TO BE KIDDING ME. I'm not a fan of the caps parade, but this is a insane. I thought we all were making progress by creating open standards and accepting other open standards? Why the hell should I have to worry about one more ****** browser I have to program for specifically? What about IE9? Will I need to have another tag for this? God help us if Firefox, Opera, and Safari decide they want to create a new version that wants a specific meta tag. I had to add Microsoft's recommendation/fix "<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" />" to make IE8 stop complaining.

There are still some pros to the compatibility view, but to force something proprietary like this is a bit disturbing. I'd be a fan of this if the IE8 engine was generating many errors, and THEN recommended the compatibility view.



*confession, my blog is not an example of this. I pay for shared hosting right now and it was the best choice


Internet Explorer 8 Compatibility View is a Joke http://www.peterf.net/blog/PermaLink,guid,bdd78992-a084-40d7-a948-36476a8bc1c9.aspx http://www.peterf.net/blog/2009/02/10/InternetExplorer8CompatibilityViewIsAJoke.aspx Tue, 10 Feb 2009 16:22:32 GMT I've been programming for many years. I'm pretty good, but I'm no fool to think I am the best. One thing that has annoyed me was developers' blatant disregard for web standards. They keep throwing in &lt;div&gt; &lt;center &lt;p&gt; in random places, refreshing the page to see how it looks, and saying "job done" when it looks the way they want. I still make little goofy mistakes like leaving an "&amp;" without converting it to "&amp;amp;", but that's the worst it should get.<br> <br> <img src="content/binary/ie8-compat-button.png" align="right">I've adopted <a href="http://www.w3.org/TR/xhtml11/">XHTML 1.1</a> for almost all of my sites* and decided to test it in IE8 RC1. One of my sites is <a href="http://www.newlenoxesda.net/">http://www.newlenoxesda.net/</a>. You can see the <a href="http://www.newlenoxesda.net/index-nonIE8.html">original site here</a> that makes IE8 offer/recommend <a href="http://blogs.msdn.com/ie/archive/2008/08/27/introducing-compatibility-view.aspx">compatibility view</a>. I loaded her up in IE8 and I got this cute little button telling me the site may not be compatible with IE8.<br> <br> <br> <br> <br> A few different angles here: IE 8 should be compatible with XHTML1.1 and therefore it should automatically know that a site listed as XHTML1.1 is IE8 compatible. Microsoft requires developers to add a meta tag to say the site is IE8 compatible. WHAAT? YOU HAVE TO BE KIDDING ME. I'm not a fan of the caps parade, but this is a insane. I thought we all were making progress by creating open standards and accepting other open standards? Why the hell should I have to worry about one more ****** browser I have to program for specifically? What about IE9? Will I need to have another tag for this? God help us if Firefox, Opera, and Safari decide they want to create a new version that wants a specific meta tag. I had to add <a href="http://msdn.microsoft.com/en-gb/library/cc817572.aspx">Microsoft's recommendation/fix</a> "&lt;meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8" /&gt;" to make IE8 stop complaining.<br> <br> There are still some pros to the compatibility view, but to force something proprietary like this is a bit disturbing. I'd be a fan of this if the IE8 engine was generating many errors, and THEN recommended the compatibility view. <br> <br> <br> <br> *confession, my blog is not an example of this. I pay for shared hosting right now and it was the best choice<br> <br> <br> <img temp_src="content/binary/Compatibility view recommended for XHTML 1.1 Valid site.png" src="content/binary/Compatibility%20view%20recommended%20for%20XHTML%201.1%20Valid%20site.png"> <p> </p> <img width="0" height="0" src="http://www.peterf.net/blog/aggbug.ashx?id=bdd78992-a084-40d7-a948-36476a8bc1c9" /> http://www.peterf.net/blog/CommentView,guid,bdd78992-a084-40d7-a948-36476a8bc1c9.aspx Programming Web http://www.peterf.net/blog/Trackback.aspx?guid=ebca51c2-a403-4ba4-999d-3a8cc1e78c60 http://www.peterf.net/blog/pingback.aspx http://www.peterf.net/blog/PermaLink,guid,ebca51c2-a403-4ba4-999d-3a8cc1e78c60.aspx Peter http://www.peterf.net/blog/CommentView,guid,ebca51c2-a403-4ba4-999d-3a8cc1e78c60.aspx http://www.peterf.net/blog/SyndicationService.asmx/GetEntryCommentsRss?guid=ebca51c2-a403-4ba4-999d-3a8cc1e78c60 This is my first post on my revived blog. I haven't blogged since my college days.  I've realized how important sharing of knowledge is, hence why I've dived back in.  Doing many nerdy things, I typically run into different blogs of people trying to do the similar tasks.  Sometimes, something has not been done before, and the knowledge stays with me once I complete it. So here we go!

For example, dasBlog 2.1.8102.813 so far seems to be a powerful, yet simple application not requiring an SQL backend.  There were not any specific write ups on a 1and1 install, so here you go:
Step 1: Upload files from dasblogce to a dir of your choice.
Step 2: Modify
web.config
comment <trust level="Medium" originUrl=".*" />
uncomment <httpCookies httpOnlyCookies="false"/>
SiteConfig\site.config
Modify obvious settings until <!-- END OF SUGGESTED SETTINGS -->
SiteConfig\siteSecurity.config
DO NOT CHANGE ADMIN PW.  It is encrypted. Log in and change it.
Step 3: Use WebFiles to modify permissions on the following directories: content, siteconfig, and logs.  Give NETWORK SERVICE full read/write/modify permissions
Step 4: Use WebFiles to create the WebApplicaion. Just point it to your subdir of your blog. Mine is /blog.
Step 5: Navigate to your blog, change your pw&options, and you're done!

Hello Internets http://www.peterf.net/blog/PermaLink,guid,ebca51c2-a403-4ba4-999d-3a8cc1e78c60.aspx http://www.peterf.net/blog/2008/05/27/HelloInternets.aspx Tue, 27 May 2008 15:48:15 GMT This is my first post on my revived blog. I haven't blogged since my college days.&nbsp; I've realized how important sharing of knowledge is, hence why I've dived back in.&nbsp; Doing many nerdy things, I typically run into different blogs of people trying to do the similar tasks.&nbsp; Sometimes, something has not been done before, and the knowledge stays with me once I complete it. So here we go!<br> <br> For example, dasBlog 2.1.8102.813 so far seems to be a powerful, yet simple application not requiring an SQL backend.&nbsp; There were not any specific write ups on a 1and1 install, so here you go:<br> Step 1: Upload files from dasblogce to a dir of your choice.<br> Step 2: Modify <br> <blockquote>web.config<br> <blockquote>comment &lt;trust level="Medium" originUrl=".*" /&gt;<br> uncomment &lt;httpCookies httpOnlyCookies="false"/&gt;<br> </blockquote>SiteConfig\site.config<br> <blockquote>Modify obvious settings until &lt;!-- END OF SUGGESTED SETTINGS --&gt;<br> </blockquote>SiteConfig\siteSecurity.config<br> <blockquote>DO NOT CHANGE ADMIN PW.&nbsp; It is encrypted. Log in and change it.<br> </blockquote></blockquote>Step 3: Use WebFiles to modify permissions on the following directories: content, siteconfig, and logs.&nbsp; Give NETWORK SERVICE full read/write/modify permissions<br> Step 4: Use WebFiles to create the WebApplicaion. Just point it to your subdir of your blog. Mine is /blog.<br> Step 5: Navigate to your blog, change your pw&amp;options, and you're done!<br> <p> </p> <img width="0" height="0" src="http://www.peterf.net/blog/aggbug.ashx?id=ebca51c2-a403-4ba4-999d-3a8cc1e78c60" /> http://www.peterf.net/blog/CommentView,guid,ebca51c2-a403-4ba4-999d-3a8cc1e78c60.aspx Programming Server