<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#ffffff">
<tt>Thanks Matt,<br>
<br>
I see that if you look in the source there are 2 different APIs also.
I suppose you should try to build to the public API and resort to using
the dev API when things don't work.<br>
<br>
Jim<br>
<br>
<br>
<br>
Actually, that is an intentional<br>
difference.<br>
The 1st link is to the 2.12 release API documentation. This is<br>
limited (by design) to public API methods (as marked in the docs<br>
within the code). Also since it is tied to the 2.12 release, it is<br>
a static snapshot of the api at the time of the latest 2.12<br>
release. The API methods are not supposed to change between<br>
releases and require at least 2 release cycles of deprecation<br>
warnings before being moved to the deprecated file and even then,<br>
by including the deprecated.js file, you can still get them back<br>
<br>
While, the 2nd link is to the 'trunk' or 'nightly' developer<br>
documentation. This documentation includes every documented method<br>
in every class and is updated every time a commit is made to the<br>
master branch of OpenLayers. The non-API methods may change or<br>
even be removed entirely between releases without warning or<br>
notice. Thus this documentation presents a very different view of<br>
the class methods and properties than the API documentation</tt>
<div class="moz-signature">-- <br>
James B. White<br>
Cary, NC<br>
H: 919-380-9615<br>
M: 919-698-1765<br>
<a href="http://whitecodingandmaps.com/">White Coding and Maps</a>
</div>
</body>
</html>