topic Re: 3.0 beta and beta in general for JSAPI in ArcGIS JavaScript Maps SDK Questions

3.0 beta and beta in general for JSAPI

TedCronin — Fri, 01 Jun 2012 19:14:10 GMT

How is beta handled with the javascript api? Beyond 3... Just incremental releases, or is there a semi formal beta channel for testing out new functionality?

Re: 3.0 beta and beta in general for JSAPI

derekswingley1 — Fri, 01 Jun 2012 19:54:53 GMT

Hi Ted,

We don't have a beta program. We occasionally announce a availability of a public RC but we don't have a formal or standard process for this.

3.0 is coming soon. Post-3.0, we plan to continue doing incremental releases every couple of months (the cliched "6-8 weeks" if you will).

Re: 3.0 beta and beta in general for JSAPI

TedCronin — Fri, 01 Jun 2012 20:15:40 GMT

Hey Derek -

Is there a list on what you will be supporting for 3?

Re: 3.0 beta and beta in general for JSAPI

derekswingley1 — Fri, 01 Jun 2012 20:29:44 GMT

There are quite a few things, here's a high level overview:
�??finalized support for new 10.1 features (refer to the "ArcGIS Server 10.1" book of samples here: http://helpdev.arcgis.com/en/webapi/javascript/arcgis/help/jssamples_start.htm)
�??enhancements to esri.request to automatically detect and use CORS
�??uses Dojo 1.7 (we're bundling the new dgrid with our API build too)
�??new Gauge dijit
�??new samples showing more mobile examples, point clustering via a custom layer, Gauge dijit usage, using a map service returned by a GP task and more samples showing ArcGIS Portal API usage
�??lots of bug fixes/enhancements, will be detailed in our "What's New in 3.0" doc

I'm also trying to finish up a tutorial on writing classes with JS and writing dijits for use with the JS API that we can publish with the release of 3.0.

Re: 3.0 beta and beta in general for JSAPI

TedCronin — Sat, 02 Jun 2012 17:57:36 GMT

There are quite a few things, here's a high level overview:
�??finalized support for new 10.1 features (refer to the "ArcGIS Server 10.1" book of samples here: http://helpdev.arcgis.com/en/webapi/javascript/arcgis/help/jssamples_start.htm)
�??enhancements to esri.request to automatically detect and use CORS
�??uses Dojo 1.7 (we're bundling the new dgrid with our API build too)
�??new Gauge dijit
�??new samples showing more mobile examples, point clustering via a custom layer, Gauge dijit usage, using a map service returned by a GP task and more samples showing ArcGIS Portal API usage
�??lots of bug fixes/enhancements, will be detailed in our "What's New in 3.0" doc

I'm also trying to finish up a tutorial on writing classes with JS and writing dijits for use with the JS API that we can publish with the release of 3.0.

Cool. Thank you. Your link is not public yet ;). 3 won't be out the same day as 10.1, right, it will be a few weeks later?

Re: 3.0 beta and beta in general for JSAPI

derekswingley1 — Sat, 02 Jun 2012 20:33:41 GMT

Cool. Thank you. Your link is not public yet 😉

My mistake, I meant to link to the currently public JS API samples page: http://help.arcgis.com/en/webapi/javascript/arcgis/help/jssamples_start.htm.

3 won't be out the same day as 10.1, right, it will be a few weeks later?

I honestly don't the know official date for 10.1. We should be ready to announce 3.0 officially in the next couple of weeks.

Re: 3.0 beta and beta in general for JSAPI

TedCronin — Sun, 03 Jun 2012 14:34:07 GMT

Couple weeks is the release window for 10.1, so wow, lots happening in June, should be a nice cycle. I assume you guys have a new help system coming on new Resource Center...

Look forward to seeing the tutorial you are working on. 🙂

Re: 3.0 beta and beta in general for JSAPI

CoreyAlix — Wed, 06 Jun 2012 12:15:20 GMT

In addition to all the great work you've already done it would be nice to see http://gmaps-utility-gis.googlecode.com/svn/trunk/ *eventually* merged into the official release. I'm not aware of any other solution for using google basemaps with JSAPI and I know presently it doesn't play well with AMD -- some reference issues when setting up the gallery. I'm sure Nianwei Liu will be quick to fix this but how nice if ESRI would take on this burden.