[geojquery] FOSS4G Code Sprint Summary
volker.mische at gmail.com
Tue Sep 14 07:34:09 EDT 2010
I should have sent this email earlier, but didn't find the time to. It
should get all the people to the same level of information that haven't
had the chance to attend to the FOSS4G code sprint.
After introducing ourselves (list of people that participated ), we
did some brain storming on how geojquery could look like. This also
included how jQuery-ish (or jQuery UI-ish for the widgets) we want to be.
The result was that the interaction with OpenLayers (what we call
"geojquery core") will use concepts of jQuery, but not be identical. So
people would need 2 paragraphs of documentation to understand the
concept, but then feel easy to use it. There is a map object (currently
called geoMap, so we don't clash with jQuery's .map()) that setups the
map and store information we might need for internal geojquery core use.
There is also a layer and a feature object. Those three elements (map,
layer, feature) need to be understood by the developer. It's still
blurry which function will return which kind of element, but in the end
it should be easy to use/understand and chainable (the question is e.g.
if a addLayer method should return the layer or the map object).
The other part are the widgets, we are calling "geojquery UI". These
will behave like jQuery UI widgets (and also use the jQuery UI widget
factory). They pollute the global namespace and return a jQuery object
so that you can do things like: $('#mtLegend').legend(options).hide().
More about the API with small examples is at the wiki .
We then decided to use the code I wrote back half a year ago for the
first version. We try to clone the functionality Anne has built for
EduGIS  (code is available at ).
A first prototype is already available in the main repository .
More information about the Mapquery