Hey Calvin, 2010/8/20 Calvin <[email protected]>: > Hi Koen > >> >> I will assume that comes from the "google.load()" statement, done by >> the WGoogleMap. >> >> Can you try two things (independently): >> - see if it works with a progressive-bootstrap ? (you need to enable >> this in your /ect/wt/wt_config.xml file. >> - see if it is because the "google" symbol is somehow already >> defined in chrome by changing WGoogleMap: line 120: >> app->require(gmuri, "google"); >> into >> app->require(gmuri); >> >> Regards, >> koen >> > Good news. Your second suggestion works but not the first with the blog.wt > example. Would this requirement to amend the WGoogleMap as you recommend be > down to differences in Chrome configuration between our systems?
Given that you still see problems with your code, I am not sure about it. My idea was that perhaps in your Chrome browser, there is already a 'google' symbol defined perhaps by one of the extension bars, debugger, etc... > Anyway, unfortunately, with my actual code, I am still seeing the same > script error with Chrome 5.0.375.x or 6.0.495: Uncaught TypeError: Object > #<an Object> has no method 'load' That is strange, have you ruled out that you are not still using the old unpatched version of Wt ? > With Firefox 3.6.8, the Google map widget is rendered correctly, but when > trying to log-in, I get the following message in a pop-up window: > > Wt internal error: [Exception... "Security error" code: "1000" nsresult: > "0x805303e8 (NS_ERROR_DOM_SECURITY_ERR)" location: > "http://192.168.0.117/?wtd=6S4pyhny1Zg8uzYt&request=script&rand=914001 Line: > 144"], code: 1000, description: undefined > > With IE8, I am getting Wt internal error: [object Error], code: undefined, > description: Error occured, no method to execute 80020101. > > It may take me some time to generate a test case with my code that gives the > same error now that the blog.wt example works fine. Any suggestions to help > to narrow/pin down the issue would be most appreciated. One possibility is to build a Debug version of the library, in that way the non-minified JavaScript is used, and in this way we will get meaningful line numbers in firefox. You can then also enable debugging in /etc/wt/wt_config.xml and debug the JavaScript error using Firebug. You need set CMAKE_BUILD_TYPE:String=Debug in the CMakeCache.txt of Wt and re-run make. Since most browsers complain, there is definitely something particular about what you are trying to do -- could you hint to anything special about it, or, provide a trimmed down test case ? Regards, koen ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ witty-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/witty-interest
