The release of exportGge 0.93 may mark a turnaround in the development of the CartoWeb 3 branch. The integration of OpenLayers makes the php cartoclient obsolete. The result is less server side processing ( processing is now made inside the browser), a more snappy interface and faster speed of development for the web interface ( no more javascript/php plumbery ) . We get closer to the CartoWeb 4 = MapFish architecture but we keep good old PHP. Technically speaking the integration of OpenLayers was made possible by forging SOAP messages... with javascript. The browser communicates straight with the cartoserver part of CartoWeb through SOAP. It is questionable if CartoWeb 3 should stick to SOAP in the future because of it's verbosity , some alternatives like json might be a better choice but at least exportGge 0.93 pushes the limits of CartoWeb 3 a little bit further away and who knows might refresh some existing applications.Using OpenLayers for the CartoWeb client side allows to take advantage of the achievements of the OL community but also to contribute to this great framework. I guess that's something.
These are the improvement/features that come with exportGge 0.93:
Known issues:
Special thanks go to the authors of:
Javascript "SOAP Client" library : http://www.guru4.net/
geoxml : http://code.google.com/p/geoxml/
TrimPath JavaScript Templates : http://code.google.com/p/trimpath/wiki/JavaScriptTemplates
jquery tableFilter: http://ideamill.synaptrixgroup.com/?page_id=16
jsPDF : http://code.google.com/p/jspdf/
jvanulder extended OpenLayers layerswitcher : http://trac.openlayers.org/browser/sandbox/jvanulden/openlayers/lib/OpenLayers/Control/LayerSwitcher.js
proj4js : http://trac.osgeo.org/proj4js/
and also to the authors of the following jquery plugins :
cacheimage, cookies, truemouseout, jcache, jQuery Post, table2CSV
Loïc