Hi,<br><br>I would suggest using a branch on your repository, too. If people enjoy what they see, it'll end up in the master repo in some way or form someday :)<br>I'm looking forward to it!<br><br>Cheers,<br> C<br>
<br><div class="gmail_quote">On Mon, Nov 29, 2010 at 2:11 PM, Volker Mische <span dir="ltr"><<a href="mailto:volker.mische@gmail.com">volker.mische@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On 29.11.2010 12:16, Anne Blankert wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Hello List,<br>
<br>
I started re-arranging the 'EduGIS' application, so that it conforms<br>
somewhat more to the current MapQuery setup.<br>
<br>
I now have two types of widgets/plugins:<br>
<br>
non-ui widgets<br>
ui widgets<br>
<br>
The difference is wether or not they depend on jquery-ui.<br>
<br>
For the legend I now have two versions:<br>
jquery.mapquery.legend.js<br>
jquery.mapquery-ui.legend.js<br>
<br>
The ui version of legend uses the non-ui version and adds such things as<br>
dragging/dropping/sorting<br>
<br>
The list that I currently have is:<br>
jquery.mapquery-ui.featureinfo.js<br>
jquery.mapquery-ui.legend.js<br>
<br>
jquery.mapquery.core.js<br>
jquery.mapquery.geosearch.js<br>
jquery.mapquery.layercontrol.js<br>
jquery.mapquery.legend.js<br>
jquery.mapquery.mouseposition.js<br>
jquery.mapquery.overviewmap.js<br>
jquery.mapquery.scalebar.js<br>
jquery.mapquery.toc.js<br>
<br>
The functionality in my jquery.mapquery-ui.featureinfo.js probably<br>
overlaps with the 'Popups for features' that Volker is working on.<br>
<br>
I would be happy to share the above plugins, but these are far from<br>
ready. Documentation is lacking, some fixed strings are still in the<br>
code, missing unit tests, missing examples, not to mention the fact that<br>
the overall structure of the plugins may require some rearranging.<br>
<br>
How do you think we should proceed? Should there be some 'central'<br>
sandbox version where people can submit ongoing work or should they just<br>
create separate git repositories and tell people about it?<br>
</blockquote>
<br></div></div>
I think the way to go is to create a branch in your own MapQuery repository. Perhaps create a wiki page that contains some information, so people can find it (and also send a mail to the mailing list).<div><div></div><div class="h5">
<br>
<br>
Cheers,<br>
Volker<br>
_______________________________________________<br>
MapQuery mailing list<br>
<a href="mailto:MapQuery@lists.osgeo.org" target="_blank">MapQuery@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapquery" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapquery</a><br>
</div></div></blockquote></div><br>