Basic documentation needed

[GoogleCodeExporter]

This is a really useful project,especially because it does (amongst lots of 
other useful things) the one thing the google parser won't - ie placemarker 
links opening in the SAME page -  but it has taken me over 8 hours to get 
on top of it due the frustrating lack of documentation or basic examples 
with explanations.

This doesn't need to be long, but the essentials needed are;

1) The simplest example showing how to parse an external kml file using 
geoxml rather than GGeoxml which most users will be replacing. The 3rd 
party samples linked to from your site are unfortunately not really 
suitable as tutorial material.

2) Details on the options that are possible. I've had had to beautify the 
compressed script (which has no copyright information by the way, you might 
want to address that for the next release) and pour over the code just to 
find out basic information on how to style infowindow names. It needn't be 
this hard!

3) Ideally you would release a version that doesn't clash with jQuery's use 
of $. I know there are workarounds, but none are very satisfactory when you 
have perhaps 20 or 30 libraries in use. jQuery is probably the most popular 
framework out there and clashing with it isn't good for uptake of geoxml.

I stress it's a GREAT piece of work, but I'm sure the author could pull 
together the documentation that is needed in less than an hour and save 
countless programmers days of frustration as a result ;-)

Original issue reported on code.google.com by roger.mo...@gmail.com on 16 Jul 2009 at 4:12

[GoogleCodeExporter]

If the data is xml no... if you can get the data in another format like having 
it in
javascript then there is possibilities. (basically this is how GGeoXml works 
they
convert the xml in to javascript. 

Yes your godaddy account is prepending html soup to the beginning of your php 
proxy
response.

Original comment by lanceala...@gmail.com on 27 May 2010 at 8:46