Compared with ESRI 9.3 and 9.2, the script library in the earlier part of ESRI is also changed to a Class Library Based on ASP. net ajax, which is hard to understand and has a big header! You can only look for information to chew on. Here we recommend a practical link:
Garden, more practical (AJAX tutorial)
Http://www.cnblogs.com/webabcd/archive/2008/02/25/1081194.html
Here we also recommend a tool Aptana to help you see the methods and objects in the new class library.
Http://www.cnblogs.com/jackielin/archive/2006/11/07/Aptana1.html
The following is a question about the client:
Question 1) ------ Add a DIV to the map
This is the case. In the original version 9.2, we added our own DIV on the map to display some information.
The original method only requires the event as follows (js script)
Map. divObject. ondblclick = creatshape // map is the map object of the client.
9.3 Implementation Method
Map. _ containerDiv. ondblclick = creatshape; // map is the map object of the client.
For example, if you add your DIV to the map
Var map = $ find (wave_mapid );
Map. _ containerDiv. appendChild (this. bqshape );
Question 2) ------ map coordinates
The client of 9.3 encapsulates its own coordinate method, which is much more convenient. You do not need to use it on the server. Please refer to the following column
Function ToImgXY (Tmapx, Tmapy)
{
Var temppt = new ESRI. ADF. Geometries. Point (Tmapx, Tmapy );
Var map = $ find (wave_mapid );
Var tmpobj = map. toScreenPoint (temppt); // coordinates of the GEO coordinate to the image
Return tmpobj;
}
// Return pt
Function ToMapXY (Timgx, Timgy)
{
Var map = $ find (wave_mapid );
Var tmpobj = map. toMapPoint (Timgx, Timgy); // returns ESRI. ADF. Geometries. Point
Return tmpobj;
}
Of course, the above is only about one or two aspects. ESRI's customers now have a good architecture, so it is very helpful to develop it, but it is not very clear about encapsulation.