<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>blog - coda.coza &#187; edgars</title>
	<atom:link href="/blog/tag/edgars/feed" rel="self" type="application/rss+xml" />
	<link>http://coda.co.za/blog</link>
	<description>dress up. leave a false name. be legendary.</description>
	<lastBuildDate>Thu, 23 Jun 2011 05:01:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Back in the saddle!</title>
		<link>http://coda.co.za/blog/2003/05/05/back-in-the-saddle</link>
		<comments>http://coda.co.za/blog/2003/05/05/back-in-the-saddle#comments</comments>
		<pubDate>Mon, 05 May 2003 20:25:25 +0000</pubDate>
		<dc:creator>coda</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[digicam.coza]]></category>
		<category><![CDATA[edgars]]></category>
		<category><![CDATA[evangelism]]></category>
		<category><![CDATA[meskanky]]></category>
		<category><![CDATA[mozilla]]></category>
		<category><![CDATA[photography]]></category>
		<category><![CDATA[shooter]]></category>

		<guid isPermaLink="false">http://coda.co.za/blog/2003/05/05/back-in-the-saddle</guid>
		<description><![CDATA[All the photos (186), as well as a brief write-up from my 10-day road trip across the country, are online - check 'em out.
Also, meskanky.com has formulated a new concoction - the "MeSkanky Shooter". Give it a try at your favourite bar and help spread the love. We're still deciding on a suitable logo - [...]]]></description>
			<content:encoded><![CDATA[<p>All the <a href="http://digicam.co.za/gallery/categories.php?cat_id=44" title="03.04.23 - splashy fen music festival 2003 ">photos</a> (186), as well as a brief <a href="/blog/2003/05/05/splashy-fen-music-festival-2003">write-up</a> from my 10-day road trip across the country, are online - check 'em out.</p>
<p>Also, <a href="http://www.meskanky.com" title="MeSkanky network">meskanky.com</a> has formulated a new concoction - the "MeSkanky Shooter". Give it a try at your favourite bar and help spread the love. We're still deciding on a suitable <a href="http://photos.meskanky.com/draftlogos">logo</a> - let us know which you like most.</p>
<p>Looks like Nat is getting her shit together - <a href="http://www.rockit.za.net" title="ROCKIT">rockit.za.net</a> - nice one chick, keep us updated.</p>
<p>Elsewhere, <a href="http://www.edgars.co.za" title="Just imagine">Edgars</a> has finally allowed their website to work in Gecko-based browsers (Mozilla/Netscape/etc), much to my delight. You might remember I <a href="/blog/2002/11/25/the-new-edgars-website-just-imagine">reviewed</a> it a while ago. Congratulations guys, it wasn't such a terribly difficult thing to do now was it? Now maybe you can fix the other bugs... baby steps, you know. And in so doing, become a fine example of how it should be done to some of the <a href="/evangelism" title="the list">other sites</a> that act with ignorance.</p>
<p>Ready. Fire. Aim.</p>
<img src="/blog/?ak_action=api_record_view&id=369&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://coda.co.za/blog/2003/05/05/back-in-the-saddle/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The new Edgars website? Just imagine.</title>
		<link>http://coda.co.za/blog/2002/11/25/the-new-edgars-website-just-imagine</link>
		<comments>http://coda.co.za/blog/2002/11/25/the-new-edgars-website-just-imagine#comments</comments>
		<pubDate>Mon, 25 Nov 2002 20:44:40 +0000</pubDate>
		<dc:creator>coda</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[criticism]]></category>
		<category><![CDATA[edgars]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[website]]></category>
		<category><![CDATA[words]]></category>

		<guid isPermaLink="false">http://coda.co.za/blog/2002/11/25/the-new-edgars-website-just-imagine</guid>
		<description><![CDATA[During the beginning of November, I wrote briefly about the new Edgars website - www.edgars.co.za. Having visited again a few weeks later, I found that attempts had been made to correct almost everything that I had mentioned. Coincidence or not, the fact remains that nothing they changed is for the better.
My first impression of the [...]]]></description>
			<content:encoded><![CDATA[<p>During the beginning of November, I <a href="/archive/20021106/14:53:47/" title="archive link">wrote briefly</a> about the new Edgars website - <a href="http://www.edgars.co.za/">www.edgars.co.za</a>. Having visited again a few weeks later, I found that attempts had been made to correct almost everything that I had mentioned. Coincidence or not, the fact remains that nothing they changed is for the better.</p>
<p>My first impression of the site is that it's not new at all.</p>
<p>Edgars have taken the 'Microsoft Internet Explorer-only' approach and now find themselves listed with <a href="/list.php" title="the list">other like-minded local websites</a>. Meaning, if you visit their site with any other browser, you're completely banned from entering and end up <a href="http://www.edgars.co.za/BrowserNotValid.htm">here</a>, an unpresentable page reading "edgars.co.za has been designed for Internet Explorer version 5 or greater".</p>
<p>It makes me think back to the days when the browser wars were still raging, and for many web developers it was either support one browser or the other. Supporting both meant an increase in research &amp; development time, and a larger project budget to account for these changes, among other things.</p>
<p>Luckily for us, those days are over. Browser manufacturers have come to realise the benefits of supporting <a href="http://www.w3c.org/" title="The World Wide Web Consortium">W3C</a> standards - allowing us to create a single, standard-compliant website that is accessible by all users, independent of their browser, operating system, platform, etc. Eventually the same website will be accessible by mobiles and other portable devices; in some instances there isn't reason why they shouldn't be already.</p>
<p>You might argue that Internet Explorer has dominance in the user market and there is little motivation to support the other 10% of the browsers. Or that modern browsers are still too buggy and inconsistent in the way they render your pages. If that's the case, you're clearly uninformed and are more than likely just repeating what someone told you <a href="http://www.blooberry.com/indexdot/history/browsers.htm" title="Browser Timelines">five years ago</a> when Netscape 4 and Internet Explorer 4 were first released. The web has evolved and matured, and with multiple case studies and reports on hand, so have our perceptions.</p>
<p><a href="http://www.digital-web.com/features/feature_2002-09.shtml" title="An excerpt from Forward Compatibility: Designing &amp; Building With Standards">Forward compatibility</a> has taken a front seat over backward compatibility - would you rather develop a website to cater for browsers two years old, or future browsers two years from today, considering how rapidly web technology is moving?</p>
<p>Not a single part of the Edgars website frontend is IE specific. So unable to find a single reason for their decision, I sent them an e-mail, only to receive reply that my questions had been forwarded. I haven't heard anything since. So, curious to discover the rest of the site, I took a deep breath, forced myself to open Internet Explorer and proceeded.</p>
<p>The first thing I noticed was the popup window, with rather amusing content. It reads: "This site has been designed to support your preferred browser text size". But it should read "This site has been designed to support your browser's text size preference" - since Internet Explorer is NOT my preferred browser. Not only that, but the average web user might ask themselves why an online retailed is providing them with instructions on how to change their browser's text size settings?</p>
<p>Quick investigation reveals that their style sheet has specified the <code>font-size</code> for the site as "smaller", which is more than likely leaving the text unreadable in particular circumstances. Providing a popup window with instructions for the visitor to solve it themselves is nothing more than a feeble excuse for a solution.</p>
<p>The next thing I noticed was the new colour scheme, replacing the bright summer blues they had previously. Fair enough, they're acknowledging the Festive Season. The layout however is still inconsistent. Depending on your screen resolution, the width of the site extends only to whatever the page contains, so in some cases the layout will stretch to fit your browser width, and in some cases it only fills half your screen.</p>
<p>Having clicked through the menu and now at some product page, I want to go back to the opening page. There is no visible link that will return you to their home page. But having years of experience on the web, I know that a logo is usually a means for returning to the home page. Previously, clicking on the logo would have resized your browser and moved it across your desktop to a new location. So, expecting the worst, I mouse over the logo. My mouse cursor remains the same, but if I leave it there long enough, the alternative text of the image appears reading "return to home page" (<span title="return to home page">example</span>). I click on the logo and it directs me back. Seem ok? Not quiet.</p>
<p>1. The average user will not know to do this, and even if they did, there is no visible indication that this logo is a link until clicked or unless they mouse over it until the image's alternative text appears.<br />
2. The reason for no visible mouse cursor change is that they use JavaScript for the link. Take into consideration that 11% of web users have JavaScript disabled, and you have an unnecessary accessibility flaw, and four lines of JavaScript code that could be replaced with the most basic anchor link. It sounds trivial, but it all adds up in an environment where size matters.</p>
<p>The more I browse through the site, the more impression I get that it was launched incomplete, with the intent to make the most of the Christmas season and the related spike in online spending. As a developer I'm very familiar with the "shortcuts" you can take to complete a site before deadline. While I've never been in this situation myself, it would seem that Edgars were. One of these shortcuts is using images instead of text - dropping a single image into a page is so much faster than styling and laying out the text around the image. The accessibility problems with applying this shortcut are obvious, excluding the fact that their popup message mentioned earlier is completely meaningless when applied to this context.</p>
<p>I haven't come across other major updates, other than their changing the logo to no longer contain their slogan, "Just Imagine", which would make sense since users without Internet Explorer wouldn't see the irony in this slogan anyway, and know that they'd need to "Just Imagine".</p>
<p>All things said, the site does download quickly and the design is fairly clean and easy to navigate despite the above-mentioned flaws. But until they realise the <a href="http://www.w3.org/QA/2002/07/WebAgency-Requirements" title="Buy standards compliant Web sites">benefits</a> and accept my browser of choice, <a href="http://www.mozilla.org/" title="an open-source web browser and toolkit, designed for standards compliance, performance and portability">Mozilla</a>, I'm quite happy to spend my money elsewhere, along with the rest of their visitors who are denied access.</p>
<img src="/blog/?ak_action=api_record_view&id=258&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://coda.co.za/blog/2002/11/25/the-new-edgars-website-just-imagine/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Edgars website update</title>
		<link>http://coda.co.za/blog/2002/11/25/edgars-website-update</link>
		<comments>http://coda.co.za/blog/2002/11/25/edgars-website-update#comments</comments>
		<pubDate>Mon, 25 Nov 2002 21:00:08 +0000</pubDate>
		<dc:creator>coda</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[criticism]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[edgars]]></category>
		<category><![CDATA[layout]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://coda.co.za/blog/2002/11/25/edgars-website-update</guid>
		<description><![CDATA[At the beginning of this month, I wrote briefly about the new Edgars website - www.edgars.co.za. Having visited again a few weeks later, I find that attempts have been made to correct almost everything that I had mentioned. Coincidence or not, the fact remains that nothing they've changed is for the better. Read my full [...]]]></description>
			<content:encoded><![CDATA[<p>At the beginning of this month, I <a href="/archive/20021106/14:53:47/" title="archive link">wrote briefly</a> about the new Edgars website - <a href="http://www.edgars.co.za">www.edgars.co.za</a>. Having visited again a few weeks later, I find that attempts have been made to correct almost everything that I had mentioned. Coincidence or not, the fact remains that nothing they've changed is for the better. <a href="/blog/2002/11/25/the-new-edgars-website-just-imagine" title="The new Edgars website? Just imagine.">Read my full review</a>...</p>
<p><a href="http://www.digiguru.co.za" title="'03 DIGIGURU">Craig</a> has a stylish new splash page.... can't wait for the site!</p>
<img src="/blog/?ak_action=api_record_view&id=259&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://coda.co.za/blog/2002/11/25/edgars-website-update/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Computicket.com blocked in Mozilla</title>
		<link>http://coda.co.za/blog/2002/11/12/computicketcom-blocked-in-mozilla</link>
		<comments>http://coda.co.za/blog/2002/11/12/computicketcom-blocked-in-mozilla#comments</comments>
		<pubDate>Tue, 12 Nov 2002 19:43:03 +0000</pubDate>
		<dc:creator>coda</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[computicket]]></category>
		<category><![CDATA[criticism]]></category>
		<category><![CDATA[css]]></category>
		<category><![CDATA[edgars]]></category>
		<category><![CDATA[internet explorer]]></category>
		<category><![CDATA[mozilla]]></category>
		<category><![CDATA[rant]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[technology]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://coda.co.za/blog/2002/11/12/computicketcom-blocked-in-mozilla</guid>
		<description><![CDATA[Unlike the new Edgars website (I ranted about it here), if you visit Computicket's website in Mozilla you're not excluded from viewing the site. But you do end up at their test web site. My first thought was that they'd redesigned again and were experimenting with IE-specific CSS layouts, but as it turns out their [...]]]></description>
			<content:encoded><![CDATA[<p>Unlike the new Edgars website (I ranted about it <a href="/archive/20021106/14:53:47/">here</a>), if you visit Computicket's website in <acronym title="Mozilla 1.2 expected release date next week sometime">Mozilla</acronym> you're not excluded from viewing the site. But you do end up at their <a href="http://www.computicket.com/computicket/booking/">test web site</a>. My first thought was that they'd redesigned again and were experimenting with IE-specific CSS layouts, but as it turns out their browser-detection script, or whatever does redirection, is the culprit. I could be wrong, but either way, they've fucked up and I've let them know about it.</p>
<p>Still waiting for Edgars to respond to my e-mail, when or if they do I will definately share their answers here.</p>
<img src="/blog/?ak_action=api_record_view&id=244&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://coda.co.za/blog/2002/11/12/computicketcom-blocked-in-mozilla/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Edgars: just imagine</title>
		<link>http://coda.co.za/blog/2002/11/06/edgars-just-imagine</link>
		<comments>http://coda.co.za/blog/2002/11/06/edgars-just-imagine#comments</comments>
		<pubDate>Wed, 06 Nov 2002 14:53:47 +0000</pubDate>
		<dc:creator>coda</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[criticism]]></category>
		<category><![CDATA[design]]></category>
		<category><![CDATA[development]]></category>
		<category><![CDATA[edgars]]></category>
		<category><![CDATA[rant]]></category>
		<category><![CDATA[review]]></category>
		<category><![CDATA[standards]]></category>
		<category><![CDATA[web]]></category>

		<guid isPermaLink="false">http://coda.co.za/blog/2002/11/06/edgars-just-imagine</guid>
		<description><![CDATA[Acidman just directed me to the new Edgars website. Wow, incredible stuff. How ironic that their slogan is "just imagine"...
Even when you do visit the site with their specified browser of choice, you are presented with an inconsistently-sized layout, images in place of text, a dynamic menu with a font size so tiny that it's [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.digitalsewer.net" title="reasoning with optimists">Acidman</a> just directed me to the new <a href="http://www.edgars.co.za/BrowserNotValid.htm" title="edgars.co.za">Edgars</a> website. Wow, incredible stuff. How ironic that their slogan is "just imagine"...</p>
<p>Even when you do visit the site with their specified browser of choice, you are presented with an inconsistently-sized layout, images in place of text, a dynamic menu with a font size so tiny that it's unreadable, and no way of getting back to the homepage - clicking on the logo simply resizes your browser window to the dimentions of 800x600 and moves it to a new location on your desktop.</p>
<p>Quite possibly the worse example of frontend web development I have seen in a while, <a href="/evangelism">among others</a>.</p>
<img src="/blog/?ak_action=api_record_view&id=241&type=feed" alt="" />]]></content:encoded>
			<wfw:commentRss>http://coda.co.za/blog/2002/11/06/edgars-just-imagine/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

