I have posted two questions recently concerning the printProvider and am posting what I have learned for those that may follow and make some of the same stupid mistakes I have made.
On the front end I did not know if printProvider and printPage were going to provide me with a nicely formatted output of headers, map, attributes and footer. The proof of concept went well and config.yaml wasn't difficult to figure out and I was very happy with the results. All my development was done with firefox using the printProvider GET method. I then realized that IE 7 & 8 versions had trouble parsing my urls and the GET url could easily become too long. I got stuck implementing the POST method, because of proxy problems, until Matt Priour pointed me to override-ext-ajax.js. I did not know that module existed. Including it in the geoext build was simple with the builder tool http://localhost/GeoExt-1.0/docs/builder/v1.0.html which I was also unaware of. The issues I had with using the <script> tag to load info.json or using the printProvider url: and autoload: did not have anything to do with geoext or the geoserver print module. They were caused by a firewall setting and the way I had set up apache proxy settings. Those issues did not affect my other mapping apps but they came to light when trying to get the printing to work. I would like to thank the geoext developers for such a great tool. Being able to produce a nicely formatted map is a significant step for me in continuing to develop our mapping apps with open source tools rather than former, current and future esri options. Ralph Dell
_______________________________________________ Users mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/users
