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)?
The Development team left out the navigation tools from the header in the beta release (to many other things to work on). If by final release they do not add them in then I will be releasing my custom header control widget that has them included. I'm not going to release any code for the beta AGS Flex API Map Viewer as there are to many things (code) in flux right now and it would be pointless. So just be a little patient until the viewer has gone final. There are many things to be fixed and added to the viewer right now.
When you talk about "navigation controls" - what do you really mean? 🙂 Is it "just" the Next/Previous functionality, like Josh mentions? What about initial extent? Or full (some sort of max) extent?
Which of them are most important (and thus what do you think should be our priority)?
When you talk about "navigation controls" - what do you really mean? 🙂 Is it "just" the Next/Previous functionality, like Josh mentions? What about initial extent? Or full (some sort of max) extent?
Which of them are most important (and thus what do you think should be our priority)?
For me, its more the "Zoom In", "Zoom Out", "Pan" buttons as the main priority. I personally have never been a big user of previous/next extent, but it seems like it would make sense to include them too. Its an interface that has been standard in ArcDesktop, ArcIMS, ArcGISServer WebADF, and FlexViewer1.3 and by now its something people have come to expect/use frequently.
Robert's list is excellent. With the WebADF being discontinued, it seems like the FlexViewer is the new long-term "out of the box" solution, so it really needs to be able to replace the ease and functionality of the WebADF map creation interface.
The one important addition I would add to Robert's list is a Buffer widget (or at least Buffer capabilities built into the Search widget like the ProximitySearch Widget that Robert(?) created for 1.3).
About the pan and zoom in/out, I'm still curious to why an application would need buttons for those specific actions.
Users can navigate the map by dragging the map (pan) and using the zoom in and out buttons of the navigation slider, as well as double-clicking to zoom in, or using the mouse wheel to zoom in/out. Consumer mapping sites like Bing Maps, Google Maps, and MapQuest all seem to work fine without specific navigation "states". I'm wondering why some developers want them and others don't. Is it because of legacy issues? Are your clients asking for it because their old sites had it, and/or they are used to it from other applications like ArcMap?
I think that it is both legacy and some use to those controls in ArcMap. I know in my case, my site serves a mainly computer illiterate user base so the site has to be very visual and simple to understand that is why I have made the zoom in and out tools work with single click and dragging a box. It amazes me when I watch a person from the public use my site and they just single click away on the map untill they get to the zoom level they want to be at. So much for all the time I invested in the sites help system and documentation...
I don't use the FlexViewer Bjorn, but I tried moving away from specific nav tools, like pan/zoom previous/zoom next/zoom out, but one of the first things users ask is, "hey, where is the zoom previous or pan button". I never should have put it in to begin with, but the users want what they want. Personally, I think a single zoom in would be fine, but apparently I'm too minimalist.
