Rank: Member
Groups: Member
Joined: 11/9/2007
Posts: 15
|
Hello, I would like to know whether there was any incompatibility of the essential controls objects and products ESRI.
The doubt is because we are a company that we are dedicated to developing Geographic information systems and thereby occupy different controls but by occupying callbacks for controls on the map do not match or clash with panelscallbacks of eo.web
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi Rafo,
While we strive to be compatible with as many third party products as we can, it is impossible for us to test every third party products out there, especially for some very field specific product such as ESRI. So we are unable to give you an answer on that one.
The most common compatibilities issue as to an AJAX solution has to do with client side JavaScript. As a general rule, if component A renders in place client side JavaScript, then it's very likely that it will have problem when placing in an AJAX panel (such as our CallbackPanel) and to be AJAX updated. When this occurs, there is no solution from the AJAX panel side. Component A itself has to change --- in another word, component A has to be prepared to be AJAXed. A typical example is Microsoft's own Menu control does not work with Microsoft's own ASP.NET AJAX extension. Because Menu is released with ASP.NET 2.0 and is not AJAX ready, there is no way to support it no matter what Microsoft does with ASP.NET AJAX. The change has to be made on the Menu side.
As an alternative, you may want to take a look of ASP.NET AJAX --- it comes from Microsoft so many component vendors are aware of it and they may support it.
Thanks
|