<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: GeoKit: More Syntactic Sugar</title>
	<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Mon, 01 Dec 2008 22:59:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: yves</title>
		<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-5809</link>
		<pubDate>Tue, 29 May 2007 16:16:52 +0000</pubDate>
		<guid>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-5809</guid>
					<description>I have been using the plugin wo any problem until today : I needed to use the :range option and I discover that the find :range doesn't handle the exclusive option at all , I tried several cases :
p_exclusive = Proposition.find_by_range((0...2),  .. and got 89
p_exclusive =  Proposition.find_by_range(Range.new(0,2,true).. got 89

p_inclusive = Proposition.find_by_range((0..2),  .. and got 89
p_inclusive =  Proposition.find_by_range(Range.new(0,2,false).. got 89
p_inclusive =  Proposition.find_by_range(Range.new(0,2).. got 89

I know my result should be 86, I can exclude the 2..  but the generated SQL is always   </description>
		<content:encoded><![CDATA[<p>I have been using the plugin wo any problem until today : I needed to use the :range option and I discover that the find :range doesn&#8217;t handle the exclusive option at all , I tried several cases :<br />
p_exclusive = Proposition.find_by_range((0&#8230;2),  .. and got 89<br />
p_exclusive =  Proposition.find_by_range(Range.new(0,2,true).. got 89</p>
<p>p_inclusive = Proposition.find_by_range((0..2),  .. and got 89<br />
p_inclusive =  Proposition.find_by_range(Range.new(0,2,false).. got 89<br />
p_inclusive =  Proposition.find_by_range(Range.new(0,2).. got 89</p>
<p>I know my result should be 86, I can exclude the 2..  but the generated SQL is always
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Sascha Brink</title>
		<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-2311</link>
		<pubDate>Sat, 03 Mar 2007 13:47:18 +0000</pubDate>
		<guid>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-2311</guid>
					<description>@Jeroen: You're right. I've altered the tutorial a bit. Now GeoKit uses the YM4R-Key.

Just add to config/environment.rb:
GeoKit::Geocoders::GOOGLE= Ym4r::GmPlugin::ApiKey::GMAPS_API_KEY</description>
		<content:encoded><![CDATA[<p>@Jeroen: You&#8217;re right. I&#8217;ve altered the tutorial a bit. Now GeoKit uses the YM4R-Key.</p>
<p>Just add to config/environment.rb:<br />
GeoKit::Geocoders::GOOGLE= Ym4r::GmPlugin::ApiKey::GMAPS_API_KEY
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bill Eisenhauer</title>
		<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-643</link>
		<pubDate>Mon, 19 Feb 2007 15:24:50 +0000</pubDate>
		<guid>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-643</guid>
					<description>Yeah, well we aren't affiliated with the YM4R folks and well-behaved plugins usually namespace all their stuff so that they can co-exist peacefully.

If you don't like the duplication of keys, consider creating your own variable to keep the key and assign it to the various plugins that need it.  With this approach, you can preserve your DRY goals.

Otherwise, if that's the extent of your inconvenience, then you are doing pretty well.  The value of each plugin easily outweighs your concerns (IMHO).</description>
		<content:encoded><![CDATA[<p>Yeah, well we aren&#8217;t affiliated with the YM4R folks and well-behaved plugins usually namespace all their stuff so that they can co-exist peacefully.</p>
<p>If you don&#8217;t like the duplication of keys, consider creating your own variable to keep the key and assign it to the various plugins that need it.  With this approach, you can preserve your DRY goals.</p>
<p>Otherwise, if that&#8217;s the extent of your inconvenience, then you are doing pretty well.  The value of each plugin easily outweighs your concerns (IMHO).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeroen Zwartepoorte</title>
		<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-640</link>
		<pubDate>Mon, 19 Feb 2007 14:52:59 +0000</pubDate>
		<guid>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-640</guid>
					<description>Thanks, while not totally ideal (the plugins store their API keys in 2 different locations), it works ok.</description>
		<content:encoded><![CDATA[<p>Thanks, while not totally ideal (the plugins store their API keys in 2 different locations), it works ok.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Bill Eisenhauer</title>
		<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-637</link>
		<pubDate>Mon, 19 Feb 2007 13:33:51 +0000</pubDate>
		<guid>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-637</guid>
					<description>Check out this blog (though it is in German):

http://blog.ebenessen.de/2007/2/17/geokoordinaten-und-google-maps

where he's using the YM4R plugin.  He uses GeoKit and YM4R in a brief, but useful tutorial.</description>
		<content:encoded><![CDATA[<p>Check out this blog (though it is in German):</p>
<p><a href='http://blog.ebenessen.de/2007/2/17/geokoordinaten-und-google-maps' rel='nofollow'>http://blog.ebenessen.de/2007/2/17/geokoordinaten-und-google-maps</a></p>
<p>where he&#8217;s using the YM4R plugin.  He uses GeoKit and YM4R in a brief, but useful tutorial.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Jeroen Zwartepoorte</title>
		<link>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-636</link>
		<pubDate>Mon, 19 Feb 2007 13:01:27 +0000</pubDate>
		<guid>http://blog.billeisenhauer.com/2007/02/18/geokit-more-syntactic-sugar/#comment-636</guid>
					<description>Are there any plans to add support for using Google Maps in the view to display results from using geokit? If not, can you recommend a good plugin that fits well with geokit?</description>
		<content:encoded><![CDATA[<p>Are there any plans to add support for using Google Maps in the view to display results from using geokit? If not, can you recommend a good plugin that fits well with geokit?
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
