<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Adding handlers to Operator</title>
	<atom:link href="http://mike.kaply.com/2006/12/07/hello-world-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://mike.kaply.com/2006/12/07/hello-world-2/</link>
	<description>Mozilla, money, microformats and more</description>
	<lastBuildDate>Tue, 15 May 2012 05:27:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: Mike&#8217;s Musings &#187; Operator 0.7 is available</title>
		<link>http://mike.kaply.com/2006/12/07/hello-world-2/#comment-6</link>
		<dc:creator>Mike&#8217;s Musings &#187; Operator 0.7 is available</dc:creator>
		<pubDate>Wed, 04 Apr 2007 14:37:57 +0000</pubDate>
		<guid isPermaLink="false">http://kaply.com/weblog/?p=310#comment-6</guid>
		<description>[...] This release introduces a basic user interface for installing user scripts. Note that ability to add user scripts has always been there, I&#8217;ve just never had a good UI. User scripts can be used to add new microformats and new actions to Operator. As a part of the introduction of this UI, I&#8217;m moving some of what I call the non tier 1 microformats out of the core Operator and made them available as user scripts. My decision as to which ones to remove was mainly based on which microformats fit best into the Operator model; that is to say it is easy to provide actions that relate to the microformat. It is very important for you to realize that user scripts have FULL JavaScript privileges. Do NOT install Operator user scripts unless you trust the people that are providing them. I am going to make all my scripts available at http://www.kaply.com/weblog/operator-user-scripts/. If you want to write your own actions or microformats, feel free to look at my scripts, but please be aware that this API is very much in flux. I don&#8217;t a good versioning mechanism right now, so at some point your scripts would cease to work. Note that I continue to support the original Operator action model, but not the original Operator microformats model. The microformats model is actually pretty close to final. [...]</description>
		<content:encoded><![CDATA[<p>[...] This release introduces a basic user interface for installing user scripts. Note that ability to add user scripts has always been there, I&#8217;ve just never had a good UI. User scripts can be used to add new microformats and new actions to Operator. As a part of the introduction of this UI, I&#8217;m moving some of what I call the non tier 1 microformats out of the core Operator and made them available as user scripts. My decision as to which ones to remove was mainly based on which microformats fit best into the Operator model; that is to say it is easy to provide actions that relate to the microformat. It is very important for you to realize that user scripts have FULL JavaScript privileges. Do NOT install Operator user scripts unless you trust the people that are providing them. I am going to make all my scripts available at <a href="http://www.kaply.com/weblog/operator-user-scripts/" rel="nofollow">http://www.kaply.com/weblog/operator-user-scripts/</a>. If you want to write your own actions or microformats, feel free to look at my scripts, but please be aware that this API is very much in flux. I don&#8217;t a good versioning mechanism right now, so at some point your scripts would cease to work. Note that I continue to support the original Operator action model, but not the original Operator microformats model. The microformats model is actually pretty close to final. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Rukavina</title>
		<link>http://mike.kaply.com/2006/12/07/hello-world-2/#comment-5</link>
		<dc:creator>Peter Rukavina</dc:creator>
		<pubDate>Tue, 13 Feb 2007 14:02:46 +0000</pubDate>
		<guid isPermaLink="false">http://kaply.com/weblog/?p=310#comment-5</guid>
		<description>Thanks for this; I used what you provided, added a little detective work, and came up with a new handler for OpenStreetMap, the process of which I documented at:

http://ruk.ca/w/index.php/Making_an_OpenStreetMap_handler_for_Operator</description>
		<content:encoded><![CDATA[<p>Thanks for this; I used what you provided, added a little detective work, and came up with a new handler for OpenStreetMap, the process of which I documented at:</p>
<p><a href="http://ruk.ca/w/index.php/Making_an_OpenStreetMap_handler_for_Operator" rel="nofollow">http://ruk.ca/w/index.php/Making_an_OpenStreetMap_handler_for_Operator</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike&#8217;s Musings &#187; Adding new microformats to Operator</title>
		<link>http://mike.kaply.com/2006/12/07/hello-world-2/#comment-4</link>
		<dc:creator>Mike&#8217;s Musings &#187; Adding new microformats to Operator</dc:creator>
		<pubDate>Tue, 09 Jan 2007 23:30:22 +0000</pubDate>
		<guid isPermaLink="false">http://kaply.com/weblog/?p=310#comment-4</guid>
		<description>[...] Creating a handler was already covered in this post, so the main thing we need to see is how to access the hResume we just created. [...]</description>
		<content:encoded><![CDATA[<p>[...] Creating a handler was already covered in this post, so the main thing we need to see is how to access the hResume we just created. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Williams</title>
		<link>http://mike.kaply.com/2006/12/07/hello-world-2/#comment-3</link>
		<dc:creator>Jon Williams</dc:creator>
		<pubDate>Tue, 09 Jan 2007 21:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://kaply.com/weblog/?p=310#comment-3</guid>
		<description>Of course, with this kind of feature, a clearinghouse for extending Operator is needed, like UserScripts.org is for Greasemonkey. Have you talked with the Microformats.org people about providing it? That seems like a logical place.</description>
		<content:encoded><![CDATA[<p>Of course, with this kind of feature, a clearinghouse for extending Operator is needed, like UserScripts.org is for Greasemonkey. Have you talked with the Microformats.org people about providing it? That seems like a logical place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stoyan</title>
		<link>http://mike.kaply.com/2006/12/07/hello-world-2/#comment-2</link>
		<dc:creator>Stoyan</dc:creator>
		<pubDate>Tue, 09 Jan 2007 20:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://kaply.com/weblog/?p=310#comment-2</guid>
		<description>Thanks for this example and the Operator, Mike! The extensibility is one of the best features.

This example worked for me with no hiccups, the only thing you may want to add to the instructions is &quot;... and then restart your browser&quot;

Is there a place where I can check the JS API of the Microformats class.

Thanks again, amazing work!</description>
		<content:encoded><![CDATA[<p>Thanks for this example and the Operator, Mike! The extensibility is one of the best features.</p>
<p>This example worked for me with no hiccups, the only thing you may want to add to the instructions is &#8220;&#8230; and then restart your browser&#8221;</p>
<p>Is there a place where I can check the JS API of the Microformats class.</p>
<p>Thanks again, amazing work!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- This Quick Cache file was built for (  mike.kaply.com/2006/12/07/hello-world-2/feed/ ) in 0.33662 seconds, on May 16th, 2012 at 10:54 pm UTC. -->
<!-- This Quick Cache file will automatically expire ( and be re-built automatically ) on May 16th, 2012 at 11:54 pm UTC -->
