Flex Viewer 2.2 released!

[BjornSvensson]

Today we released version 2.2 of both ArcGIS API for Flex and ArcGIS Viewer for Flex.

Among the highlights to both Flex API and Flex Viewer:
�?� Support for arcgis.com web maps
�?� Legend Component in the API and Legend Widget in the Viewer
�?� Undo/redo while editing

API 2.2 What�??s New
http://help.arcgis.com/en/webapi/flex/help/index.html#whats_new.htm

Viewer 2.2 What�??s New
http://help.arcgis.com/en/webapps/flexviewer/help/index.html#whats_new.htm

[AdrianComan1]

Hi dpaddock,

I made the change in config.xml on basemaps:

<layer
label="axa"
type="wms"
visible="true"
visiblelayers="0,2"
wkid="EPSG:31600"
url="http://localhost:8080/geoserver/wms"/>

and i received a blank page..ESRI logo si loaded and staying on Transferring data from localhost..

i have a crossdomain.xml if help.

[PedroGarcia]

Hi,

I would like to know if there is a problem with the print widget in that new version. Because of margin cuts the images displayed. Note: That doesn't happen in previous version.

Thanks.

[CynthiaMatney]

Hello.  I'm new to Flex.  I have been working with Flex Viewer 2.1 for the past couple of months and have changed a lot of the xml files and some of the mxml files as well. What do I need to do in order to migrate to Flex Viewer 2.2 in order to get the updates & fixes and not lose the stuff I've already done?

Thanks!
Cynthia

[DasaPaddock]

Hi dpaddock,

I made the change in config.xml on basemaps:

<layer
label="axa"
type="wms"
visible="true"
visiblelayers="0,2"
wkid="EPSG:31600"
url="http://localhost:8080/geoserver/wms"/>

and i received a blank page..ESRI logo si loaded and staying on Transferring data from localhost..

i have a crossdomain.xml if help.

The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.

[BjornSvensson]

Pedro, about the Print Widget:
The only changes to the Print Widget between 2.2. and 2.1 was related to localization.  The actual printing should be the same for both versions. 

Maybe the print differences you are seeing is based on the size of your browser at the time of printing.  For example, if you're browser is "tall", you will get get a different printout than if you resize to be "wide".

[BjornSvensson]

Cynthia (and others), to migrate your 2.1 viewers:

A) If working with the compiled version:

1. Download the new viewer.


2. Copy your modified xml's file over to the new viewer.


3. Review What's new to see if there's something new you want to take advantage of.

B) If working with the source code:

1. Download the new viewer.


2. Copy your modified xml's file over to the new viewer.


3. Review What's new to see if there's something new you want to take advantage of.


4. For changes made in the mxml files ... depends.  If it was something that was fixed, then do nothing.  For fixes that you want to migrate over, the best way is probably to compare that specific mxml and integrate your changes with ours.

[AdrianComan1]

The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.

Worked, Thank U; I wrote in config.xml:

<layer
label="axa"
type="wms"
visible="true"
visiblelayers="axa"
url="http://localhost:8080/geoserver/wms"/>

and it's work; Now, it is a way to overlay this data with bing maps, I suppose i have to put to basemap ..bing map and to operationallayers my wms, it will work? and how i do this.

Thank again.

[BrianCrumpler]

The wkid goes on the map tag, but it may not be needed. Make sure the visiblelayers match the available layer names. You may need to use a tool like HttpFox to see what the request/responses are.

Here's another example using the 2.2 viewer and the WMS feed - one that works and one that doesn't... It does look like this is a projection definition issue...

<layer label="NOAA Infrared Satellite"
type="wms"
visible="false"
visiblelayers="RAS_GOES_I4"
url="http://nowcoast.noaa.gov/wms/com.esri.wms.Esrimap/obs?service=wms"/>

<layer label="Nexrad Radar"
type="wms"
visible="true"
visiblelayers="nexrad-n0r"
url="http://mesonet.agron.iastate.edu/cgi-bin/wms/nexrad/n0r.cgi?"/>

The Iowa State link works but the Nowcoast one doesn't.  Iowa State has their service publishing in 102100 but Nowcoast only has the following (http://nowcoast.noaa.gov/help/mapservices.shtml):

SRS Identifier  Projection Name
EPSG:4267  North American Datum of 1927 (NAD 27)
EPSG:4269  North American Datum of 1983 (NAD 83)
EPSG:4326  World Geodetic System 1984 (WGS 84)
EPSG:102113  Web Mercator (ESRI Identifier)
EPSG:900913  Web Mercator (Google Identifier)

I have also tried adding in variables for SRS or WKID and they haven't worked, but removing them alltogether makes Iowa State work.


What would be helpful in the next go around would be to have the option to specify the SRS/WKID of the WMS layer since SRS is required by WMS (see http://help.arcgis.com/en/arcims/10.0/mainhelp/mergedprojects/wms_connect/wms_connector/get_map.htm).  While it is optimal for the WMS layer to be in the same projection, this is not always possible.  This is especially the case when using regional data (ie. national or multi-state like weather) and applying it to local or regional areas where the projections will be different.

Additionally, for cross-jurisdictional interoperability, there is a requirement to be able to leverage multiple projections either automatically or programmatically.  Much of your local, regional, federal and multi-state data will be in different projections and the ability to use WMS layers with other ArcGIS server layers should be simple to solve by adding a variable for WKID for the map layer.

If this isn't possible, then while WMS is added, it really doesn't work unless the WMS service provided has an option to output in the same projection as your other map layers which isn't always possible.

Thoughts?

Brian Crumpler - GIS Manager
Virginia Department of Emergency Management

[PedroGarcia]

Hi,

Could somebody explain how to integrate the esri geoportal extension widget to this new version (both compiled and source code)? All documentation I've found in forums and webhelp refers to previous versions.

Thanks.

[TimMcKinney]

Bjorn and others - 
Is there a preferred strategy for copying the 'modified xml's' to the new viewer while leaving enhancements to the new viewer intact?  In other words, is there a better/easier way to sync the old and new viewers rather than looking through all of the widgets and comparing code?  If I've modified a 2.1 widget, and the widget is improved a 2.2, I don't want to just copy my widget and replace the newer version, I want to merge the two. 

thanks

Tim