[MapQuery] comparing edugis and git code

[Volker Mische]

Thanks Steven,

sorry I didn't get around to send out a mail about the FOSSGIS yet. But
here's the reply to your mail.

I planed to make the vmx branch the new master one. It is based on the
work Drew Wells did. I haven't merged it as I heard from all this nice
EduGIS stuff at the FOSSGIS.

So the best would be to merge the EduGIS code with the vmx code. I
propose that you put your code into your own repo and then try to merge
it with the vmx code. The result should then become the new master.

The current existing widgets in the vmx branch are really more about
showing off what's possible/how MapQuery might look like, rather than
full blown widgets. They should be seen as templates for building your
own ones.

I've also added a few guidelines to the README, so that the widget names
are consistent. Feel free to revise them whenever you see a fit.

And finally, I really like the idea of having a distinction between UI
and non-UI widgets, got for it!

Cheers,
  Volker

On 04/12/2011 12:10 PM, Steven M. Ottens wrote:
> Hi Volker, others,
> 
> (Sorry, mail got out before I finished, so here the complete mail)
> 
> I've compared the mapquery code we're using for EduGIS
> (http://research.geodan.nl/edugis or http://kaart.edugis.nl) with the
> code in the master tree.
> 
> master:
> jquery.mapquery.core.js is almost untouched, we added a few more layer
> types line 83 (OSM, TMS, Google and an alert for unknown type)
> jquery.mapquery.layercontrol is exactly the same
> 
> missing in master are:
> jquery.mapquery.featureproperties.js
> jquery.mapquery.geosearch.js
> jquery.mapquery.history.js
> jquery.mapquery.legend.js
> jquery.mapquery.mouseposition.js
> jquery.mapquery.overviewmaps.js
> jquery.mapquery.permalink.js
> jquery.mapquery.scalebar.js
> jquery.mapquery.toc.js
> jquery.mapquery-ui.featureinfo.js
> jquery.mapquery-ui.legend.js
> 
> I noticed that the vmx branch is quite a bit different from master  (for
> instance var self has been introduced). The EduGIS code is very much
> coded in the style of the master. The master hasn't been touched for
> quite a while, so I would presume that new insights on how to do things
> have not ended up in the master branch.
> 
> As you can see there is quite a lot of code in the EduGIS code base, so
> the question is how do we proceed? I can put everything in a branch in
> git and than we start merging code with the vmx branch and other
> branches into a new master?
> 
> Also we introduced jquery.mapquery-ui for widgets which depend on
> jquery-ui so making it possible to do all kinds of nifty flashy
> thingies. But for those who do not need those or want to use a different
> ui library, the basic logic is still retained in it's sister in the
> jquery.mapquery namespace (eg jquery.mapquery.legend.js and
> jquery.mapquery-ui.legend.js)
> 
> regards,
> Steven
> 
> _______________________________________________
> MapQuery mailing list
> MapQuery at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapquery