Latest Contributions by TyroneBiggums

Yea, and/or embed... for HTML5 http://stackoverflow.com/questions/8702704/alternative-to-iframes-with-html5 ... View more

Look into this link. They are setting properties that have images as data. You could probably use this and customize it for displaying an image. There is probably an easier, Esri-like, way, but this is what I'd do. https://developers.arcgis.com/javascript/jssamples/widget_infowindowchart.html ... View more

What about using a different container in lieu of an iframe? ... View more

http://www.smashingmagazine.com/2014/02/making-embedded-content-work-in-responsive-design/ ... View more

I saw something like this yesterday. That user does not have access to that ncsu service. Are you able to open that service on arcgis online outside of your application? ... View more

Can we see the javascript? ... View more

It's probably worth noting that you'd need 3.11 (I think) to support IE11. ... View more

If you're going to upgrade, you may as well upgrade completely. Here is what I'd do: HTML5/CSS3: If you want to maintain support with IE7-9, you're going to want to refrain from HTML5. But, you can develop in Esri JS API 3.14 on HTML4. There seems to be a larger focus on well-formed HTML in HTML5. You can/should do that in HTML4. Otherwise, you can't really use HTML5 in the older browsers. So, I wouldn't worry about HTML5 or CSS3. If you're not doing anything fancy enough to require HTML5/CSS3, don't worry about either. Really, if you want some of the newer features, you're going to want to ditch old browser support. Or, those users will lose out on features. Summary: Use HTML4. Esri JS API 3.14 (or 3.15): It's probably worth it. Pretty soon you're going to run into issues where other browsers you'd like to support will just plain work better with freshly supported APIs. I think you'll find (assuming you're Esri code is AMD) that there isn't going to be too much you have to change. Don't get me wrong, there'll be some changes. But, we've gone from 3.11 to 3.15 seamlessly. They are adding goodies, not making too many changes. For example, look at this jsfiddle. Change the CND link from 3.9 to 3.14 and run it. The code is the same, the map renders the same way. http://jsfiddle.net/DavidSpriggs/2QxMw/ Summary: I recommend 3.14, at least, so that you can support newer browsers and acquire better support from the community. jQuery/Dojo: I've used jQuery for as long as I can remember. Some minor syntax might change but you probably won't notice too much just by referencing the newer version of these libraries/tools. You'll have more "oh cool" moments upgrading (you may as well go to jQuery 2+, btw) than you will have "oh crap" moments. Some stuff is deprecated, some stuff is added. It's doing pretty much the same thing. Browsers: I think it's going to be difficult to support IE7 and Chrome. It'll be more difficult to handcuff a user and force them to use an older version of Chrome. This is where your bigger dilemma is at, I think. Performance: I would be guessing. I have no idea what performance gains there'd be going from 3.9 to 3.14. Probably marginal at best. It should really just come down to which browsers you would like to support. You could make a lighter version of your application that works with the 3.14 CDN link. Download the browsers you're interested in, and test it out. ... View more

I do not have an answer to all of your questions, but I do have a few questions to stir up discussion. 1. Are you going to still support IE 7-9? 2. Are you also going to support IE10+ along with the other browsers? 3. Are you planning to support newer Chrome, Firefox, Safari versions only? 4. Have you considered upgrading your version of the API to the latest and greatest? ... View more

There are a handful of ways to manage authentication/authorization in a web app. It depends on what resources you have available to you, and how you want to manage the users (and their sessions). ... View more

Yea, we're going from SL to rewriting in JS. We had that ability in SL. ... View more

The setzindex of a graphic in a layer is what I'd be interested in but it looks like it's been removed in the latest version of the API (at least I don't see it anywhere in the API reference guide). I did see another old post that used getDojoShape().moveToFront(). I suppose I could iterate through all the graphics and move them to front/back in the right order to reorder them. But, moveToFront only makes it look like that shape is the top graphic. The order of the graphics are still the same. It's looking like remove all and add in the order that I want them in. I just don't want to see graphics flashing. Maybe it's going to be fast enough that the user doesn't see them redrawn? ... View more