<p>Every one is more than welcome to share their opinions and examples of their experiences and frustrations with Ol.</p>
<p>I had the exact same experience myself.</p>
<p>I'd like to see a debug build which validates argument collections, both for required and unknown arguments. One which can be stripped out when building a single file. Also with some generous debug messages, as with my email the other day with the JSON issue.</p>
<p>Is it possible to generate full parameter examples via natural docs?<br>
</p>
<p>On 18 Jun 2010 18:49, "Richard Duivenvoorde" <<a href="mailto:rdmailings@duif.net">rdmailings@duif.net</a>> wrote:<br type="attribution">> <br>> Don't have so much credit to interfere, but<br>
> <br>> as a user I have seen users (mw) who made the mistake with eg the <br>> WMS-layer by putting param-arguments into the options-object and vice versa<br>> <br>> what about always 2 object arguments:<br>
> - the required<br>> - the optional (optional :-) )<br>> making it possible to check for the required (off course also possible <br>> with one object!)<br>> but for users googling for examples and copying code, it makes sense to <br>
> know that the first object will always be the required ones (so in all <br>> googled code snippets the same).<br>> Seeing code with 8 parameters (even in one object), not knowing which <br>> ones are really required is not that easy.<br>
> <br>> (though you can always read the api docs offcourse...)<br>> speaking of api-docs, it would be really nice to have the inherited <br>> required args, functions, props into a class definition also<br>> <br>
> Regards,<br>> <br>> Richard Duivenvoorde<br>> <br>> On 06/18/2010 01:22 AM, Schuyler Erle wrote:<br>>><br>>> On Jun 17, 2010, at 3:33 PM, Tim Schaub wrote:<br>>><br>>>> In adding the WMTS layer, I created a constructor that takes a single<br>
>>> argument. If others agree that this is the way forward, I think there<br>>>> is sense in getting used to it before 3.0.<br>>>><br>>>> I am bringing this up here because Chris objected to my commit of the<br>
>>> WMTS layer and reopened the ticket.<br>>>><br>>>> If anybody else has an opinion about the many versus one argument<br>>>> constructor, please weigh in.<br>>><br>>> I think that we can address this by placing a practical guideline on the number of arguments to any function in OL. For example, we could express a style guideline that any method that might take more than 3 arguments should use a dict instead of OR in addition to one or two fixed arguments. We can then require that any violation of this guideline be accompanied by a strong justification in the code comments.<br>
>><br>>> SDE<br>>> _______________________________________________<br>>> Dev mailing list<br>>> <a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>>> <a href="http://openlayers.org/mailman/listinfo/dev">http://openlayers.org/mailman/listinfo/dev</a><br>
> <br>> _______________________________________________<br>> Dev mailing list<br>> <a href="mailto:Dev@openlayers.org">Dev@openlayers.org</a><br>> <a href="http://openlayers.org/mailman/listinfo/dev">http://openlayers.org/mailman/listinfo/dev</a><br>
</p>