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

























	
	



	
		
		
			
			
			
		

		
		
			
			
			
			
		
	
	
	

	
	
	
	
	
	


<rss version="2.0">	
	<channel>
		<title>Radiant Core: XUL</title>
		<link>http://www.radiantcore.com/</link>
		<description>All of the Radiant Core posts from the XUL category.</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[A XUL Development Primer]]></title>
				<author>Jay Goldman &lt;info@radiantcore.com&gt;</author>
				<link>http://www.radiantcore.com/blog/archives/03/07/2006/xuldevprimer</link>
				<guid isPermaLink="true">http://www.radiantcore.com/blog/archives/03/07/2006/xuldevprimer</guid>
				<comments>http://www.radiantcore.com/blog/archives/03/07/2006/xuldevprimer#comments</comments>
				<description><![CDATA[We've started doing a fair bit of work with XUL, the Mozilla XML-based User Interface Language (there's a hint in there about a big upcoming announcement for the In-Between-Line-Readers among you). It's a really interesting environment to work in and really easy to learn since the entire Firefox browser is built in XUL and you can take it apart to study by example.<br /><br />Now that we've clocked in a couple of days worth, we thought we'd share a few quick tips for those aspiring extension developers:<br /><br /><ol><li>You can use the DOM Inspector to look inside any element of <span style="font-style: italic;">chrome</span>, the term Mozilla uses to refer to the browser's interface. Just open the inspector and use the URL to your chrome as the address - try chrome://browser/content/browser.xul to pick apart the browser's interface.</li><li>You can use Venkman, the Mozilla JavaScript debugger, to step through you component's code too. If you're running Firefox (as opposed to Mozilla), you'll need to grab the <a href="http://www.mozilla.org/projects/venkman/">Venkman Extension</a> first, then launch it from the <span style="font-style: italic;">Tools</span> menu. You won't see any <span style="font-style: italic;">chrome</span> files at first, but they'll all show up if you turn off <span style="font-style: italic;">Exclude Browser Files</span> in the <span style="font-style: italic;">Debug</span> menu. Make sure that the component you want to debug is actually open or the files won't be listed (i.e.: if you're trying to debug a window, open the window once to get the files listed, set a breakpoint, close and reopen).</li><li>This one's a little more obscure but might save you a whole bunch of hair pulling - you can load a <span style="font-style: italic;">stringbundle</span> from inside an <span style="font-style: italic;">overlay</span> on a <span style="font-style: italic;">window</span>, and the bundle will be visible in the DOM Inspector, but you won't be able to access it using JavaScript. Seems to be a bug, though we couldn't find anything listed in <a href="https://bugzilla.mozilla.org/">BugZilla</a>. You can insert the <span style="font-style: italic;">stringbundle</span> in the JavaScript first and then insert it into the <span style="font-style: italic;">window,</span> or you can just put the <span style="font-style: italic;">stringbundle</span> into the <span style="font-style: italic;">window</span> instead. If anyone has a better workaround, we'd love to hear it.<br /></li></ol>  That's it for the first installment - stay tuned as we learn more :)<br />]]></description>
				<category>Tech Geekery, XUL</category>
				<pubDate>Mon, 03 Jul 2006 18:11:00 GMT</pubDate>
			</item>
		
	</channel>
</rss>