Thanks for chiming in!
Q1: What do you mean with image linking ability? Having it show an image that when clicked goes to a URL or having a link that when clicked shows an image (either right there or outside of the app)?
A1) Based on my testing it seems like with the existing samples I can either point it to one URL field (i.e. create a hyperlink) OR point to one field with a path to a picture. In many of my data sets I have both, or even multiple hyperlinks. So it would be nice if the identify was more like the one found in ArcMap, that could handle multiple linkages. It would also be nice to not have to set this up each time in a config file, since we have close to 40 web maps running at my organization.
Q2: Where would your image come from? A blob field in the data, or a field with a URL, or a field with a filename (where the rest of the URL would have to be added) or taking advantage of the attachment in 10?
A2) Currently all of our images fields are simply a file path back to the system folder. I could see us eventually putting them into the blob, since I saw all the slick demo's at the UC.
When do you anticipate the release of the next version of the flexviewer?
Thanks again for developing such a cool tool!
Frank
