Oh, who hasn't been there? I totally agree upon using objects for related data. It's like using OpenLayers.Layer.WMS(title, url, url_params, options).<br>I'd be happy to see that principle applied throughout MapQuery, especially as we are probably starting to integrate it into Mapbender 3 during the Bolsena hacking event.<br>
<br>Cheers from the garden!<br> C<br><br><div class="gmail_quote">On Wed, Jun 1, 2011 at 4:19 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi all,<br>
<br>
the code sprint in Amsterdam comes closer. I guess (and hope) it will<br>
solidify the MapQuery API. It has gone to many changes. For example<br>
.layer() previously had a signature like:<br>
<br>
.layer(id, options)<br>
<br>
I then switched (proposed by Drew iirc) to<br>
<br>
.layer(options)<br>
<br>
I'd like to switch back again. My reasoning was this great article about<br>
arguments in JavaScript functions:<br>
<a href="http://blog.rebeccamurphey.com/objects-as-arguments-in-javascript-where-do-y" target="_blank">http://blog.rebeccamurphey.com/objects-as-arguments-in-javascript-where-do-y</a><br>
<br>
Please take your time and read through it, it's really worth it (even if<br>
you are not attending). I think for MapQuery I'd like to go mostly the<br>
"Use Objects for Related Data" path. In the case mentioned above I see<br>
the ID independent of the layer options.<br>
<br>
We should also look at other libraries to see what they are doing.<br>
<br>
Cheers,<br>
Volker<br>
_______________________________________________<br>
MapQuery mailing list<br>
<a href="mailto:MapQuery@lists.osgeo.org">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>
</blockquote></div><br>