here are the exported module xml and the modified xsl file that i was discussing on gemini. 

these were my steps:
1) manage user defined table -> display settings (for current page) -> rendering method -> predefined xsl transformation -> show xsl source code
2) I saved that source onto my desktop and modifed it using stylus studio.  I added the google maps div tag and script block in the "detailview" xsl:template element.  I didnt' modify anythin to do with the search form (and i didnt' remove anything, only added that block of code).
3) uploaded the xsl under "user defined xsl transformation".  now the search is jank, sometimes workin on certain columns but not others, and sometimes not workin at all.

another thing i noticed.  only when i upload a custom xslt to the XslStylesheets/ directory do they work properly.  if I use an xslt uploaded to the portal root directory, i get "null reference" errors with the red triangle above my UDT.

don't know if this was intentional
when a Page Copy is performed, including a reference to the UDT on the copied page, all custom xsl is lost in the copy.  This applies as well when "Add Existing Module" is used to add a reference to the UDT existing on another page.  The new UDT is rendered using the default grid view.

I can think of situations where this would be preferable, but in my current situation i'd like it to be rendered using the same xsl on all pages.  there should be an option, somethin like "copy over custom xsl?" / "revert copy to default xsl settings?"