<?xml version="1.0" encoding="utf-8"?>

























	
	



	
	
	

	
		
		
		

		
		
			
			
			
			
		
	
	
	
	
	
	


<rss version="2.0">	
	<channel>
		<title>Radiant Core: joeclark tag</title>
		<link>http://www.radiantcore.com/</link>
		<description>All of the Radiant Core posts tagged with joeclark.</description>
		<language>en-ca</language>
		<copyright>Copyright 2006, Radiant Core Inc. All rights reserved.</copyright>
		<managingEditor>webmaster@radiantcore.com</managingEditor>
		<webMaster>webmaster@radiantcore.com</webMaster>
		
			
			
			
			
			
			
			
			

			
				
			
			<item>
				<title><![CDATA[HTML5 and CSS3]]></title>
				<author>Jay Goldman &lt;info@radiantcore.com&gt;</author>
				<link>http://www.radiantcore.com/blog/archives/21/10/2007/html5andcss3</link>
				<guid isPermaLink="true">http://www.radiantcore.com/blog/archives/21/10/2007/html5andcss3</guid>
				<comments>http://www.radiantcore.com/blog/archives/21/10/2007/html5andcss3#comments</comments>
				<description><![CDATA[<p>We currently write websites to the <a href="http://www.w3.org/TR/xhtml1/">XHTML 1.0 Strict</a> specs, which was published by the W3C in 2002 and extends the <a href="http://www.w3.org/TR/html4/">HTML 4.0 specs</a>, which were published in 1997-1999. Although it may not feel like it when you pay attention to sites like <a href="http://www.techcrunch.com" title="TechCrunch">TechCrunch</a>, the pace of change in the technologies which underly the web is actually remarkably slow. It would be fair to say, from a purely HTML-focused perspective, that there have been no major innovations in nearly ten years (if you don't count XHTML as anything more than a natural evolution of HTML). Even the<a href="http://www.w3.org/TR/CSS2/"> Cascading Style Sheets 2.0 spec (CSS2)</a> that we use to format and display websites is nearly ten years old, having been published in May 1998.</p><br /><br /><p>So, almost needless to say, we're getting really excited about the emerging drafts of the <a href="http://www.w3.org/html/wg/html5/">HTML5</a> and <a href="http://www.w3.org/Style/CSS/current-work">CSS3</a> specs. This may seem somewhat abstract to some of you, particularly if you don't do what we do, but it means your websites are 'about' to gain some great new functionality which will solve a number of the problems we bump into on a regular basis. Some things we're really looking forward to:</p><br /><br /><ul><li><strong>CSS3 Fonts:</strong> The technology to embed fonts in a web page was first specified a long time ago (so long ago that there's a <a href="http://www.webmonkey.com/design/fonts/tutorials/tutorial2.html" title="Webmonkey: Embedding Fonts">webmonkey tutorial</a>!), but support from the browser makers never materialized and it died in the water (for a complete history, I refer you to our esteemed colleague, <a href="http://joeclark.org" title="Joe Clark">Joe Clark</a>: <a href="http://blog.fawny.org/2007/09/13/simonda/" title="Joe Clark: Personal Blog">Simon&nbsp;Daniels: Web font embedding rides again!</a>). This is a very complicated issue given that the web exists in virtually every language on the planet (does your favourite font include a full set of <a href="http://en.wikipedia.org/wiki/Kanji" title="Wikipedia: Kanji">Kanji characters</a>?), and that fonts have licenses (just like other software) and many of those licenses prohibit things like embedding them in web pages. CSS3 brings it back to life with the <a href="http://www.w3.org/TR/css3-webfonts/#font-descriptions" title="W3C CSS3 Working Draft: @font-face">@font-face</a> at-rule, which means that we will finally be able to use something other than <span style="font-family: Verdana;">Verdana</span>, <span style="font-family: 'Trebuchet MS',Trebuchet;">Trebuchet</span>, <span style="font-family: Georgia;">Georgia<span>, and <span style="font-family: Arial;">Arial</span>.</span></span></li><li><strong>CSS3 Multiple Columns:</strong> Clients who are used to working with print layouts are often surprised to discover that there's no way to automatically layout HTML content in multiple columns. Sure, we can count out the total number of elements in a list, divide by two, then output the first half, end the column manually, and finally output the second half, but that's about as tedious as it sounds. The Multi-Column Module in CSS3 makes it about as simple as specifying: <pre>column-count: 2</pre> and Bob's your multi-column uncle.<br /></li><li><strong>HTML5 Client Side Storage:</strong> Of less import from a visual perspective, <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/section-sql.html#sql" title="W3C Working Draft: HTML5 4.11 Client Side Storage">Client Side Storage</a> gives web applications the ability to store data locally in the browser, which effectively makes the app accessible offline (e.g.: if you had a website which allowed people to store recipes and share them, client side storage would make those recipes available even when Tom's laptop wasn't connected to the Internet and he was in his kitchen making Duck à L'Orange). This is fundamentally similar to <a href="http://gears.google.com/" title="Google Gears">Google Gears</a>, but would mean that your site's visitors wouldn't need to install anything in their browser to make use of the technology. Congrats to Dave Hyatt and the WebKit team, who have <a href="http://webkit.org/blog/126/webkit-does-html5-client-side-database-storage/" title="Surfin' Safari: WebKit does Client Side Storage">announced preliminary support</a> in the latest nightly builds.<br /></li></ul><p>Keep in mind that we're a good five years away from actually being able to make use of these fun new features, since they'll have to get built into the next release of the major browsers, and then those will take some time to eventually replace the current versions in popular enough numbers to make the new stuff widely available. As always, we'll do our best to keep covering the new specifications for your ongoing edification, as well as to start producing some fun samples for you to play with once some browsers with HTML5 and CSS3 support become a little more stable and easy to download.</p>]]></description>
				<category>Tech Geekery, HTML/CSS</category>
				<pubDate>Sun, 21 Oct 2007 11:18:00 GMT</pubDate>
			</item>
		
			
			
			
			
			
			
			
			

			
				
			
			<item>
				<title><![CDATA[Fight for TTC Signage]]></title>
				<author>Jay Goldman &lt;info@radiantcore.com&gt;</author>
				<link>http://www.radiantcore.com/blog/archives/03/07/2007/ttcsignage</link>
				<guid isPermaLink="true">http://www.radiantcore.com/blog/archives/03/07/2007/ttcsignage</guid>
				<comments>http://www.radiantcore.com/blog/archives/03/07/2007/ttcsignage#comments</comments>
				<description><![CDATA[Regular readers will know we've got a thing for the <a href="http://www.radiantcore.com/blog/archives/16/01/2007/betteringthebetterway">TTC</a>. Some regular readers, particularly those who also read Joe Clark's <a href="http://www.fawny.org/">Fawny</a>, will know that we <a href="http://blog.fawny.org/2007/05/15/anticommons/">don't always agree with Mr. Clark</a>, especially when it comes to the TTC. That said, I think his <a href="http://joeclark.org/design/signage/TTC/activism/">campaign to save the old TTC signage</a> from St. George, Eglinton, Pape, Victoria Park, and Islington/Kipling needs all the support it can get and I encourage you to go read about it on his site, and to contact the Commission. <a href="http://joeclark.org/design/signage/TTC/redesign/">Paul Arthur's signs</a> (documented by Joe) are beautiful and original and far superior to the current inconsistent attempts at wayfinding which litter our transit system. If you care about design, transit, or our city, go read Joe's request and follow his instructions for contacting them. My email:<br /><br /><blockquote>General Secretary and Members of the TTC -<br /><br />I write as a concerned citizen and lover of Toronto's transit system, inspired by Mr. Joe Clark's weblog post regarding the removal and destruction of signage from the St. George, Pape, Victoria Park, Eglinton, and Islington/Kipling stations (see http://joeclark.org/design/signage/TTC/activism/). <br /><br />Our city's current renaissance is beautiful to behold but we must not forget that it is founded on a history - albeit a short one - full of people with equal passion and drive to see Toronto flourish. They may be gone but their work is not forgotten and it lives on (and is celebrated) in the intricacies and details of our collective history. Although the signage in those stations may need replacement for reasons of modernization or safety, it deserves to be preserved as part of the rich fabric that makes up the life of our city. Please take this request into consideration as a plea to donate those works to an institution or individual who will protect them with the respect they deserve. Mr. Arthur's papers reside at the ROM - perhaps they might take his St. George signage as well? I'm sure I speak for many of the TTC fans and supporters when I say that I would rather take on the responsibility of preserving one of the signs myself than to see them neglected and in a trash heap.<br /><br />Thank you for your time!</blockquote>]]></description>
				<category>Design</category>
				<pubDate>Tue, 03 Jul 2007 10:56:00 GMT</pubDate>
			</item>
		
	</channel>
</rss>