[MapQuery] Must read before code sprint

[Christian Wygoda]

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).
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.

Cheers from the garden!
 C

On Wed, Jun 1, 2011 at 4:19 PM, Volker Mische <volker.mische at gmail.com>wrote:

> Hi all,
>
> the code sprint in Amsterdam comes closer. I guess (and hope) it will
> solidify the MapQuery API. It has gone to many changes. For example
> .layer() previously had a signature like:
>
>  .layer(id, options)
>
> I then switched (proposed by Drew iirc) to
>
>  .layer(options)
>
> I'd like to switch back again. My reasoning was this great article about
> arguments in JavaScript functions:
>
> http://blog.rebeccamurphey.com/objects-as-arguments-in-javascript-where-do-y
>
> Please take your time and read through it, it's really worth it (even if
> you are not attending). I think for MapQuery I'd like to go mostly the
> "Use Objects for Related Data" path. In the case mentioned above I see
> the ID independent of the layer options.
>
> We should also look at other libraries to see what they are doing.
>
> Cheers,
>  Volker
> _______________________________________________
> MapQuery mailing list
> MapQuery at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapquery
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osgeo.org/pipermail/mapquery/attachments/20110602/bc409458/attachment.html