Navigation controls in FlexViewer 2?

[JoshuaKalov]

Are the navigation controls available somewhere in the new header with FlexViewer 2?  I can't seem to find a way to add navigation to the header.  Am I missing it, or are they excluded for some reason (despite being default/standard with the old header)?

Thanks

[CattyannCampbell]

I like Robert's list as well... I miss the zoom tools (zoom in/zoom out) and the identify tool.
Although I agree you can zoom in and out in many ways users are used to having those tools.
Buffer is a must...

Keep the widgets coming 😉

[MatthewLawton]

Robert, thank you for your lists and I agree they are dead on correct. When i showed my boss the Flex Viewer 2 template yesterday the first things he asked me were "Where are the navigation buttons?" and "Where is the Identify tool?".

Bjorn, you get an F- for your response. Instead of asking why customers want something (especially something as simple as navigation buttons) your response should be "We will get working on that ASAP!". It is nice to think that all of our apps are being consumed by 20-something web geeks, but the fact of the matter is that we have many people using our apps that are not Internet savvy. When they learn to zoom in on a map by clicking a Zoom In button, then by gosh they want that Zoom In button to be there every time.

Even if you think these tools are unnecessary, we need the option to add them. This is the concept of good legacy support.

[MarcWeinshenker]

I have another consideration for why nav controls should be available.   I want to make web mapping a suitable alternative to the desktop client for my users who are not good candidates for using desktop clients.  They still need to make maps to meet their needs, and to me that means having control over coordinate system and scale.  And that means State Plane rather than Web Mercator as well as arbitrary scale rather than pre-defined tile levels.  (Yes, I know this also means dynamic maps which take more time and resources).  So, in order to offer control over zooming to an arbitrary scale, I think it's natural to want to select a zoom tool to drag an extent and then make fine adjustments as needed.  That also implies the need for a pan tool since you need to have a way to switch functions.  And I think, under these circumstances, that previous and next extent functions also help in this scenario. 

Thanks,
Marc

[LeeAllen]

I agree with Robert's list as well.  I love using cached basemaps, and the scroll/slider zoom in/out are designed for navigation with the cache.  But there is no way all apps are going to have cached data.  For simple navigation, "click this tool and drag a box around the area you would like to zoom in to," is pretty easy.  The more options there are for navigation, the better chance of the user picking up on one of them.  I think these tools will help promote the use of the new Flexviewer and ease the transition for users.  The jump to web 2.0 is good for esri apps, and tools like these make esri apps stand out when compared to Bing or Google. FYI-It is not the developers that want these, it is the people using the apps that want them.