thron7 wrote: > Hey Burak, > > thanks for the contribution. Can you say a word about OpenLayers and > what you used it for?! > > well, first thing i can say is that, just like any js library, it duplicates lots of work that qooxdoo already does (oo javascript, cross-browser code, minification, etc), sometimes poorly. i find qooxdoo's oo features to be much better designed than openlayers' for example. i wish there was an easy way to make it a native qooxdoo module.
the library delivers its promises. it is easy to integrate an existing non-supported map engine, the TMS layer is quite easy to implement on the server side. it supports multiple map backends, including popular ones like google maps. so instead of using e.g. google maps api, one could use openlayers to integrate google maps data to qooxdoo. this way, you won't be stuck to one single map engine. (i don't think it supports all of the gmaps api though) the work to integrate ol and qx looks negligible for a qooxdoo developer, but for a qooxdoo *user* who doesn't have to know, for example, exactly when a qooxdoo widget materializes as divs, it was surely educating :) finally, we use it for showing vehicles on maps and getting spatial input from the client. i hope what i said overlaps with what you had in mind when you asked me to talk about openlayers, thomas. best regards, burak ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
