Jump to:
| Project: | KML |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I have been working on a KMLextras module (internal to my site initially, but I'll make it more flexible and submit it when I have time!) that is both a hack of the KML module and another module that uses that handy invoke_nodeapi call as well. At any rate, the two things that made me start this project were:
* KML module does not use CDATA for its field, it instead uses entity references (i.e. <h1> vs. ) via check_plain. This makes the KML file hard to read when you're crazy and actually want to read the KML file.
* Couldn't get KML to use the view fields for it's description - i.e. I wanted to have images, teasers, an a differently formatted title that was based on my theme's CSS. Right now I'm fiddling around with the format_placemark function and $args, but in the future support for grabbing information based on the view fields would be great!
Thanks for all the great work!
Comments
#1
Sorry about that accidental h1 up there... I meant to refer to the ampersand characters for HTML. Doh!
#2
#3
These both sound like very good suggestions. The views support is pretty new, so hopefully we can improve upon that to make it use more of the information available through the views module (like fields, arguments, etc). I've just set up a test site with views, cck, location, gmap and kml module to work on improvements to it.
#4
Switching to head - this will be implemented in the new version.
#5