<?xml version="1.0" encoding="iso-8859-1"?><!-- generator="wordpress/2.0.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: mapkit :: new mashup tool by platial</title>
	<link>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/</link>
	<description>milk, cookies, and molecules [[ plus programming, GIS, and web mapping ]]</description>
	<pubDate>Wed, 07 Jan 2009 09:45:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.2</generator>

	<item>
		<title>by: mappgrrl</title>
		<link>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/#comment-171</link>
		<pubDate>Wed, 08 Nov 2006 15:44:51 +0000</pubDate>
		<guid>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/#comment-171</guid>
					<description>hi!  i added wisconsin.  it seemed to work!

your neighborhood rogue mapper,

mappgrrl</description>
		<content:encoded><![CDATA[<p>hi!  i added wisconsin.  it seemed to work!</p>
<p>your neighborhood rogue mapper,</p>
<p>mappgrrl
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: the new number two</title>
		<link>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/#comment-158</link>
		<pubDate>Fri, 03 Nov 2006 20:47:48 +0000</pubDate>
		<guid>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/#comment-158</guid>
					<description>&lt;p&gt;thanks for the comments, jason. i agree, putting a mapkit map inside a blog post would be a bit silly, because the map would soon disappear. however, putting a mapkit map on a wordpress page instead of a wordpress post would have value. since wordpress pages are stored and processed the same way that the posts are, a plugin such as text control would still be necessary.&lt;/p&gt;
&lt;p&gt;also, thanks for looking out re the busted plugin link. unfortunately, not sure what to say.  the link is correct and worked yesterday, but now the dev.wp-plugins.org site appears to be down. hopefully it will reemerge soon.&lt;/p&gt;</description>
		<content:encoded><![CDATA[<p>thanks for the comments, jason. i agree, putting a mapkit map inside a blog post would be a bit silly, because the map would soon disappear. however, putting a mapkit map on a wordpress page instead of a wordpress post would have value. since wordpress pages are stored and processed the same way that the posts are, a plugin such as text control would still be necessary.</p>
<p>also, thanks for looking out re the busted plugin link. unfortunately, not sure what to say.  the link is correct and worked yesterday, but now the dev.wp-plugins.org site appears to be down. hopefully it will reemerge soon.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: jason</title>
		<link>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/#comment-157</link>
		<pubDate>Fri, 03 Nov 2006 19:53:00 +0000</pubDate>
		<guid>http://schillerlabs.net/2006/11/02/mapkit-new-mashup-tool-by-platial/#comment-157</guid>
					<description>thanks for putting us to the test.  i hope it's clear that this is more or less an alpha release, trying to really figure out what people want, what people expect, and what people are bumping into bug wise.

question: with all the talk about how putting this into a blog post is quirky, there remains the question of what kind of value would a mapkit map really have inside a blog post vs on a static page somewhere.

that first error you got, can you drop me a line, i'm curious if it was a momentary glitch or something more.

also,
the wordpress plugin link above is busted.</description>
		<content:encoded><![CDATA[<p>thanks for putting us to the test.  i hope it&#8217;s clear that this is more or less an alpha release, trying to really figure out what people want, what people expect, and what people are bumping into bug wise.</p>
<p>question: with all the talk about how putting this into a blog post is quirky, there remains the question of what kind of value would a mapkit map really have inside a blog post vs on a static page somewhere.</p>
<p>that first error you got, can you drop me a line, i&#8217;m curious if it was a momentary glitch or something more.</p>
<p>also,<br />
the wordpress plugin link above is busted.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
