Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

InfoWindows for AGS/A2E layers #47

Open
bFlood opened this issue Jan 16, 2012 · 1 comment
Open

InfoWindows for AGS/A2E layers #47

bFlood opened this issue Jan 16, 2012 · 1 comment

Comments

@bFlood
Copy link

bFlood commented Jan 16, 2012

I think the default InfoWindows should be left as-is where the dev can set the exact content/style using a local template. however, AGS and A2E allows users to define InfoWindows in design mode and many users would expect these templates (well, the results of the template) to be used automatically. This makes their InfoWindow experience uniform over many different cleint apps (ArcMap, the AGS javascrip API, eventually ArcGIS.com, Google Earth etc)

so, a good option would be to use HTML generated at the server for the infowindow and use Ajax to fetch the html for the popup (or maybe an iframe for better css support?) The REST api supports feature based HTMLPopups:
http://atlas.resources.ca.gov/arcgis/SDK/REST/fs-htmlPopup.html

examples:
http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Hydrography/Watershed173811/FeatureServer/1/1/htmlPopup?f=html

http://sync.arc2earth.com/9280826/ArcGIS/rest/services/tfs/1920753/FeatureServer/0/1/htmlPopup?f=html

these Urls could easily be created by the framework, so all we would need is a simple option like "serverInfoWindows":true

@JasonSanford
Copy link
Owner

Yep, I agree. This would be simple enough and would be a big benefit to AGS/A2E users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants