Geocortex JavaScript API 2.2

Permanently deleted user

17 Maj 2012 03:50

(Continued from posting: “creating an overmap”)

Regarding the new Geocortex JavaScript API 2.2, that is available when you download the HTML5 SDK package.

 

The HTML 5 viewer is nice and all, but I don’t plan on using it for all of my HTML/JS mapping application needs. Yes, I could download the needed .JS file and use it locally. But since The recommended way to use the Geocortex Essentials JavaScript API is to use the JavaScript API file hosted by Geocortex.

I'd like to know if Geocortex plans to host it like it has other versions.

 

Also, when can look forward to updated documentation?

Thanks for all your hard work.

 

Tyler

0

• 

  Permanently deleted user

  11 Juni 2012 22:37

  Hi Tyler,

       The resource center was out of date. I've updated the information.

       The API is now an integral part of the Geocortex Viewer for HTML5 and will only be released as part of viewer releases. It is possible to use only the API from the viewer release but you will need to host it yourself alongside your application.

        Also note that features such as Geocortex Forms, commands and events are only available with the Viewer.

  Cheers,

  Christian.

  0
• 

  Permanently deleted user

  12 Juni 2012 00:07

  Yes, the API is an integral part of my Geocortex mapping site too. 

  Are Geocortex Forms part of the new API?  If so, why would they be limited to the HTML5  Viewer only?

  To me it seems the API and Viewer are two separate things, and it’s odd that someone needs to download a Viewer, in order to use the API.

  I’d hope the GeoCortex reconsiders its decision to host the API.

  Thanks,

   

  -Tyler

  0
• 

  Permanently deleted user

  12 Juni 2012 03:35

  Hi Tyler,

       The definition of Forms are part of the API. But JavaScript is not a rendering technology, HTML is, so for that reason, the rendering of the forms is done in the Viewer. For Silverlight and Flex it's different, because they provide the language and the rendering technology combined.

        Forms also use our databinding technology which is provided by the viewer. For all these reasons, the API is now bundled with the viewer. If your application doesn't need forms or commands or events, it can use the API file on its own.

        Hosting the API made sense when there was no viewer technology. And we'll continue to host the API up to version 2.1, so any applications built using the hosted files will continue to work. 

  Hope this provides a better explanation,

  Christian.

   

   

  0
• 

  Permanently deleted user

  12 Juni 2012 03:53

  Christian,

  Yes that's clear.

  thanks for the explanation.

  -Tyler

  0

Du måste logga in om du vill lämna en kommentar.