09-22-2011 12:14 PM - edited 09-23-2011 11:57 AM
I get several errors, including one that says I have a cross domain issue. I have tried whitelisting the outside resources and listing the url's separately in the config. Both methods get me the same result.
If there are any WebWorks guru's out there could you take 5 mins and try running my simple page and let me know what the issue is? Even if this can't ever work, I'd like to know why.
Here's the link to the online resource for this code sample:
Here's a link to a live sample:
Here's the code
<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"> <html> <head> <meta name="viewport" id="viewport" content="height=device-height,width=device-width,u
Solved! Go to Solution.
09-27-2011 11:21 AM - edited 09-27-2011 11:30 AM
Here's the related link from another forum:
One other note. The above code actually works in the Beta Ripple emulator. However, it will not run on a simulator or on the physical device.
09-28-2011 10:04 AM
09-28-2011 10:18 AM
Thanks for the reply! I understand, and didn't expect anyone to debug the external library, just wanted to make sure I hadn't overlooked something really simple is all. I'm only 3 weeks into this framework and still not confident with some of the general stuff.
Thanks for checking it out!
Here is what I use for the whitelist in my config. If that's not correct please advise. Otherwise, thanks again.
<access uri="*" subdomains="true" />
09-28-2011 10:26 AM
That does look correct...
What I would do if I were you, is strip out all the JS toolkits and get a simple Hello world page up and going and then add in parts piece-by-piece. This will tell you where the problem lies.
09-28-2011 01:30 PM
Yeah, the Dojo Toolkit seems to load and work fine when I separate it. It's something with that Esri JS API and how it's trying to load the supporting resources I think.
For now anyway, I'll be sticking with Google Maps v3 API, which is working in my WebWorks application.
10-31-2011 10:31 AM
I'm having pretty good luck using OpenLayers (www.openlayers.org) on the device. OpenLayers seems to trigger the out of memory issue less frequently than google maps for me.
Plus you can customize your OpenLayers build so it only includes the component libraries you need (as opposed to the full source download).