Looks like my sample may have been too simplistic - upon re-reading
http://code.google.com/p/google-web-toolkit/wiki/ConditionalProperties it
looks like they do indeed suggest using a default as the 'correct' way to
do things:
I'll try to build a more complex test case that actually uses th
@Colin: thanks for isolated example that shows the problem.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.co
If you compile in PRETTY instead of DETAILED, it won't intern those
strings, but still will leave the output mostly readable (just no packages).
Without seeing the rest of the structure of the module files, it is hard to
speculate, but we're using more or less the same idea successfully, though
I didn't think it would help, but I just added a default browser.engine
property to the BrowserEngine.gwt.xml file, just below the
Strange enough this does help, as it does starts now.
The code to determine the strong name has changed to:
strongName =
answers[computePropValue($intern_47)][co
I am debugging the bootstrap js script to find out what is going wrong and
I am a bit confused, please some help?
It seems that the bootstrap script throws an exception that is silently
ignored, such that the strongName variable is undefined, such that it tries
to load undefined.cache.js..
BTW:
