I'm sorry to hear you're still having trouble.  I can give you some
general tips.  If you are unable to debug in hosted mode, you might
try using a javascript debugger like Firebug or IE8's developer tools.
When you compile, add the option -style PRETTY to the build and the
javascript output will be (somewhat) human readable.

I just checked biooffice.at in ff3, chrome, ie8 and ie8 compatibility
mode (ie7) and I saw that things worked in FF, but not the others.
The code not being executed is custom javascript, that looks like its
being generated on the fly and injected. Maybe it has to do with the
way your script is being injected?

The whole point of GWT is to reduce the pain of trying to write
JavaScript  - 1) take care of cross platform issues, 2) provide tools
such as hosted mode that make it easier to debug, so I'm going to
suggest that you refactor that code (in Java) so that GWT will handle
the browser dependent baloney.   For example, try using JSNI to wrap
just the function 'topoGetAltitude()', and write all the rest of that
code I see in the maps.log window in GWT.
 - the image tag becomes an 'Image' object
 - Change the altitude div to a label object (or DivElement)
 - The hard part will be wrapping the closure that gets passed to
topoGetAltitude().  There are sample ways to do this of this in the
GWT developer guide.
Then, you can write a dummy function called 'topoGetAltitude()' in
java script to mock the way the real function works.  The mock would
just asynchronously returns a number after a few seconds and test in
an isolated project using hosted mode to iron out this issue.  You
could modify the mock to test your timeout logic too.

If you want some more help writing your app in GWT and getting tips
for debugging strategies, I suggest postng to the Google-Web-Toolkit
group along with short snippets of code you want help with.

If you think you've found a bug in the bindings, please file an issue
(http://code.google.com/p/gwt-google-apis) with a small case that
reproduces the problem that includes a description of the problem,
Java source code and any errors you get from hosted mode or web mode.
Often, the first step is to re-write the case in JavaScript to make
sure the problem is related to the bindings and not the Maps API in
general.

-Eric.
On Wed, Jul 22, 2009 at 1:43 AM, lumo<[email protected]> wrote:
> comilation log is ok (although i still does not know how to change the
> compiler...):
>
> WARNING: 'com.google.gwt.dev.GWTCompiler' is deprecated and will be removed
> in a future release.
> Use 'com.google.gwt.dev.Compiler' instead.
> (To disable this warning, pass -Dgwt.nowarn.legacy.tools as a JVM arg.)
> Compiling module at.biooffice.gwt.maps.biomap.BioMapModule
>    Compiling 6 permutations
>       Permutation compile succeeded
>    Linking into D:\GOOGLE\workspace\BioMap\build\gwtOutput
>       Link succeeded
>    Compilation succeeded -- 19,168s
>
> i did not run it in hosted mode (only in browser, as some of my js run only
> if they are hosted on our webserver(registered service from another webpage)
> )
>
> you are right i get a nullpointer while creating a marker with point=null
>
> good and bad news...
> the js-error in ie is gone now, but the js still does not get executed.
>
> tell me what you need to help find out what it is...
> here is the compiled map:
> http://www.biooffice.at/biomap/test/biomapmodule.html
> when you click on a marker (which YOU created) it starts loading the
> altitude of that point from topocoding and is supposed to update it in the
> infowindow. (while its loading it should show you a loading image - this
> image is put there if altitude==0, the content of the infowindow will be
> logged to maps.log)
>
> >
>



-- 
Eric Z. Ayers - GWT Team - Atlanta, GA USA
http://code.google.com/webtoolkit/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to